Path: utzoo!news-server.csri.toronto.edu!cs.utexas.edu!uunet!orca!undies!pmartz From: pmartz@undies.dsd.es.com (Paul Martz) Newsgroups: comp.windows.x Subject: Re: PEX Information Wanted Message-ID: <1991Mar4.212402.6543@dsd.es.com> Date: 4 Mar 91 21:24:02 GMT References: <1991Feb28.182621.19253@dsd.es.com> Sender: usenet@dsd.es.com Reply-To: pmartz@undies.dsd.es.com (Paul Martz) Organization: Evans & Sutherland Computer Corp., Salt Lake City, UT Lines: 33 Nntp-Posting-Host: 130.187.85.56 In article , gregc@cgl.ucsf.edu (Greg Couch) writes: > Does the PEX standard specify how the PHIGS API and X work together? > Specifically, if you want to use X events for input, could you still > use PHIGS for picking? > > The current DEC PHIGS product provides such a method, a pphittest > function to do picking in an PHIGS output-only workstation. And I've > heard that in IBM's graPHIGS, you can pass an X event to the graPHIGS > widget for picking. > > Please tell me that this will be standardized soon. > > - Greg Couch > gregc@cgl.ucsf.edu In addition to the good points Rich Thomson has already made concerning this issue, I just wanted to add that the PEX protocol itself makes no rules concerning input. It provides some requests to ease the implementation of picking, but how picking is implemented is entirely up to the API library. If your favorite PEX-based PHIGS won't let you use both PHIGS picking and X input events at the same time, that's a restriction the API implementors have made, not the PEX protocol itself. I believe the PEX-SI has indeed made this restriction (i.e., PHIGS input and X input may not be intermixed) but I may be wrong... Anyone from the SI team read this? Marty? Cheryl? Tom? Lisa? Also, FYI, the PEX protocol defines no new events. -- -paul pmartz@dsd.es.com Evans & Sutherland