There is another broken call to XGetWindowProperty() in ewmh.c,
which seems to have been introduced recently. Attached is the
patch.
Hope this helps. Regards
Harri
--- fvwm-snap-20060830/fvwm/ewmh.c~ 2006-08-30 10:00:03.0 +0200
+++ fvwm-snap-20060830/fvwm/ewmh.c 2006-08-31
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
CVSROOT:/home/cvs/fvwm
Module name:fvwm
Changes by: domivogt06/08/31 06:36:56
Modified files:
. : ChangeLog NEWS
fvwm : events.c ewmh.c
Log message:
* Fixed map/unmap bug.
* Another 64 bit fix.
On 8/31/06, Harald Dunkel [EMAIL PROTECTED] wrote:
There is another broken call to XGetWindowProperty() in ewmh.c,
which seems to have been introduced recently. Attached is the
patch.
I guess it was already corrected? I've tried the patch, but it seemed
that the changes were already there..
On 8/31/06, Harald Dunkel [EMAIL PROTECTED] wrote:
Hi Renato,
The snapshot of today still uses 0 instead of 0L in the
argument list for XGetWindowProperty. Maybe you have a modified
version, or you are working on a different branch?
I've updated now from cvs, and it uses 0L... Maybe the
On 8/31/06, seventh guardian [EMAIL PROTECTED] wrote:
On 8/31/06, Harald Dunkel [EMAIL PROTECTED] wrote:
Hi Renato,
The snapshot of today still uses 0 instead of 0L in the
argument list for XGetWindowProperty. Maybe you have a modified
version, or you are working on a different branch?