LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

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

 

0 Kudos
Message 1 of 2
(2,685 Views)

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 | National Instruments | CLA
Message 2 of 2
(2,630 Views)