Hrvoje Niksic <hniksic(a)iskon.hr> writes:
wmperry(a)aventail.com (William M. Perry) writes:
> Only the menu about to be popped down is generated (I think the
> lwlib menus currently generate the entire menubar when you click in
> the menubar, not 100% sure).
I'm 100% sure -- I've been seeing it for a while. Because of that,
popups with many submenus are extremely slow as they need to evaluate all
the :active statements. Things get even worse when filters come into
play.
Cool, then I did a good thing. :) The code in (gui|menubar)-x.c could use
some commenting. I'm going to start writing up a GTK-Internals document
that talks about the redisplay, X specific crap I needed, how menus work,
etc, while it is still fresh in my mind.
> On to toolbars tomorrow - although this will probably be nasty
given
> that toolbar.c wants to know about pixel positions of the mouse and
> things like that. I want to let Gtk handle all that nastiness. Should
> be interesting. :)
You can always take a look at what Windows people have done. Although
I'd rather you wouldn't :), because the mswindows toolbar doesn't behave
properly, for instance it doesn't generate motion events when mouse moves
over the toolbar.
Well, is the only reason for motion events while over the toolbar for
tooltips? Those are handled natively by the GTK toolbar.
-Bill P.