On 6/1/2013 8:24 AM, John Weeks wrote:
Alex-
Thank you! You seem to be the only one that takes an interest in my
peculiar questions.
The dialog takes extra clicks- one to select a menu item that displays
the dialog, then more clicks to interact with the dialog and click OK
button. I agree
Op 31-5-2013 19:25, John Weeks schreef:
We have a couple very long menus in our application (containing a list
of functions in our internal programming language). On Macintosh, the
menu simple runs from the top to the bottom of the screen and scrolls
very quickly. On Windows, it shows as a
I will try to recall what I did once.
Instantiate and add subclass of QWidgetAction to the menu.
Such subclass had to instantiate your widget (better not to derive it from
dialog).
To do this override createWidget. Such widget can be any complex or simple
widget.
If not mistaken I had explicitly
We have a couple very long menus in our application (containing a list of
functions in our internal programming language). On Macintosh, the menu simple
runs from the top to the bottom of the screen and scrolls very quickly. On
Windows, it shows as a multi-column menu that fills the monitor!
Alex-
Thank you! You seem to be the only one that takes an interest in my peculiar
questions.
The dialog takes extra clicks- one to select a menu item that displays the
dialog, then more clicks to interact with the dialog and click OK button. I
agree that huge menus aren't great; I'm not sure
