On Wed, Aug 30, 2006 at 11:20:27AM +0200, Dominik Vogt wrote:
I have committed a fix for this. At the end of HandleUnmapNotify,
check for pending MapRequests for that window, replace the window
and parent with the client window and root, then call
dispatch_event immediately. (See attached
On Tue, Aug 29, 2006 at 10:18:30PM +0200, Viktor Griph wrote:
[snip]
The idea was to check for a MapRequest of FW_W_PARENT before reparenting
the window, while the server is grabbed, and if sush event exists not
unparent it. The problem is only if the window is mapped again before the
On Tue, Aug 29, 2006 at 10:18:30PM +0200, Viktor Griph wrote:
On Tue, 29 Aug 2006, Viktor Griph wrote:
On Tue, 29 Aug 2006, Dominik Vogt wrote:
On Mon, Aug 28, 2006 at 08:07:31PM +0200, Viktor Griph wrote:
On Mon, 28 Aug 2006, Andreas Ehliar wrote:
I have a problem with fpga_editor as
On Mon, Aug 28, 2006 at 08:07:31PM +0200, Viktor Griph wrote:
On Mon, 28 Aug 2006, Andreas Ehliar wrote:
I have a problem with fpga_editor as reported in bug 4062. With some
help from #fvwm I managed to find something suspicious. fpga_editor
does an UnmapWindow request and a MapWindow
On Tue, 29 Aug 2006, Dominik Vogt wrote:
On Mon, Aug 28, 2006 at 08:07:31PM +0200, Viktor Griph wrote:
On Mon, 28 Aug 2006, Andreas Ehliar wrote:
I have a problem with fpga_editor as reported in bug 4062. With some
help from #fvwm I managed to find something suspicious. fpga_editor
does an
On Mon, 28 Aug 2006, Andreas Ehliar wrote:
I have a problem with fpga_editor as reported in bug 4062. With some
help from #fvwm I managed to find something suspicious. fpga_editor
does an UnmapWindow request and a MapWindow request right after each
other.
An example program that does the same
