gilmore@vax1.acs.udel.EDU (Scott Gilmore) (07/11/90)
Does anyone know what the PHIGS standard defines as the structure display priority range (last argument to PPOST in Fortran binding)? I have looked through the official ANSI functional description, as well as the October 1987 draft ANSI Fortran-PHIGS binding document, and cannot find any mention of the valid range. I am using Template's FIGARO and IBM's graPHIGS. The FIGARO version 1 manual defines the range from 0.0 -> 1.0, FIGARO version 2 defines it as -1.0 -> 31.0, graPHIGS prioritizes by view rather than structure. No agreement anywhere. I am writing a Fortran application which must adhere as closely as possible to the ANSI standard for PHIGS. Any information would be greatly appreciated. Although I do read this group daily, Email responses are preferred unless you feel it is of general interest. -- --- Scott Gilmore gilmore@vax1.udel.edu Mechanical Engineering and Center for Composite Materials, U. of Delaware
thomson@cs.utah.edu (Rich Thomson) (07/20/90)
In article <6722@vax1.acs.udel.EDU> gilmore@vax1.udel.edu (Scott Gilmore) writes: >Does anyone know what the PHIGS standard defines as the structure display >priority range (last argument to PPOST in Fortran binding)? >through the official ANSI functional description, as well as the October 1987 >draft ANSI Fortran-PHIGS binding document, and cannot find any mention of the >valid range. The routine INQUIRE NUMBER OF DISPLAY PRIORITIES SUPPORTED returns an integer indicating the number of display priorities supported. If the integer is zero, the workstation can support an arbitrary number of display priorities. If the integer is non-zero, then that is the number of display priorities supported by the workstation. Now of course, this doesn't tell you the accepted range for the floating point argument to POST STRUCTURE. This may be a shortcoming of the standard document in that this is not clearly defined. My understanding (which could be flawed ;-) is that the values of the floating point parameter are unconstrained, but the *number* of different priority values you can post a structure with are returned by INQUIRE NUMBER OF DISPLAY PRIORITIES. It could very well be that this is the case and the PHIGS implementations you mention in your post are not strictly adhering to the standard in this fashion. PHIGS as a standard is complex enough that getting all the nooks and crannies filled is quite a task, so these kind of deviations from the 'standard' are not to be interpreted as sloppy work of the implementor. -- Rich Rich Thomson thomson@cs.utah.edu {bellcore,hplabs,uunet}!utah-cs!thomson ``If everybody is thinking the same thing, is anybody thinking?'' --Bob Johnson