Dan Espen wrote:
> 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?
Try to do fullscreen (press f11) several times. Note that most
distribution builds don't do it, as they use EWMH, only the official
build has this problem. See also "FVWM: firefox disapera on full screen"
thread on this list. Same with Reader 7.0.
>> 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?
When I replace XFlush(dpy) with XSync(dpy,False), it behaves the same.
XSync(dpy, True) discards queued events and is almost never used, IMO.
--
Jindrich Makovicka
--
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 Thu Mar 17 2005 - 02:49:12 GMT