Hovering over Drop Down Menu triggers "Mouse Leave" Event

[MadScientist]

Hi, If anyone can help with this problem, I would be very grateful.

I have a tab control set to change to a different page when the user's mouse enters or exits the tab control. The purpose of this is so that the tab control becomes invisible when coloured "transparent", depending on the user's mouse movement. This allows the full screen to be used for viewing the video when menus aren't needed, and menus can appear when the user moves into the tab area. There is also a button to lock the menu in place.

This worked really well until I added some Text Rings to a sub tab menu. When the user clicks the drop down arrow, and hovers over the items, the event case registers as if the mouse has left the tab control, and the tab resets back to page 1 (blank page). I don't want this to happen, but I still want to use drop down menus as they are more concise and convenient than the alternatives (listboxes etc). This does not happen with buttons, and other controls, only with drop down menus as far as I know.

Can anyone suggest a workaround? I have chosen this trigger method because it is less processor intensive than using the mouse move event coordinates to trigger the tabs to appear. I need to save as much processor time for video capture as possible. I have attached my vi (Labview 2010 32-bit) with the tabs set to grey so you can see them and test for yourself. 

[zou]

This might not be a bug.  The pull down menu might be another window itself.  When you hover onto the menu, you are leaving the Tab.

To work around this, inside the mouse leave event, check the cursor position, make sure it's not within the boundary of the Tab.

[Darin.K · Accepted solution]

I would add an Event Case for 'Operate Menu Activation' for the ring controls.  This simply feeds a true constant into a shift register in the while loop.  In the Mouse Enter and Leave events add a case structure and only change pages when the boolean is false.  Be sure the feed the true value back into the shift register in the Mouse Leave case as well (other cases can use the Default of False so you don't have to string wires in every case).

Quick mod after ripping out IMAQ stuff, also remove the delay in the Event Structure loop, the ES provides needed delays.

[MadScientist]

Thank you for the quick replies!

Darin, the change you made works well. I forgot that event structures don't need timing delays. I will add the changes you made and see if it still works while the image control is below the tab and report back.

James

[MadScientist]

Darin,

I had a go at repeating your changes, and I don't know how you added the "operate menu activation" event. I can't see it in my "add event case" menu.. How did you create this event case? 

[Darin.K]

If you choose one of the rings as the Event Source (Camaras, Video Modes) you should see the Event right below Value Change.

[MadScientist]

For me, there is nothing below Value Change. See screenshot. Maybe I need an add-on or something? Your mod works in my version though, so it's strange how I can't select it. 

[Darin.K]

Oh man, that is one of those top secret private events.  Normally they are labelled as such in the Context Help, not this case so I guess the cat is out of the bag.  I may be more helpful over on your LAVA crosspost.

[MadScientist]

Ok, thanks for your help so far. You noticed my post on LAVA as well 🙂  

Anyway, it would be really useful to have more events to choose from, and more properties for property nodes, rather than trying to shoehorn the features I want into the program!