Grant --
Thanks! You've found the missing piece I've been overlooking!
GM>> If a Motif client quickly maps and then immediately unmaps a window...
The problem is not limited to Motif apps. It also shows up with certain
Tk apps (well, we know of one, anyway) that use the TkSteal extension to
reparent an xterm window into a Tk frame. This was reported a few weeks
back by Michael Schumacher <mike_at_hightec.saarlink.de>. It is due to the same
oversight you've found.
I sent Chuck a tentative patch that works for the reparenting case, but
that I was never comfortable with, because it doesn't catch the synthetic
Unmap here, but detects the problem later, when we get the MapNotify and can
see that the parent has changed.
*** Chuck: I have tested Grant's changed Unmap logic against Tgdb,
and it does clear up their reparent problem as well. This is clearly the
right place to detect the condition, and has broader applicability.
Feel free to discard my version.
GM>> The obvious quick fix...presumably the if statement is there for some
GM>> reason...
Yup. Although removing it makes the code look superficially more like
version 1's handling, significant changes have been made in this area (I'm
not familiar with their history.) Removing the if produces decidedly
unpleasant results.
Thanks again!
Bob
--
Visit the official FVWM web page at <URL:http://www.hpc.uh.edu/fvwm/>.
To unsubscribe from the list, send "unsubscribe fvwm" in the body of a
message to majordomo_at_hpc.uh.edu.
To report problems, send mail to fvwm-owner_at_hpc.uh.edu.
Received on Tue Nov 26 1996 - 22:46:03 GMT