Several libraries define their own codes for they keyboard (GLFW, GTK, GLUT,
etc)
Maybe it would be nice to agree on a standard datatype for keys? This might
also include digital buttons on a joystick, etc...
The Windows API has virtual key codes for this.
Peter Verswyvelen wrote:
Several libraries define their own codes for they keyboard (GLFW, GTK, GLUT,
etc)
Maybe it would be nice to agree on a standard datatype for keys? This might
also include digital buttons on a joystick, etc...
The Windows API has virtual key codes for this.
X windows
But should we use X11 as the standard library then, even on Windows or Mac?
It surely is better than nothing, but it feels a bit weird to install X11
just for using the key codes.
Maybe splitting these keys into a separate package would be a good idea?
On Wed, Aug 26, 2009 at 12:42 PM, Yitzchak
Peter Verswyvelen wrote:
Several libraries define their own codes for they keyboard
(GLFW, GTK, GLUT, etc)
Maybe it would be nice to agree on a standard datatype
for keys?
...The Windows API has virtual key codes for this.
I wrote:
X windows key symbols...
are found in the X11 package
Excerpts from Peter Verswyvelen's message of Wed Aug 26 12:15:14 +0200 2009:
Maybe it would be nice to agree on a standard datatype for keys? This might
also include digital buttons on a joystick, etc...
The synergy project (sourceforge) already does some mapping from Windows
- Linux - Mac
I would already be happy with a low level library that holds the union of
all keys, assigning them unique codes. So you would have keys like Apple,
Amiga, Windows, Start, Popup, LeftControl, RightControl, etc... No mapping
is done at the low level.
Then one would need an OS dependent interface to
