LabVIEW Idea Exchange

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

LabVIEW searches complete run-time menu path to return correct ItemTag

Status: Declined

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

This idea was brought about the Discussion here...

http://forums.ni.com/t5/LabVIEW/run-time-shortcut-menu-odd-behaviour/td-p/1967017

 

LabVIEW currently searches and returns the FIRST ItemTag match that it comes across, regardless of the Menu hierarchy, which means the user must guarantee that the ItemTag name is always unique.

eg. For the picture below BOTH menu selection examples will return the SAME value ie. ItemTag = Approved  ItemPath = Move:Approved.  This forces the user to append text to TAGS that will not be unique, requiring extra programming.

 

run-time menu selection.png

 

I would like LabVIEW to take into account the complete menu path (ie. Top Level and sub-menus) when it searches and returns the ItemTag and ItemPath values.  This change will not affect anyone's current code, because LabVIEW does this in the background.

1 Comment
Darren
Proven Zealot
Status changed to: Declined

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