Re: FVWM: bug: XMapWindow/XUnmapWindow race condition

From: Dan Espen <dane_at_mk.telcordia.com>
Date: Wed, 16 Mar 2005 23:14:52 -0500

Jindrich Makovicka <makovick_at_kmlinux.fjfi.cvut.cz> writes:
> Hello,
>
> There is a problem with XMapWindow and XUnmapWindow handling - when they
> are called too fast one after another, the window just disappears. This
> is the cause of disappearing window in official binary builds of mozilla
> and probably also in new Adobe Reader 7.

How do I make a mozilla window disappear?

> Sample code triggering the bug is attached. The created window is
> visible for one second, then disappears forever. After uncommenting the
> delay between map and unmap, the window vanishes for 1 second, then
> appears again.

Shouldn't that be using

Xsync(dpy,True)

if you really want to have the server display something?

-- 
Dan Espen                           E-mail: dane_at_mk.telcordia.com
--
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 Wed Mar 16 2005 - 22:16:08 GMT

This archive was generated by hypermail 2.3.0 : Mon Aug 29 2016 - 19:37:57 BST