| WINDOW procedure and SET_X_BID keyword [message #42215] |
Tue, 18 January 2005 08:03 |
John R. Iverson
Messages: 6
Registered: September 2002
|
Junior Member |
|
|
I've been allocating my own Pixmaps (in a C program) and using IDL's
WINDOW procedure to draw into that Pixmap
(WINDOW, /FREE, /PIXMAP, /SET_X_BID=####). That works pretty well, but
in some circumstances I've seen BadPixmap X Errors come out of the IDL
process.
Now clearly this situation is begging for me to have some timing issues
- I am using XFlush() and IDL's "EMPTY" procedure in an attempt to keep
the two X Displays from getting out of sync.
If I remove my call to WDELETE, I believe I never have this issue.
However, this appears to leak memory on the X Server (my processes run
for a long time).
Anyway there is no documentation about this keyword. Does anybody have
any insight into this issue? I am having a devil of a time reproducing
this problem also, so I'm thinking it's a timing issue.
Thanks!
Rob
|
|
|
|
comp.lang.idl-pvwave archive
Members
Search
Help
Login
Home
