Re: No Graphics

New Message Reply Date view Thread view Subject view Author view

Michael Jones (mtj++at++babar)
Mon, 24 Jan 1994 09:16:19 -0800


On Jan 24, 12:36am, Jim Helman wrote:
> Subject: Re: No Graphics
:
:> I beg to differ with Michael Jones, I had to do this for a DIS interface
:> we did. Basiclly, what I did is not call pfFrame or pfSync in the main
loop.
:
:Performer always opens a noport() window for the vertical
:sync clock at pfConfig time. I'm not positive, but I don't
:think this will fly on a server. For 1.2 or later we plan
:to fix it so that a Performer database conversion
:application can run without any graphics whatsoever.
:
:-jim helman

My reputation is saved ;-)

Actually, what I meant is what Jim's getting at above. When the original
questioner asked about "intersections on a server," I took that to mean
something different than "an intersection server." Since being too literal
in communication is one of my common mistakes, I just went with the flow
when the always wise Dr. David Pratt, PhD, Marine, mentioned his success,
thinking that the questioner would clarify if needed.

What does this mean?

 If you have an SGI "server" (machine with *no* graphics HW or SW) then
 IRIS Performer is not going to be happy when you call pfConfig() -- no
 doubt about it. I want to change this attitude, and the idea of calling
 pfMultipipe(0) to indicate your no-graphics-whatsoever intentions seems
 like the best way to me. Look for this (or a better) mechanism in the
 future. Stubbing the GL calls is the only way until this happens.

 If you want to use an SGI graphic workstation as an "intersection server"
 then you are home free. Dave Pratt provides all the instructions that you
 will need to do this now.

Thanks to Dave Pratt and Jim Helman for delving into the facts out of such
an innocent question.

-- 

Be seeing you, mtj++at++sgi.com 415.390.1455 M/S 7L-590 Michael Jones Silicon Graphics, Advanced Graphics Division 2011 N. Shoreline Blvd., Mtn. View, CA 94039-7311


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:09 PDT

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