On Sat, Apr 10, 2010 at 10:18:07AM +0200, Carlos R. Mafra wrote: > > The other misuses of CARD32 which were addressed were calls to > XChangeProperty(.., int format, ...) where format == 32, but in this > case it involves XGetWindowProperty() and I couldn't understand by > reading the man page if something odd might happen, so I left it untouched.
The manpage here (from Debian's libx11-dev) specifies in prop_return: If the returned format is 32, the property data will be stored as an array of longs (which in a 64-bit application will be 64-bit values that are padded in the upper 4 bytes). > Is this "minimized window restoring as shaded" behavior always reproducible > for you? I never saw anything like that (on a 64-bit Core2 Duo here). 100% reproducable: 1. Minimize some windows 2. Use my menu entry for "RESTART /path/to/wmaker" 3. The formerly-minimized windows will be restored shaded. Even if they have the title bar hidden. And, to cinch the deal, when I print out the data array in wWindowSaveState it gives "0 1 0 0 0 xx yy ww hh 0", while printing the array read back in getSavedState gives "0 0 1 0 0 0 0 0 0 0" (i.e. reading each 64-bit returned value as two 32-bit values). I also haven't had a crash in step 3 since I fixed this problem, but I haven't done enough restarting to be able to confidently say that that is fixed too. -- To unsubscribe, send mail to [email protected].
