[Lazarus] New menu designer

[Anthony Walter]

Ondrej,

The old menu designer was stay on top as well. Stay on top is needed
because the a menu designer is typically a separate non docking window (a
dialog). For all users menu editing invariably consists of:

1. Creating a menu (or sub menu) item using the menu editor dialog
2. Then editing the menu item properties using the object inspector
(setting the name/caption, possibly creating a click event stub)
3. Go back to step 1

These steps are repeated many times as a user creates many items while in
the initial stages of developing an application. If the menu designer did
not stay on top it would be a major annoyance to constantly go to some type
of menu list to bring the menu designer back to the foreground. Not
everyone has multiple screens, and more often than not the entire menu
editor dialog would be obscured by the code window when adding events, or
with docked IDE user when switches to the object inspector (which would
likely be docked tot he side of the code editor) in step 2.

As such, in the case of editor menus, it makes total sense to keep the menu
editor on top of other IDE windows until the time when the user closes the
menu editor (clicks the X button in the menu editor title bar). Any non
stay on top form style for menu editing would driver users crazy.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lazarus-ide.org/pipermail/lazarus/attachments/20151222/0438f81b/attachment-0003.html>