[TCLCORE] Re: [Sawmill] Bug report: Fwd: Entry Widget and CPU Hogging...

[John H. <jo...@dc...>]

Jeffrey Hobbs writes:
|To be more specific, in TkWmRestackWmToplevel, we do an
|XReconfigureWMWindow, and then we wait for a ConfigureNotify event
|back.  This has a 2 second timeout, which is exactly what users
|see on wm's that don't serve one up.

Exactly which version of sawfish does this happen with? Since 0.30.1
sawfish ensures that it generates a single synthetic ConfigureNotify
event for every ConfigureRequest. I've appended the relevant log entry,

	John



2000-07-12  John Harper  <jo...@dc...>

        * events.c (configure_request): ensure that one (and only one)
        synthetic ConfigureNotify event is sent to the window after the
        configure request has been handled (even if the window's state
        doesn't change at all)

        [ this fixes the bug where menus in java/swing apps appear too
        high until the window has been moved ]

--
The TclCore mailing list is sponsored by Ajuba Solutions
To unsubscribe:  email tcl...@aj... with the 
                 word UNSUBSCRIBE as the subject.