Dominik Vogt wrote:
>
> I am mistaken here. These events do play a role. For some reason
> (I think to make some other application happy when it starts as an
> icon), I forced an UnmapNotify event being sent to the application
> before the icon was created. I'm mystified as to why wish thinks
> the UnmapNotify negates the MapNotify that arrives later.
> Maybe it processes events out of their proper order. Anyway, I've
> added a faked MapNotify event that is sent right before the
> UnmapNotify, and wish seems to be happy now.
>
> Please consider reporting this problem to the wish developers. I
> still think it's a bug in there that may well show other symptoms.
> In general processing events out of order - especially events
> that are of related types like MapNotify and UnmapNotify - is
> dangerous. It usually works as long as not much is happening on
> the desktop, but when things get really busy it may cause
> problems.
>
I did submit a bug entry at tcl.sourceforge.net and quoted some of your postings
there, hope that'll be ok. The Bug entry #578569 and any comments to it can be
viewed at
http://sourceforge.net/tracker/index.php?func=detail&aid=578569&group_id=12997&atid=112997
Gerhard
--
Gerhard Hintermayer
http://www.inode.at/g.hintermayer
--
Visit the official FVWM web page at <URL: http://www.fvwm.org/>.
To unsubscribe from the list, send "unsubscribe fvwm" in the body of a
message to majordomo_at_fvwm.org.
To report problems, send mail to fvwm-owner_at_fvwm.org.
Received on Mon Jul 08 2002 - 08:39:10 BST