On Fri, Mar 22, 2002 at 11:53:12AM +0000, Angus Leeming wrote:
> (eg, it'd be nice to have multiple short Toolbars the can abutt each other
> rather than have a new line all there own.
This needs a little tweak: ToolbarNew as well as Separator and Newline.
Easy. I've found the toolbar stuff to be mostly OK, some little tweaks,
that's all (and one c++ problem with stupid fucking moc)
> eg2, communicate via signals rather than directly.)
sure
also, I need a name for each icon that can be shown in qt when the
toolbar is too wide... oh, and some moving around of setPixmap to
be GUII (I'll do that soon in my guii tree)
As for menubar, it needs a /total/ overhaul I think. It /might/ be
possible to get the current version working with Qt, but it's a real
struggle. Here's a few of the things I want :
1. shortcuts available (how does xforms do this ? haven't looked ...)
2. open_by_name makes little sense for Qt, it can handle it already
(probably qt can just continue to ignore this)
3. the on-demand menu creation. This is a real pain for Qt. Rather I
would like expand() to work at Menubar_pimpl constructor (I already have
this, sort of), and provide some signals to connect to so we can know
whether to update the "special" menus
4. probably a lot of other things. I found the way you have to parse the
menu structure was a bit confusing ... I don't know if the main
main_nobuffer technique is really best.
Ideally Qt would have to store the /very/ minimum of extra information
(i.e. only the mapping from the special menu type to the QPopupMenu for
it). The id (action) is already part of the Qt API for menus, so that
part is trivial to do ...
The menu stuff and the scrollbar are the only things really remaining to
do for the Qt thing to happen nicely I think.
later indeed,
john
--
"Way back at the beginning of time around 1970 the first man page was
handed down from on high. Every one since is an edited copy."
- John Hasler <[EMAIL PROTECTED]>
