Browse Prior Art Database

Input Synchronization Process for a 3D Drawing Widget Based in X Windows and GL

IP.com Disclosure Number: IPCOM000120918D
Original Publication Date: 1991-Jun-01
Included in the Prior Art Database: 2005-Apr-02
Document File: 1 page(s) / 35K

Publishing Venue

IBM

Related People

Haletky, EL: AUTHOR [+2]

Abstract

The problem of integrating two very different input strategies becomes apparent when two APIs are used. The X Windows System has an event driven strategy and GL contains a device-driven strategy. The two do not always match. However, the vast majority of GL devices come from the same dispatcher as X Events. These devices are the concern of this process. (Image Omitted)

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 100% of the total text.

Input Synchronization Process for a 3D Drawing Widget Based in X
Windows and GL

      The problem of integrating two very different input strategies
becomes apparent when two APIs are used.  The X Windows System has an
event driven strategy and GL contains a device-driven strategy.  The
two do not always match. However, the vast majority of GL devices
come from the same dispatcher as X Events.  These devices are the
concern of this process.

                            (Image Omitted)

      The X Events from the dispatcher need to be translated to GL
devices if, and only if, the Event occurred within the GL window.  If
the event can be translated, then the event is passed back to an
application as a device.  If the event occurs outside of the GL
window or is not translatable, then the event is passed back to the
application as an X Event.

      The process outlined solves the problem of having two
distinctly different input strategies with the same source of
information.

      Disclosed anonymously.