Starbase Functionality

Commands Not Supported (NO-OPS)

The following commands are not supported. These commands will not generate Starbase errors.

await_retrace               depth_cue_range
backface_control            hidden_surface
bank_switch                 light_ambient
bf_control                  light_attenuation
bf_fill_color                interior_style (INT_OUTLINE,  INT_POINT)
bf_interior_style           light_model
bf_perimeter_color          light_source
bf_perimeter_type           light_switch
bf_perimeter_repeat_length  shade_mode
bf_surface_coeficients      shade_range
bf_surface_model            surface_coefficient
define_trimming_curve       surface_model
depth_cue                   viewpoint
depth_cue_color             zbuffer_switch

Gescapes

The following gescapes are supported by the sox11 driver. Detailed information on these gescapes can be found in Appendix A of this manual.

All other gescapes are used to control the input model. These gescapes are described in the following section (Input Model).

Input Model

A Starbase application is free to gopen an X11 window with the OUTDEV flag and utilize the X11 library calls to perform input. The Starbase application may also choose to use Starbase library input routines if the INDEV or OUTINDEV flags are used as arguments to gopen. A program should use exclusively either X11 input routines or Starbase input routines. Using both within the same application may cause an X error.

The sox11 input model represents X11 as a virtual device including a keyboard and an X11 pointer. The keyboard is accessed as a CHOICE device while the X11 pointer is accessed as a CHOICE and a LOCATOR device.

The default mode returns HP Roman-8 keycodes. This is the "cooked" mode for input keystrokes. Special function keys and control keys are not supported in this mode and their return value is undefined. These keys generate a two-byte sequence. The sample_choice and request_choice functions will return one of the two bytes. The other byte is discarded. (As to which byte is retained, this is undefined.)

"Raw" input for this driver consists of an integer composed of two parts. The first half (or upper two bytes) specify the state of the keyboard at the time of the button or key press (that is, an "Extend char" or "CTRL" key is depressed at the time of the event). The lower half (or last two bytes) is a server dependent key symbol which, for this server, identifies each key or button.

In "cooked" mode the X11 pointer buttons are represented by values one through five, corresponding to the X11 pointer button used. Button one typically represents the left-hand button, two represents the middle button, etc. In "raw" mode the value returned by a button is determined by the "raw" value returned by the X11 server for that button.

The X Window System input device can also return raw keycodes. These codes are the unmapped keycodes and the keyboard state information returned by the X11 server. The input model can be placed in "raw" mode using the XN_INPUT_RAW gescape with a value of TRUE in the first argument of the gescape. Similarly the input model can be reset to the default "cooked" mode using the XN_INPUT_RAW gescape with the first argument containing the value of FALSE.

By default the sox11 driver returns only events associated with the key press and button press input. An application can request input events associated with both presses and releases of keys or buttons. Requesting the release events associated with X11 pointer buttons or keys can be controlled independently.

An application can request events associated with both button presses and button releases by using the XN_BUTTON_RELEASE gescape. The value returned by a button release event is the negative value of the corresponding button press event.

An application can request to be sent events associated with both key presses and key releases using the XN_KEY_RELEASE gescape. The value returned by a key release event is the negative value of the corresponding key press event.

Both of these gescapes are set by sending a first argument of TRUE. Both gescapes are reset by sending a first argument of FALSE.

HP-HIL pointing devices controlled by the X11 server are mapped into the virtual X11 pointer device represented by the input model. The X11 pointer cannot be controlled by both the X11 server, sox11, and the HP-HIL device driver at the same time. If the pointer device is to be controlled by the Starbase HP-HIL device driver, then the pointer must be excluded from the X11 server.