09-14-2018
07:58 AM
- last edited on
03-14-2019
02:18 PM
by
NIadmin
Hi,
I encountered some weird close behavior with the SkyLine Tag API.
Error 1448 shouldn't originate in a close method. This error is caused by supplying a parent class to the wire, this causes the sort method to output an error, which should have been discarded inside the close methods instead of being propagated.
To More Specific Class in NI Skyline Tag.lvclass:Sort By Configuration.vi:6720001->NI Skyline Tag.lvclass:Close Tag (Multiple).vi:4260001->Jade Alarm.lvclass:close.vi->Jade Tag.lvclass:close.vi->SystemLink Interface.lvclass:close tags.vi->SystemLink Interface.lvclass:re-init tags.vi->dlg.Configuration.vi->Main.vi
Thanks
09-17-2018 05:39 AM - edited 09-17-2018 05:39 AM
That emoticon got in there by accident 😞
09-17-2018 01:55 PM
Does this always happen, or does this only happen in your code calling the tag close? I want to see if we can reproduce this.
09-17-2018 02:02 PM
I'll upload an example tomorrow.
09-18-2018 02:37 AM
Hi Mark,
The attached snippet (LV2016) shows an error for 2 of the 3 Skyline tag types (result image).
In my opinion the close method should never return an internal error, only propagate the error in, which should be ignored by the close method (which seems to be implemented correctly).
I would love to hear a rationale that advocates the opposite, there could be a good reason why the close wants to output an error on default object values.