LabVIEW
"Start Asynchronous Call" as it should be
I've never had any issue with Tools >> Advanced >> Edit Palette Set in adding XNodes. But this feels clumsy.
Before VIPM supported XNodes naively there were two options that were both hacky. First was you could make a normal VI with nothing but your XNode on it, then in VIPM configure that VI to be inlined (place contents) which would place the XNode. Another solution was to have a Post-Install VI as part of the package which would replace a placeholder VI on the palette, with the XNode. This also worked and allowed for other XNode methods like Copy to be invoked properly where dropping the VI contents wouldn't.
VIPM as of the last year or so added VIM and XNode support and I haven't had any issue just adding it there. The icon will be the one with the .xnode file but obviously the node when dropped may look different depending on how you have it configured to be drawn.
What issues have you had in the past?
@EricR wrote:
Are you open to a discussion with me about allowing NI to just ship this code?
XNODE! XNODE! XNODE!
But seriously there are several useful well written XNodes on NI and LAVA. NI should consider making it a real official feature. Even if NXG is the new hotness with no plans (that I'm aware of) to have XNodes in it.
As for the palette stuff. Here is a VIPM package I made which installs just fine, and creates a Paul palette, and under that an XNode Icon Constant item which seems to drop and be used just like it should. Sorry it is so ugly I just wanted to make sure a package could be made with VIPM with no issues.
Listen I can make all the packages we want I just think Paul has several worth highlighting and it might make more sense to have a Paul's Favorite XNodes package which has a bunch of these rather than a package for each XNode. I wouldn't want a palette for each array function for instance. This is a bit larger of a request but one I can still help out with. I'd just need a list of XNodes Paul things is ready for public consumption. I think I can find most he's posted.
Also in playing around with this one I did find a few things that you might consider changing in the future. The "Calll and Collect" mode when right clicking has one too many L's.
In the Support folder there is a "Tamplete.vi" I assume this should be template.
I too would suggest adding some way to enable reentrant calling. It could be added without any extra input by reading the VI Execution >> Is Reentrant property, and then just automatically OR the option with 0x40 if it is. The only minor issue is this is adding an extra property node read that normally wouldn't be there. Maybe a checkbox on right click for Reentrant Run would work.
And lastly I think it would be super slick if you could support dragging and dropping a VI reference to the node and handle the drop. For VIs that are saved this is easy enough but I'm unsure if you can script the Static VI Reference to a VI in memory and not saved yet. Still I could see myself using this for non reentrant things today.
