Problem with FORK_ISECT and X Window resize

New Message Reply Date view Thread view Subject view Author view

Scott A. Friedman (friedman++at++ucla.edu)
Wed, 17 Jun 1998 18:02:05 -0700


Hi,

I have a Performer application running under Motif and whenever I use
FORK_ISECT in my program there are problems whenever the window is
resized (manually or programmatically)

mpMode = PFMP_APPCULLDRAW | PFMP_FORK_DBASE | PFMP_FORK_ISECT;

works okay

---

mpMode = PFMP_APP_CULLDRAW | PFMP_FORK_DBASE | PFMP_FORK_ISECT;

Performer does not seem to know about resize - or gets confused - Performer window is messed up. After resize only part of the window is drawn to.

---

mpMode = PFMP_APP_CULL_DRAW | PFMP_FORK_DBASE | PFMP_FORK_ISECT;

crashes with:

X Error of failed request: BadMatch (invalid parameter attributes) Major opcode of failed request: 141 (GLX) Minor opcode of failed request: 17 (X_GLXVendorPrivateWithReply) Serial number of failed request: 146 Current serial number in output stream: 146

which happens while APP is in pfSync( ) - typically several frames *after* my motif resize callback is called (correctly). Is this some kind of Xserver slowness?

---

Normally, I would think that there was some problem with the application but under...

mpMode = PFMP_APP_CULL_DRAW | PFMP_FORK_DBASE ;

Here everything works fine - and has for quite a while now. All APP, CULL, DRAW combinations work so I'm pretty sure it's not some kind of MP data problem.

Also, it does not matter whether a ISECT callback is installed or not - the (mis)behavior occurs either way.

Might there be a small tidbit of information that I am missing here?

Any suggestions are appreciated!

Thanks, Scott Friedman UCLA

======================================================================= List Archives, FAQ, FTP: http://www.sgi.com/Technology/Performer/ Submissions: info-performer++at++sgi.com Admin. requests: info-performer-request++at++sgi.com


New Message Reply Date view Thread view Subject view Author view

This archive was generated by hypermail 2.0b2 on Mon Aug 10 1998 - 17:57:33 PDT

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