Laziness/convenience - other scopes requires extra RPC work, extra data type shenanigans, more work overall.
1 Like
Hey @PGriffith, I know you don't have much on your plate right now 
, but are you planning to update this extension to support v8.3?
Also, any chance of getting the functions in this module within the product itself?
Yes, I'll (eventually) get it working in 8.3; none of the stuff here should require significant overhaul.
I'd definitely like to get some of this stuff into the platform eventually, like the dataset extensions, but I'm not in too big of a hurry, and some of the stuff is explicitly not intended to be available without "opting in" by installing this module.
6 Likes
Hi,
The dataset extensions look so handy. Is this meant to work on Edge? I tried to install the module but got a 'not licenced on Edge' error...
Koen
Edge does not allow for arbitrary 3rd party modules to be installed.
Can this module be included in the whitelist? As I understand it, the reason most 3rd party modules aren't whitelisted is because they could introduce functions that could circumvent things specifically excluded to make the lower pricepoint viable (like database access, despite this still being technically possible through Jython/Java at the expense of labour). However, modules that simply add creature comforts would be nice to be allowed. Perhaps it being open source makes this difficult though?
That being said, it would be extremely nice to have some of the functions in Paul's module moved into the Ignition source itself... like isAvailable - I use this function in 80% of my views. An Edge project for me would be painful going back to using:
indexOf(toStr(qualityOf({tag})), 'Bad_NotFound') = -1 &&
indexOf(toStr(qualityOf({tag})), 'Bad_Disabled') = -1
1 Like
I'm able to offer my Integration Toolkit in Edge when you buy one of my drivers. The Modbus module is just $200 in Edge. {/shameless plug}
4 Likes
Yeah I knew that you finally got your module approved which is great, but your module isn't open source like Paul's. Guessing that might affect it's eligibility?
I can't read IA's mind, but I expect that is a consideration. And that I am trusted to not break the Edge rules.
You could use my transform() function to do a single qualityOf() operation and then the two comparisons against value(), if you want something particularly efficient.
I should mention that my tags() expression does transfer each result quality into the dataset using BasicDataset's quality arrays. I'm not sure if the [] operator retrieves those qualities, but if it does, and you have many tags for which to check availability, wrapping the tags() function will be most efficient.
2 Likes
SubscriptExpression does not pay attention to the quality flag on dataset data. Might be an improvement, might break all the things...
I can see the logic here, though this module as it stands offers too many "dangerous" functions to be something I'd campaign for including. I think the best path forward is for me to just add a few of the minimally invasive helpers to the core product, rather than push for this module to be added to the whitelist.
11 Likes
That would be marvellous if you could! 
6 Likes