I'm giving Joystick support to GGL, and it's almost done, but I
found a little problem. The joystick buttons are reported in a evKey event,
so, the GGL keyboard device gets its own events and also the joystick
ones...
I open the joystick by opening a gii_input_t of type
Rubén wrote:
I'm giving Joystick support to GGL, and it's almost done, but I
found a little problem. The joystick buttons are reported in a evKey event,
so, the GGL keyboard device gets its own events and also the joystick
ones...
I open the joystick by opening a
It's been 3 days since the apocalypse and all goes well.
I've sucessfully run dual monitor support by buying 2 matrox mileninum 200SD
cards, and ramming them in the same system, then booting a 2.3.3x kernel
with all the matrox stuff enabled.
i then ran a "tile" demo spanning the monitor test
I'm a bit confused about how XGGI handles keyboard input.
With my DirectX port of GII, I set sym=label and the appropriate
modifiers.
Running XGGI and xterm, I only get lowercase letters. Looking at
Xserver\hw\ggi\keyboard.c, which I take to be the keyboard handler for
XGGI, I don't see
It does crash my system/keyboard when i try to quit the test pattern, but
that's probably cuase i'm using a old library.
That's strange. Please enable Magic SysRq for debugging purposes and then
help us to track that one down.
Now, on a more phychotic note... I read a note about somone
I know that I can access to event-any.origin to distingish between
keyboard and joystick events, but how can I know which value is the keyboard
one and which is the joystick one? In a few proofs that I've made the
keyboard events had the 0100 value and the joystick the 0200, but I don't
On 2000/Jan/04, Andreas Beck wrote:
I know that I can access to event-any.origin to distingish between
keyboard and joystick events, but how can I know which value is the keyboard
one and which is the joystick one? In a few proofs that I've made the
keyboard events had the 0100 value
