Re: Performer and OSF/Motif

New Message Reply Date view Thread view Subject view Author view

Wade Olsen (wade++at++fnord)
Mon, 10 Jan 1994 17:18:22 -0800

On Jan 10, 11:46am, james covington wrote:
> Subject: Performer and OSF/Motif
> Last week I wrote:
>
> ->I have reviewed Wade Olsen's sample program which shows how to run Performer
> ->inside a Motif application. However when I tried to modify a larger existing
> ->Performer application (one which used the standard winopen() call in the
> ->pfInitfunc) to run in this manner, I received GL error #114 (ERR_NOGRAPHICS)
> ->when I called the GLXlink function. Can you help explain what causes error
> ->#114, and what I could possibly do to avoid it?
>
> I want to thank you for the EXTREMELY fast response to my last posting
> on this subject. I sent the mail late on Friday, and really didn't expect
> any reply before the beginning of the week.
>
> Your suggestions were very helpful, and I am still working on the problem.
>
> At this point, I have taken a step backward and simply compiled Wade Olsen's
> sample program with my original makefile and include files. When I ran the
> program, it ran "successfully," but generated the error message:
>
> ERROR #4 ortho2: ERR_BADWINDOW
>

The sample program has definitions for the GL routines getsize and
getorigin. These are faster versions than the GL counterparts because the
GL must make a request to the X server and wait for a responce. But since
this application watches for resize events it knows what the window size
is. But if performer asks for the window size before the app gets some
indication of the window size then performer might be using garbage from
my version of getsize. A quick and resonable fix might be to stick some
default values in win_x_size and win_y_size right after they are allocated
out of shared memory. I wrote this example using Perf1.1 on IRIX 5.*.
I'll bet that compiler differences and not initializing these variables
is the culprit. Sorry.

Regarding applying this approach to an existing application, be careful!
The order things happen in is very critical. It might be easier to take
a working program and make incremental changes (the example for instance)
and morph it into your final application. Then again, maybe not :-).

I'm trying to come up with a multi-pipe version of this. I'll post it here
when I can get it working.

> twice, once when I called pfConfig, and again when I called XtRealizeWidget.
> Can you tell me what conditions generate this error?
>
> I am running Performer 1.0 and Motif 1.1 on an IRIS 4D/440 Reality Engine
> with IRIX 4.0.5G. Thanks.
>
> James Covington LT USN
> Naval Postgraduate School
> Monterey CA
>
>
>
>
>
>-- End of excerpt from james covington

-- 
-------------------------------------------------------------------------------
Wade Olsen, wade++at++sgi.com, 415-390-1023, Silicon Graphics Computer Systems

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:50:08 PDT

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