From: Allen Bierbaum (allenb++at++vrac.iastate.edu)
Date: 06/12/2001 10:32:55
I have an application where I don't know the complete window
configuration at startup. As such I just get handles to all the
pfPipe's that I could use in the system and then I add pfPipeWindow's
later while the application is running.
This works except for one major problem.
If I have a pfPipe that I have allocated but not assigned any
pfPipeWindows, then Performer pulls up a big black window on that pipe
at what I assume to be the first pfFrame() call. I am assuming that
this is Performer automatically allocating a pfPipeWindow (and
associated channel) for the pfPipe that has none assigned.
So my questions are these:
- Is there any way to keep the "black window" from coming up?
- If not, is there any way to automatically remove it when I actually
assign a pfPipeWindow to that pipe.
On a related note, it would be really nice if I didn't have to even know
(at application startup) the pfPipes I wanted to use. I would like to
be able to grab a new pfPipe while an application is actually running.
But from some test I have run I don't think that is possible in the
current version of Performer.
-Allen
--Allen Bierbaum ISU -- Virtual Reality Applications Lab Research Assistant
This archive was generated by hypermail 2b29 : Tue Jun 12 2001 - 10:29:00 PDT