strange menu behavior

Chris Sheffield cmsheffield at
Wed Mar 1 12:30:10 EST 2006

I've found what I think is a bug of some kind, but I wanted to ask  
here to see if someone else has run into anything like this, and to  
see if maybe it's something I'm doing.

I've got an application that uses a splash screen method.  The main  
stack opens and the user has to enter his password to continue.  This  
main stack has its own menu, which includes File -> Quit with Ctrl-Q  
set as the shortcut.  After entering a password and logging in  
successfully, another stack opens.  This stack has its own menu,  
which also includes File -> Quit with Ctrl-Q as its shortcut.  When  
hitting ctrl-Q from this second stack, it should close the stack and  
return to the main login screen.  Unfortunately, it's exiting the  
application completely.  I believe what's happening is hitting ctrl-Q  
in the second stack is triggering the menu item in the first stack,  
which *is* supposed to exit the application completely.  I've found  
that if I access the menu in the second stack by just clicking File,  
then ctrl-Q works correctly. It's almost as if the menu in the second  
stack is not loading or coming to the front or whatever until it is  
accessed in some way with an actual click of the mouse.

Anyone have any ideas?  Have I found a bug of some kind, or could  
there possibly be something I'm doing?  One extra piece of  
information is that I am changing the menu items of this File menu in  
the preOpenStack handler of the second stack, dependent on a couple  
different conditions.  Not sure if that would have anything to do  
with it or not.  This problem only occurs under Windows, btw.  On the  
Mac the behavior is exactly how I want it.

Any help would be appreciated.


Chris Sheffield
Read Naturally
The Fluency Company

More information about the Use-livecode mailing list