home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!haven.umd.edu!darwin.sura.net!sgiblab!sgigate!odin!twilight!zola!fido!fudge!karlton
- From: karlton@fudge.asd.sgi.com (Phil Karlton)
- Newsgroups: comp.sys.sgi
- Subject: Re: IrisGL to GLX changes
- Date: 23 Nov 1992 18:44:06 GMT
- Organization: Silicon Graphics, Inc. Mountain View, CA
- Lines: 27
- Message-ID: <1er8pmINNsfn@fido.asd.sgi.com>
- References: <7013@dove.nist.gov>
- NNTP-Posting-Host: fudge.asd.sgi.com
-
-
- In article <7013@dove.nist.gov>, fred@poly2.nist.gov writes:
- Where can I find a definative list of the functions that are available in IrisGL,
- but which can't be used in a mixed mode (GLX) application.
-
- This should be fairly close. I got it from the GLXwinset man page.
-
- PK
- =======================================================================
- BUGS
- All of the GL routines which access window system controlled features are
- illegal to call for a mixed model window. Not all of these routines
- report errors, so here is a list of the routines which mixed model
- programs cannot call.
-
- qdevice, qread, qtest, qenter, getbutton, getvaluator, setvaluator,
- noise, unqdevice, mapcolor, getmcolor, gconfig, doubelbuffer,
- singlebuffer, RGBmode, cimode, overlay, underlay, acsize, curstype,
- defcursor, setcursor, winopen, wintitle, winposition, winmove,
- foreground, noborder, noport, iconsize, icontitle, keepaspect, maxsize,
- minsize, step, fudge, prefposition, prefsize
-
- The following routines will work, but execute much slower for mixed model
- windows, and this information should be obtained from the window system
- if at all possible. Avoid these routines.
-
- getsize, getorigin, reshapeviewport, getviewport
-