Dan Labute (dan++at++discreet.com)
Thu, 01 Oct 1998 11:55:12 -0400
Thanks for the code snippet, Chris. Unfortunately, *our* code still
doesn't work. I'm doing everything you do, except that I'm not
using Motif (just plain X), and our program does a few more things in
between. What happens to us is that the setWSWindow method inexplicably
never returns. Obviously the conditions for caling the function are not
met. What those are is a complete mystery. My guess has to do with the
state of the X Window. Does it need to be mapped or created?
As for the Display parameter passed to setWSWindow, you create one in
your rendering process (via XOpenDisplay). Doesn't Performer create one
on its own? If so, when? I tried using Performer's display *and*
creating my own, but no luck. Performer's lone sample code snippet
passes NULL as the Display parameter ... tried that too. What about
calling sequence ... does that matter?
Just after posting my original question, I recieved a number of letters
asking me to forward the solution if and when I get it. Clearly, I'm
not the only one struggling with Performer in this area. Why is
Performer's
documentation and sample code so inadequate?
I have yet to hear from any of the Performer guys on this ...
Any thoughts?
Dan Labute
Discreet Logic
e-mail: dan++at++discreet.com
Tel.: (514)-954-7549
This archive was generated by hypermail 2.0b2 on Thu Oct 01 1998 - 08:55:39 PDT