Re: [AD] Bug in readkey() with numeric keypad?

Re: [AD] Bug in readkey() with numeric keypad?

[ Thread Index | Date Index | More lists.liballeg.org/allegro-developers Archives ]

To: <alleg-developers@xxxxxxxxxx>
Subject: Re: [AD] Bug in readkey() with numeric keypad?
From: "Chris Jones" <cj@xxxxxxxxxx>
Date: Sat, 3 Dec 2005 11:46:06 -0000

> This will leave the KEY_* untouched, and simply change the ASCII
> from numerical keys to 0, in case NumLock is on, right?
>
> I think we should apply it to both branches then..

It will leave the scancode (upper byte) untouched, but simply change the
ASCII value to 0 if numlock is off.

Follow-Ups:
- Re: [AD] Bug in readkey() with numeric keypad?
  - From: Chris Jones

References:
- [AD] Bug in readkey() with numeric keypad?
  - From: Chris Jones
- Re: [AD] Bug in readkey() with numeric keypad?
  - From: Elias Pschernig
- Re: [AD] Bug in readkey() with numeric keypad?
  - From: Chris Jones
- Re: [AD] Bug in readkey() with numeric keypad?
  - From: Elias Pschernig

Messages sorted by: [ date | thread ]
Prev by Date: Re: [AD] Bug in readkey() with numeric keypad?
Next by Date: Re: [AD] ChangeLogs on website?
Previous by thread: Re: [AD] Bug in readkey() with numeric keypad?
Next by thread: Re: [AD] Bug in readkey() with numeric keypad?

Mail converted by MHonArc 2.6.19+

http://listengine.tuxfamily.org/