Where you put menu handlers is a design decision.
If you put a given menu handler at the App level, then that will be
the default for the whole app. It can be triggered even if you have
no windows open (e.g. on a Mac).
If you put a menu handler at the window level, you can tailor-make
tthe responses to each window type, and you can also make sure that
menu choice is not available if the window to field is is not available.
It sounds to me from the symptoms you describe, that you used a
shortcut to trigger a menu handler in a superior window, which then
automatically closed the subordinate window (?). This could happen if
you did not also have a menu handler defined for the subordinate
window...
HTH
Russ
On Dec 26, 2005, at 1:47 PM, [EMAIL PROTECTED] wrote:
I've noticed that you can put a menu bar on a window but also at
the App
level too. What is the customary philosophy of having menus
attached to the app
itself or the main window? I have one main window in my app, then a
number of
subordinant ones. Right now I hang the menus at the app level - but
I there are
several small issues ... the autocomplete doesn't work, and on
Windows I get
bleed through... if i click a shortcut on a subordinate window to
close it, the
same key stroke will close both windows at the same time.
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
