Amaury Aubel (aubel++at++lig.di.epfl.ch)
Fri, 17 Oct 1997 17:39:55 -0600
1) In perfly, just before the Application main loop (main.c) I call one of my
own functions, in which I need to check whether the window (single pipe mode)
is open. I added this line:
while (!pfIsPWinOpen(ViewState->pw[0])) sleep(1);
which causes an endless loop.
- ViewState points to shared memory.
- The window is opened in the draw process, which is set off by a previous call
to pfFrame (or at least that's what I understand).
Could anyone explain to me what I'm doing wrong?
2) Ten days ago I sent the following post:
> Is there a size limitation when loading textures using the frame buffer as a
> source?
>
> pfTexLoadMode(tex, PFTEX_LOAD_SOURCE, PFTEX_SOURCE_FRAMEBUFFER);
> pfTexLoadSize(tex, WIN_X, WIN_Y);
>
> if I set WIN_X/WIN_Y to 32, 64 or 128, no problem. If I set them to 256 or
512,
> my windows manager is killed upon the first texture load.
>
> Is this normal?
> I'm running my app. on an Octane, Irix 6.4, performer 2.0
Since then, I ran the same application on an O2 and an Impact: everything
worked fine, no matter the texture size. Did anyone else experience this on
Octanes?
Thanks for your time,
Amaury
=======================================================================
List Archives, FAQ, FTP: http://www.sgi.com/Technology/Performer/
Submissions: info-performer++at++sgi.com
Admin. requests: info-performer-request++at++sgi.com
This archive was generated by hypermail 2.0b2 on Mon Aug 10 1998 - 17:56:05 PDT