I have come upon a troubling situation in my application: if I left click and hold the mouse button on a command button when a particular timer ticks, my application's GUI locks up.
The timer in question is in another panel, fires every 0.050 seconds, and is used to update/initiate some UDP network communication. The panels are not running in separate threads. This has been working fine for months, until I noticed a quirk: if I'm in a call to RunPopupMenu() when the timer wants to tick, the popup menu locks up, the timer stops ticking, and the user interface locks up. I worked around this by preventing the timer's callback from doing anything if the popup menu was open and this solved the problem.
The issue with the command buttons is still there, and is more perplexing. The only command button event I'm handling with the command buttons' callback is EVENT_COMMIT -- everything else is ignored.
Is this a known issue? The situation may be more complicated than just command buttons and timers, but I'm trying to look at it in simple terms.
Thanks
Randy
LabWindows 8.5, Windows XP SP2.
