Le lundi 27 juillet 2009 à 12:19 +1000, Timothy S. Nelson a écrit :
On Sat, 25 Jul 2009, Jim Gettys wrote:
For curiosity's sake, have people actually seen keyboards with more than
248
keys?
- Jim
No, but I had this idea, see, of having one keyboard for each
On Sat, Jul 25, 2009 at 08:29:40PM -0400, Jim Gettys wrote:
I guess I'm still confused...
So they'd show up as different devices with time; each time you get
notification that the keysym mapping for the keycodes have changed.
Why is there a problem?
It makes things overly complicated.
On Sun, 2009-07-26 at 18:41 +1000, Peter Hutterer wrote:
On Sat, Jul 25, 2009 at 08:29:40PM -0400, Jim Gettys wrote:
I guess I'm still confused...
So they'd show up as different devices with time; each time you get
notification that the keysym mapping for the keycodes have changed.
Peter Hutterer wrote:
On Sat, Jul 25, 2009 at 08:29:40PM -0400, Jim Gettys wrote:
I guess I'm still confused...
So they'd show up as different devices with time; each time you get
notification that the keysym mapping for the keycodes have changed.
Why is there a problem?
It makes things
On Sun, Jul 26, 2009 at 09:10:52AM -0400, Jim Gettys wrote:
Embedded systems, however, are just as likely to expose raw scancodes;
their evdev driver will be having to stand on their head to fit the PC
model, which we may or may not consider to be a 'good thing'.
It's the kernel's
- What's the purpose of using XGetEventData now instead of plain
GenericEvents?
libX11 has an internal maximum size for events which was the cause for
events having to store pointers to external memory locations. this exposed a
huge memory leak in naive applications, the cookie approach
On Sun, Jul 26, 2009 at 09:10:52AM -0400, Jim Gettys wrote:
Peter Hutterer wrote:
On Sat, Jul 25, 2009 at 08:29:40PM -0400, Jim Gettys wrote:
I guess I'm still confused...
So they'd show up as different devices with time; each time you get
notification that the keysym mapping for the
On Sun, Jul 26, 2009 at 06:47:44PM +0200, Florian Echtler wrote:
- What's the purpose of using XGetEventData now instead of plain
GenericEvents?
libX11 has an internal maximum size for events which was the cause for
events having to store pointers to external memory locations. this
On Sat, 25 Jul 2009, Jim Gettys wrote:
For curiosity's sake, have people actually seen keyboards with more than 248
keys?
- Jim
No, but I had this idea, see, of having one keyboard for each hand,
and merging their events together at the kernel level.
:)
On Mon, Jul 27, 2009 at 12:19:13PM +1000, Timothy S. Nelson wrote:
On Sat, 25 Jul 2009, Jim Gettys wrote:
For curiosity's sake, have people actually seen keyboards with more
than 248 keys?
- Jim
No, but I had this idea, see, of having one keyboard for each hand, and
On Mon, Jul 27, 2009 at 01:00:45PM +1000, Timothy S. Nelson wrote:
On Mon, 27 Jul 2009, Peter Hutterer wrote:
On Mon, Jul 27, 2009 at 12:19:13PM +1000, Timothy S. Nelson wrote:
On Sat, 25 Jul 2009, Jim Gettys wrote:
For curiosity's sake, have people actually seen keyboards with more
than
On Sat, 25 Jul 2009, Peter Hutterer wrote:
- When will the XI2 API be finalized?
I think it is now, though I have to have a final glossover on monday to make
sure I didn't forget anything.
Quick question: What's the maximum number of keys per keyboard it
supports?
Thanks :)
On Sat, Jul 25, 2009 at 05:43:50PM +1000, Timothy S. Nelson wrote:
On Sat, 25 Jul 2009, Peter Hutterer wrote:
- When will the XI2 API be finalized?
I think it is now, though I have to have a final glossover on monday to make
sure I didn't forget anything.
Quick question: What's the
On Sat, 2009-07-25 at 12:12 -0400, Jim Gettys wrote:
For curiosity's sake, have people actually seen keyboards with more than
248 keys?
No, but plenty with keycodes 256
(Most TV remotes fail in this category, and I still am waiting for limit
of 256 keycodes to be lifted)
-
That isn't a good reason: keycodes are arbitrary, a simple table lookup
to remap them to 8-255 is an easy solution, much easier than the
alternatives, unless I'm missing something...
- Jim
Maxim Levitsky wrote:
On Sat, 2009-07-25 at 12:12 -0400, Jim Gettys wrote:
For
Le samedi 25 juillet 2009 à 13:31 -0400, Jim Gettys a écrit :
That isn't a good reason: keycodes are arbitrary, a simple table lookup
to remap them to 8-255 is an easy solution, much easier than the
alternatives, unless I'm missing something...
keycodes are not arbitrary, the codes 255 have
Nicolas,
In the original X11 design and keyboard system, keycodes are arbitrary,
and need not have anything to do with the codes produced by the hardware
(which are often quite baroque, and often formed by multiple character
transmissions from the keyboard to the host).
Just because the
I guess I'm still confused...
So they'd show up as different devices with time; each time you get
notification that the keysym mapping for the keycodes have changed.
Why is there a problem?
- Jim
Alan Cox wrote:
Ergo my question on whether anyone has ever actually
On Sat, Jul 25, 2009 at 07:59:54PM +0300, Maxim Levitsky wrote:
On Sat, 2009-07-25 at 12:12 -0400, Jim Gettys wrote:
For curiosity's sake, have people actually seen keyboards with more than
248 keys?
No, but plenty with keycodes 256
(Most TV remotes fail in this category, and I still am
On Sun, 2009-07-26 at 10:37 +1000, Peter Hutterer wrote:
On Sat, Jul 25, 2009 at 07:59:54PM +0300, Maxim Levitsky wrote:
On Sat, 2009-07-25 at 12:12 -0400, Jim Gettys wrote:
For curiosity's sake, have people actually seen keyboards with more than
248 keys?
No, but plenty with
Hello everybody,
I recently updated my Xserver, libXI etc. to the most recent master and
this broke my XI2 FreeGLUT patch again. While I'm trying to get it
working again, I have two questions:
- What's the purpose of using XGetEventData now instead of plain
GenericEvents?
- When will the XI2 API
21 matches
Mail list logo
