[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
On Wed, Jul 13, 2011 at 5:30 PM, Evert Glebbeek <eglebbk@xxxxxxxxxx> wrote:
>
> By the way, we need to specify what happens to the menu if the user doesn't create one for a new window. It would feel rather odd if most of the menu entries disappeared...
>
It doesn't really matter much to me. The easiest approach, and
probably works good enough for any reasonable application, would be to
just not change the menu if the newly focused display does not have
one set. That would be perfect for the most common scenarios:
1) Only the primary display has a menu.
2) Each display has a menu.
If somebody removes the menu from the current display, then it would
be cleared back to the basic system menu until either a new display is
focused or a different menu is attached. That's not going to be a
common case.
It gets a little messy if there are three displays with two having
menus and one not, because either of the two menus could be present
"on" the third display that has no menu ... but personally I don't
think it's worth trying to have a "principle app menu" concept (either
by implicit first usage, or explicitly set).
I think a brief reminder about how OS X works in the documentation
should be a sufficient way to address most concerns.
--
Matthew Leverton