I've just encountered what appears to be a bug in the FL_ObjWin()
macro. If it is called in double buffer mode it returns the XID of
the Pixmap used as the back buffer rather than the actual Window XID.
This causes the program to die if this XID is used in any Xlib calls
requiring a Window XID or if used in the fl_set_cursor() function
(among others).
Is there any way to reliably fish up the actual Window XID other than
some form of gross hack?
spl
_________________________________________________
To unsubscribe, send the message "unsubscribe" to
xforms-request@bob.usuf2.usuhs.mil or see
http://bob.usuf2.usuhs.mil/mailserv/xforms.html
Xforms Home Page: http://bragg.phys.uwm.edu/xforms
List Archive: http://bob.usuf2.usuhs.mil/mailserv/list-archives/