LabVIEW Idea Exchange

cancel
Showing results for 
Search instead for 
Did you mean: 
Broken_Arrow

Put the TAG VI's on the palette

Status: Declined

Any idea that has received less than 5 kudos within 5 years after posting will be automatically declined.

Don't hide the very useful Tag VI's. Put them on the palette! (we need better icons for 'em too Smiley Wink)

 

TagsOnPal.jpg

Richard






13 Comments
PhillipBrooks
Active Participant
The icon is fine; just tilt it 5 degrees, make it a darker yellow, the text bold and it would be a 'best buy' for me 😄
Broken_Arrow
Active Participant

Phillip, LOL. I hope I don't get caught up in a logo copyright.

 

But seriously, I was referring to the icons for the individual VI's that NI made. You have to look carefully to tell the difference between VI, OBJ, Get, Set, etc.

Richard






PhillipBrooks
Active Participant

If the VIs are placed on the palettes for public use, then I would expect them to use the conventions on LV primitives like the queue glyphs or instrumentation 'set' and 'get' type functions.

 

I spend at least a few minutes thinking about my own icons, I wish NI would do so with theirs.  They did go to the trouble of making a library...

 

http://zone.ni.com/devzone/cda/tut/p/id/6453

 

What do you think this VI does?

 

WhatDoIDo.png

 

 

Broken_Arrow
Active Participant
That icon looks like it reads a file and makes one of three types of image data based on the file.
Richard






tst
Knight of NI Knight of NI
Knight of NI

> What do you think this VI does?

 

Gives me a headache? 

 

Seriously, who came up with that color scheme?

 

 

BA, you should note that there aren't three kinds of image data (well, actually there are, but that's not relevant here). I assume what it does is accept a path to an image file and then determine internally what file type the image is and use that to call the correct VI to load the image. OpenG has a similar VI.

 

 

Anyway, I was the one who petitioned NI to make the tags available publicly, but I have to admit that I haven't used them in any production code since. I did mainly because I figured it would be reasonably easy (since the code was already there and working) and because I figured others might find it useful in their production code. I use them occasionally, but I usually just use the private methods, which are easier to use.


___________________
Try to take over the world!
Broken_Arrow
Active Participant

tst, I think the tag VI's are extremely simple to use. Thanks for talking to NI about them. What private methods are you talking about? Is there a setting in ini to activate it?

 

 

Richard






tst
Knight of NI Knight of NI
Knight of NI

The methods should be available if you install the scripting API. My original request was simply for NI to make these methods public. They chose to create wrapper VIs instead, mainly because this allowed them to ensure that all user tags would be namespaced and thus not collide with existing tags.

 

The main thing I don't like about the VIs is that if you wish to continue using the reference for most properties/methods after using the VI, you have to cast the reference back to the original class or wire it around the VI. Not hard, just annoying.

 

You should find more details about these VIs in posts Darren made both here (as a nugget) and on his blog.


___________________
Try to take over the world!
JackDunaway
Trusted Enthusiast
@tst: Try reposting that link to Darren's nugget, thanks.
Broken_Arrow
Active Participant

Darren's nugget is how I learned about these VI's. Making them more accessible (i.e. on the palette) would expose many more people to tagging.

 

As far as the usefulness, let the people decide. I've never used a rendezvous, but that doesn't mean it shouldn't be on the palette.

 

How about an "Advanced" sub-palette that could hold items like tag VI's?

Richard






Neil.Pate
Active Participant

Broken Arrow,

 

Please can you post a link to the original discussion about tags. I cannot find it using the NI search engine (big surprise there...).

 

Thanks