Menu selection event

Is there any way to generate a Menu Selection Event for a menu item that has a sub-menu?

You can handle the "Menu Activation?" (Filter) event to set the menu item info before it is displayed.
The attached VI has a custom menu. Set the "Checked?" boolean to the desired value and then activate the menu to see the effect.
Attachments:
Menu_Test.zip ‏9 KB

Similar Messages

Menu Selection (App) catches Menu Selection (User)

In 2010 I would use the same case in an event structure to handle both Menu Selection (App) and Menu Selection (User) events.
I've recently upgraded to 2012 and started seeing duplicates of my User menu events. I separated the Menu Selection (App) and Menu Selection (User) events into separate cases. I still see duplicates. The event is being caught in both the Menu Selection (App) and Menu Selection (User) cases. (App) menu items are only caught in the Menu Selection (App) case. If I use Menu Selection? (App) I don't see the duplicate events.
I don't like that solution as I would like to only have one case in the event structure to handle all menu events. Is there a fix short of upgrading to a new version?
Thanks,
Jason

Jason,
What you have found is a known bug in LabVIEW 2012. I was able to recreate your issue and tried to find a workaround for what you were doing, but aside from simply building in logic to reject the menu selection event if it occurrs too close to the previous event, what you have found is probably the simplest solution.
If this is a reason you choose to upgrade to a newer version you have not yet installed I will give you a friendly warning that this bug still exists in LabVIEW 2013 SP1 but seems to be fixed as of 2014.
Matt J
Professional Googler and Kudo Addict
National Instruments

I am using the "Menu Selection With Events.vi" example alongside other while loops, When I select exit from the new menu it stops the other while loops but not the menu/event while loop

The event driven menu example works fine and I've integrated it into my application. I have built in simple local vars to link menu selections to existing GUI buttons. The problem is that I cannot get the File-Exit menu option to switch off/terminate the application. The [1] "Stop": Value Change panel of the event structure simply switches off the other while loops but leaves the event while loop running. Add a while loop to the axample using a local var from the event while loop to terminate 2nd while loop to get the effect.
Help appreciated, Chris

Attached you will find a modified version of your VI.
I documented what I did on the block diagram.You were right on you just needed to add a variable with a true wired to it.
Have fun with it.
Joe
Joe.
"NOTHING IS EVER EASY"
Attachments:
Menu_Selection_with_Events_%26_while_loop[1].vi ‏76 KB

Can I programmatically trigger a menu item tag selected event?

I am trying to trigger a menu item selected event using built-in vi's. I want my Handle Menu vi to handle the case where the user checks on a boolean control as well as slected the menu option. I don't want to use POSTMESSAGE with acceleration key combination. Are there any built-in vi's which can "post" such a message?

I have a similar situation and understand why adding a message to the menu queue would be an elegant solution to the problem.
I have lots of menu bar selections in my program, and I would like to set up a button bar like most applications now have. To do this using the "in parallel" way becomes a ratsnets of wires and would take up a lot of window space.
I have attached a file that is a good example of how to solve this problem with Event Structures in LabVIEW 6.1. It doesn't take up much additional diagram space and it can be quickly and easily reconfigured.
It would be nice if future versions of LabVIEW had a more integrated button bar.
Matt
Attachments:
Menu_and_button_bars.vi ‏68 KB

VI Keydown event interferes with menu selection

My application requires that the user log a data point with a spacebar pressed. To do this, I want to use the Key Down event at the VI level. However, I find that when I include this event it disables the keyboard's Alt- menu selection, even though I'm passing all the parameters through KeyDown unchanged. I've included a skeleton VI that exhibits this behaviour. Has anyone else run into/overcome this problem?
Thanks,
David Moerman
Advanced Measurements Inc
www.advmeas.com
Attachments:
VI_KeyDown_vs_MenuSelect.vi ‏41 KB

Instead of using keydown, use keyup. I have written the attached VI to decode the scancodes on my computer so that one can tell what key was pressed. Unlike with keydown, this method allows the alt-keys of the window to work and it will indicate a larger number of keys.
Jeremy Braden
National Instruments
Attachments:
Decode_scancodes_into_ascii.vi ‏487 KB

Capturing a front panel menu selection in a SubVI

All,
Title is pretty descriptive, so i've got a subvi that's running pretty much in a while loop and I want a menu selection from the parent VI to be able to cancel it. What i've tried so far is passing the reference to the front panel menu and then trying to detect a valuechange/mouse click/ selection etc in an event loop in the SubVI. The problem is it doesn't look like the front panel menu registers the change until after the SubVI finishes executing. How can I fix this?
Regards,
Ken

Hi Ken,
I hope you are doing well today! Before I attempt the answer your question, I
need just need to clear a few things as to what you are trying to do. Are you
trying to stop the while loop in the subVI from the parent VI? And, what’s the
purpose of using a menu selection? If you can post a simple example, that would
be great.
Adnan Zafar
Certified LabVIEW Architect
Coleman Technologies

Handling menu selection in multi states of states machine

Hi everyone,
My application uses states machine architecture, I have to handle menu selection in two different states and the 2nd of them has to be handled by the event case structure.
The problem is that when I use event structure in the 1st state it is also handled later by the event case in the 2nd state and it is impossible to handle menu selection in the 1st state by the "Get Menu Selection" block because according to it's descripton if event structure is configured to handle the same menu as item as this block, LabVIEW ignores this function.
I would be greatful for any clue.
Greetings,
Mariusz
Solved!
Go to Solution.

Thanks for respond.
Here's a code explaining the main idea.
Attachments:
Untitled 1.vi ‏9 KB
Enum_States.ctl ‏5 KB

Reversing "Add Flagged Photos to Selected Event" Command

Apparently, we inadvertently moved all of our flagged photos to one event using the "Add Flagged Photos to Selected Event" Command. The problem is, I want all of these flagged photos back in their original events.
Is there a way to do this without manually re-sorting the photos? I currently have ca. 10,000 photos in 270 events, and I am not looking forward to a manual re-sort.
Thanks in advance for your help.

The easiest way ti to use your backup of the iPhoto library - that is why you make them - in case of software, hardware or human error
If that will not do it, I can not test this but it should get you started - assuming that your events are in the default time/date based set up - and assuming that the photos are still flagged create a new event form the flagged photos and select that event - under the event menu ==> autosplit selected event - this will create new events that will be next to the event the photos came from - then go through and merge the newly created events with the event the photos came from
Other that your backup I can not think of any other way to get there except to move each photo manually
LN

Get menu selection help

Hi I am new to the Labview world and am having a bit of an issue with the get menu selection vi. I opened an example (Queued Message Handler.vi) and basically copied that get menu selection setup in my vi. Yet all i get for menu selections are null strings. I have tried to set the get menu selection timeout to -1 then selecting a menu item. I still get a null string from it so I know it isn't some timing issue. I have attached a copy of my vi. The runtime menu I was using was just File with an exit option. There are a couple sub vi's that i made that are required to run Queue.vi but they arent really needed to see what I am doing. Thanks for any help in advance.
Attachments:
Queue.vi ‏59 KB

Hi Superseadragon,
I recommend you to use an event-driven state machine desing pattern that combines a queued state machine and event structure into a hybrid single-loop design pattern.
I made an example with your code but as I don't have your set up I put in commentary all the communication function.
To close the VI click on the cross on the upper right corner like for a tradionnal application.
You can fire an event from the run time menu. I included a case in the event structure. Have a look at it. This is not the only way to do it.
Have fun with your algae!
Charly
It's always sunny in California! Certified LabVIEW Associate Developer!
Attachments:
SuperSeaDragon.zip ‏135 KB

Run-Time Menu and Event Structure~~HELP~~

Hi, brothers,
I'm new user for LabVIEW. Use the version of LabVIEW is 8.6
One problem describe as below:
Can Run-Time Menu and Event Structure exist simultaneously?
Without Event Structure, Run-Time Menu works well, but Run-Time Menu works abnormally.after adding Event Structure,
How do I modify the problem?
Thank you for your help.
Attached is the program.
Attachments:
PC_Adjustment.zip ‏44 KB

Yes they can coexist, but not how you did it.
Every iteration of the while loop you wait for an event in the event structure, and you look if the user has selected anything from the menu.
To get this working you should add an event for <this VI>\Menu Selection (User):
Ton
PS you should add a stop button, the only way you can stop the VI is hitting the 'emergency stop' button, with hardware connected (like you have) this is not the adviced routine
Message Edited by TonP on 09-26-2008 07:34 AM
Free Code Capture Tool! Version 2.1.3 with comments, web-upload, back-save and snippets!
Nederlandse LabVIEW user groep www.lvug.nl
My LabVIEW Ideas
LabVIEW, programming like it should be!
Attachments:
Main_BD.png ‏5 KB

Programmatically simulate the Get Menu Selection vi

Hi,
I'm using LabVIEW 8.5 base version (no event handling). I have created a custom RTM (Run-Time Menu) and use the Get Menu Selection vi wired to a Case structure to handle all the items. (Part of the handling it to put a check mark next to the selected menu item and clearing the check mark from all other items using the Set Menu Item Info vi. Too bad it doesn't do that automatically. Maybe it does in newer versions, but I digress.)
My application can save and recall setups. When I recall a setup I would like to programmatically call the respective Case, as is done by the Get Menu Selection vi, even though the menu is not actually clicked by the user. I cannot find a way to do this. Is is possible?
Thank you.
Ed
Solved!
Go to Solution.

Edjsch wrote:
Thank you for your reply. It looks like there is no convenient way to "simulate" a Windows "event" with the base version. Duh!
I'd take that a step further and say there is no convenient way to write software without the event structure. I don't know how people write code without it. This limitation has been removed and the event structure comes with all versions of LabVIEW as of 2012.
As for my virtual keyboard trick, here is a better one I didn't get a chance to check the link previously.
https://decibel.ni.com/content/docs/DOC-15310
With that you can call a subVI that will invoke the Alt+F or whatever to open menus.
Edjsch wrote:
Note that in the Get Menu Selection vi's Case structure, I had to actually clear each check mark and set the one for the current selection, since the RTM does not handle check marks automatically, as, for example, Visual Basic does. Again, maybe newer versions do.
They do not, you are welcome to make an idea exchange for it, but I'm fine with toggling that bit myself. But then again I can't think of a time when clicking on a checked item, shouldn't uncheck it so I can see your point.
Edjsch wrote:
Let me know if anyone would like to see screen shots of that area of my block diagram.
Never post screenshots.
When posting code post the actual code not a screenshot. You wouldn't take a screenshot of a text file and post it on a text language forum. Upload the actual VI, or zip several files and upload the zip. The exception to this rule is when uploading a VI Snippet. This is an image with the VI embedded in it, so the source is still intact.
Unofficial Forum Rules and Guidelines - Hooovahh - LabVIEW Overlord
If 10 out of 10 experts in any field say something is bad, you should probably take their opinion seriously.

PDA Menu Selection (user) Item Tag returns Item Name

Using LV Mobile 8.6.1 with iPAQ on Windows Mobile 5.0 (5.1.1702) I have a custom run-time menu. The Item Tags are shortened versions of the full Item Name. The event structure provides the Item Tag, but the actual string value returned is the full Item Name. The Item Path returns the complete hierarchy of the menu selection, but also contains the Item Name.
Michael Munroe, ABCDEF
Certified LabVIEW Developer, MCP
Find and fix bad VI Properties with Property Inspector

Hi David,
My PDA application has a custom run-time menu of 20 items. Some menu items are up to 4 words in length, so I used unique single-word names for the item tag to differentiate the commands. Debugging my code, only the single word menu items executed correctly. All others ended up in the default case.
This has to be a bug in LabView, that the event structure returns the Item Name in place of the cluster element labeled Item Tag. The same problem exists in the Get Menu Selection.vi.
The work around was to change all the case elements to match the item name and not the tag. The item tag then is never used.
Michael Munroe, ABCDEF
Certified LabVIEW Developer, MCP
Find and fix bad VI Properties with Property Inspector

Firing events from a Menu using Event Structure - all in the same Event Window?

I have an ap where I have three menus, and several selections from
those three menus. I'm trying to keep everything within the Event
Structure, but it seems that ALL of the events fired from the Menu must
be contained within one "frame" of the Event Structure, that being the
Menu Selection (user) Event. In other words, if I have 16 events that
can be fired from the menu, do I have to put them ALL in this one event
frame?
I can't seem to use a T/F indicator within the Menu Selection (user)
Event to access another Event. For example, within the Menu Selection
(user) Event, I placed a boolean named X and can turn it on with a menu
selection. Now, make a new Event Structure to look for X Value Change -
doesn't work.
Message Edited by Broken Arrow on 11-30-2005 10:24 AM
Richard

I use one event, Menu Selection (user). to trap all of my menu events. Use Item Path and / or Item Tag to figure out what menu item was selected then branch code based on selection. Wtih Booleans and menus you need to update the state of the boolean on the menu by setting it True or False. It doesn't automatically toggle like you would expect.
Matt
Matthew Fitzsimons
Certified LabVIEW Architect
LabVIEW 6.1 ... 2013, LVOOP, GOOP, TestStand, DAQ, and Vison
Attachments:
menuSelect.JPG ‏45 KB

Hardcode menu selection

How to hard code value for a menu selection?
I want a specific menu option to be selected if i click a particular button.

309...,
In your .jpg you show an event structure embedded inside another event structure. Don't do it! You are going to wind up having lots of problems with your code.
Event structures capture events even when they aren't in the current path of execution. So if you do a number of menu selection (Apps) before you do a Cut (Value Change) you'll wind up accumulating events in your queue for the inner event structure. Possibly to the point of even crashing your program, but at least to the point that your program will seem like it's not behaving the way you want to.
There should be only one event structure in any given while loop. Any given event case should run quickly enough so that the front panel always seems responsive to the user. Never trap an event structure in a piece of code that may not be executed or not executed for a long time (such as in a case structure or another event structure.)

Menu selection with timer callbacks

Hello,
I am using LabWindows 5.0.1 to display event logging data at regular intervals
based on a timer callback (200 msec). The data is displayed on the main
panel in listbox controls, etc.
When timer events are enabled, I'm having trouble making menu selections
from the panel menu. When I click on a menu bar entry, I get the drop-down
menu list, but it disappears before I can make my selection.
How do I solve this problem?
-Thanks

Hello Dough
Have you find a solution for the problem? I have a similar problem in an customer application and the customer is very disapointed about that...
Stephan

Menu selection event

Similar Messages

Maybe you are looking for