<DEL> key is sending an extra char when NumLock is ON

penna at bb.com.br penna at bb.com.br
Wed Feb 1 05:56:47 CST 2006

zhilla wrote:

> >         I am going to open a bug at bugzilla and send the 
> > (just the piece where the stuff happens).
> dont, its already opened for a while.
> http://bugs.winehq.org/show_bug.cgi?id=2400
> there is a working patch there... but some people claim its not very 
> good since it hardwires the key to code.
> somebody should really look into this already... half of solution is 
> already there :)

Sorry ... I did a search and found nothing so I have already opened a bug. 

Anyway, they already marked it as duplicated.

Well, I was taking a look into it but I am going to need some 
explanations. If someone could provide (or point me out) I will be very 

1) Does X send two separate sequences of keys for some type of keys (<del> 
for example)?
2) The translation from keycode to virtual key in wine is a little bit 
difficult to understand (at a first glance). Is there an email or any 
documentation explaining that (besides the source code ;-))? Otherwise it 
will take some weeks just to understand how it works 8-( ....
3) The patch proposed at bug #2400 works very well, however it seems to be 
not in a correct place (at first glance) .... 
4) There is a "gap" in the nonchar_key_scan[] array just at the 
VK_SEPARATOR equivalent position (0xFFAC) on the nonchar_key_vkey[] 
position (see the question mark below - as in source code):

static const WORD nonchar_key_vkey[256]=
0, 0, 0, 0, 0, 0, 0, 0,               /* FFA8 */

static const WORD nonchar_key_scan[256]=
0x00, 0x00, 0x37, 0x4e, /* ? */ 0, 0x4a, 0x53, 0x135,     /*FFA8 */

        The VK_SEPARATOR is the <del> and/or <,> key at the numeric pad. 
Any relation with the problem?

Ulisses de Sousa Penna
Analista Consultor - Banco do Brasil
Fone: +55-61-3310-6320   Fax: +55-61-3310-6435

More information about the wine-devel mailing list