pfPipeWindow fun

New Message Reply Date view Thread view Subject view Author view

From: Rob Krajcarski (rjkrajca++at++dciem.dnd.ca)
Date: 11/13/2001 06:54:49


Hello,

I'm trying to write an application that uses Performer to render a scene within
a GUI. There are two different types of canvases I want to use, where some of
the differences are resolution, number of channels, and parent X window.
Currently I am using two pfPipeWindows. Everything works except when I create
the second one performance deteriorates (going from 10ms draw time to about
130ms).

I've seen all of the comments about the chef beating eggs and I
understand that problem (two active pfPipeWindows causes the dreaded context
switch), but in this application I can be guaranteed that only
one pfPipeWindow is visible at a given time.

I have read/experienced a number
of problems with opening/closing/reopening pfPipeWindows so I currently never
actually close them, but I do detach the channels from the scene, and from the
pfPipeWindow in an effort to prevent any context switching...I'm pretty sure my
strategy still doesn't work...

Can anyone offer me some advice on how to:
  a) find out if context switching is my problem
  b) prevent a pfPipeWindow from trying to grab the graphics context
  c) offer any other hypothesis to my problem

I'm running Performer 2.2.11 within a Fltk GUI on IRIX 6.5.11

Thanks for any help that you can offer...


New Message Reply Date view Thread view Subject view Author view

This archive was generated by hypermail 2b29 : Tue Nov 13 2001 - 07:04:14 PST

This message has been cleansed for anti-spam protection. Replace '++at++' in any mail addresses with the '@' symbol.