Darren's Weekly Nugget 04/13/2009

[Darren]

---

crelf wrote:

I've always used the private scripting nodes to use tags - any chance of the VIs in the new folder appearing in the standard palettes in LabVIEW 2009?

---

The UserTag VIs will not be in the palettes in LabVIEW 2009.  There are no plans to put them in the palettes, but they will continue to ship with LabVIEW.  If you think it would be a good idea to put them in the palettes, feel free to submit a product suggestion.

-D

[crelf]

I wonder if I should just make a package that exposes some of the "hidden" (ie: not on the palette) features of LabVIEW...

[F._Schubert]

What about exposing them via right-click menu.

See here:

https://forums.ni.com/t5/LabVIEW-APIs-Discussions/What-types-of-LabVIEW-right-click-menu-features-do...

Felix

[crelf]

---

F. Schubert wrote:

What about exposing them via right-click menu.

---

I don't think that's the right framework for exposing hidden VIs in vi.lib - the right click framework is more for applying attributes to existing selected FP & BD items.

[F._Schubert]

I agree, my intention was not the same as yours. I was too busy in my thoughts about how to use this feature (already knowing that it exists and how to access it).

Exposing these features would be great, not only to facilitate/ease the usage. It also will allow access (and knwonledge) for more than a handful of LV-geeks that browse the LV directories for whatever exists there

Wouldn't it be as simple as creating a mnu entry for these VIs? Could it just be placed in the OpenG-tools, or distributed via VIPM-network?

By 'simple' I do mean technical simple and straightned legal aspects.

Felix

[crelf]

---

F. Schubert wrote:

Wouldn't it be as simple as creating a mnu entry for these VIs? Could it just be placed in the OpenG-tools, or distributed via VIPM-network?

By 'simple' I do mean technical simple and straightned legal aspects.

---

I think yes for both of those.  OpenG already has some packages that expose hidden VIs (librarian(?), scripting, etc).

[shb]

Result of a short test: The tags are working in the runtime engine. But you can not save them because VIs can not be saved in the runtime engine. (Cite of initial post: Tag names/values are persisted when you save the VI after assigning a tag.)

Greetings,

shb

[AbbeI]

Does anyone know whether user tags are supported in NXG?

Considering the boon they have represented to enhance and circumvent limitations of CG, it would be a shame if they were not (or a confirmation that NXG is not intended to be NX, but a brand new and incompatible language).

[tst]

---

@AbbeI wrote:

Does anyone know whether user tags are supported in NXG?

---

They are not.

NXG doesn't have invoke nodes and in NXG 5 there is no replacement for those methods or for the VIs.

That doesn't mean that they won't be there in the future, but NI's published roadmap doesn't go into that level of detail. In general, the implementation rate of existing LV features in NXG has certainly been slower than desired by many people (or not slow enough, for those who want NI to keep supporting and developing LV 20xx).

NI does say that if you have missing features that you need, you can save them in subVIs in older versions and call those subVIs from NXG, but I haven't tried that.