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

[Jeffrey H. <jef...@aj...>]

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.

I believe this is a wm bug because it works on almost all other
wms.  The problem was encountered in E as well, and the author
there also agreed and made the fix in E.

I can send you the relevant code that we specifically call.

Jeffrey Hobbs                     Tcl Ambassador
ho...@Aj...          Ajuba Solutions (née Scriptics)

> -----Original Message-----
> From: Jonas Linde [mailto:jo...@in...]
	...
> And jef...@aj... spoke unto the world. And said:
> > There used to be the same problem in E, which was fixed in 0.16
> > (I think between 0.15 and 0.16).  See the notes at:
> >    http://dev.scriptics.com/ticket/issue-view.tcl?msg_id=3777&mode=full
>
> > The author of E knew what the change required was, so you may
> > want to ask him.  I suspect that a lot of shared code was used at
> > some point that introduced these bugs in the gnome wm clients.
> > In any case, there is a solution for them.
	...
> Sorry, but I don't get it. You report on a supposed bug without any
> consistent way of reproducing it. The "wish; raise .; raise ." sequence
> doesn't behave in any way strange. From the discussion at the Scriptics
> web site it seems the problem lies with some suspiciously simplistic
> algorithm in TkWmRestackToplevel. I doubt this has anything at all to do
> with sawfish.

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