Alexandre Hedreville
2005-07-21 08:34:28 UTC
Hola a todos...
Me surge la duda de como distinguir que el usuario a pulsado la tecla .
(punto) del teclado numerico (teclado extendido) de cuando pulsa la tecla .
(punto) del teclado normal (teclado estandard)...
No si os habeis fijado en como trabaja Excel, cuando pulsas . (punto) en el
teclado numerico te envia , (coma) pero cuando pulsas . (punto) en el
teclado normal te envia . (punto)
Esto es muy comodo cuando estas trabajando con cantidades, numeros o
monedas...
En VFP las funciones INKEY(), LASTKEY(), READKEY() y en evento KeyPress
devuelven el mismo valor para las dos teclas..
por lo que parece que desde el propio VFP no es posible saber cual de las
dos se ha pulsado...
Por lo que he investigado parece que la solucion podrias ser... Interceptar
via API el teclado antes de que llegue a la aplicación, cambiarla y darle el
mensaje adecuado a VFP
El problema es que no tengo base suficiente para llevarlo a cabo... ¿Alguien
sabe como resolverlo?...
Examinar el siguiente extracto... sobre todo la explicacion sobre.... el bit
24
24
Specifies whether the key is an extended key, such as the right-hand ALT and
CTRL keys that appear on an enhanced 101- or 102-key keyboard. The value is
1 if it is an extended key; otherwise, it is 0.
The window that receives the message can distinguish between these two
contexts by checking the context code in the lParam parameter.
WPARAM wParam
LPARAM lParam;
Parameters
wParam
Specifies the virtual-key code of the key being pressed.
lParam
Specifies the repeat count, scan code, extended-key flag, context code,
previous key-state flag, and transition-state flag, as shown in the
following table.
0-15
Specifies the repeat count for the current message. The value is the number
of times the keystroke is autorepeated as a result of the user holding down
the key. If the keystroke is held long enough, multiple messages are sent.
However, the repeat count is not cumulative.
16-23
Specifies the scan code. The value depends on the OEM.
24
Specifies whether the key is an extended key, such as the right-hand ALT and
CTRL keys that appear on an enhanced 101- or 102-key keyboard. The value is
1 if it is an extended key; otherwise, it is 0.
25-28
Reserved; do not use.
29
Specifies the context code. The value is 1 if the ALT key is down while the
key is pressed; it is 0 if the WM_SYSKEYDOWN message is posted to the active
window because no window has the keyboard focus.
30
Specifies the previous key state. The value is 1 if the key is down before
the message is sent, or it is 0 if the key is up.
31
Specifies the transition state. The value is always 0 for a WM_SYSKEYDOWN
message.
Return Value
An application should return zero if it processes this message.
The DefWindowProc function examines the specified key and generates a
WM_SYSCOMMAND message if the key is either TAB or ENTER.
When the context code is zero, the message can be passed to the
TranslateAccelerator function, which will handle it as though it were a
normal key message instead of a character-key message. This allows
accelerator keys to be used with the active window even if the active window
does not have the keyboard focus.
Because of automatic repeat, more than one WM_SYSKEYDOWN message may occur
before a WM_SYSKEYUP message is sent. The previous key state (bit 30) can be
used to determine whether the WM_SYSKEYDOWN message indicates the first down
transition or a repeated down transition.
For enhanced 101- and 102-key keyboards, enhanced keys are the right ALT and
CTRL keys on the main section of the keyboard; the INS, DEL, HOME, END, PAGE
UP, PAGE DOWN, and arrow keys in the clusters to the left of the numeric
keypad; and the divide (/) and ENTER keys in the numeric keypad. Other
keyboards may support the extended-key bit in the lParam parameter.
This message is also sent whenever the user presses the F10 key without the
ALT key.
Notification Requirements
Me surge la duda de como distinguir que el usuario a pulsado la tecla .
(punto) del teclado numerico (teclado extendido) de cuando pulsa la tecla .
(punto) del teclado normal (teclado estandard)...
No si os habeis fijado en como trabaja Excel, cuando pulsas . (punto) en el
teclado numerico te envia , (coma) pero cuando pulsas . (punto) en el
teclado normal te envia . (punto)
Esto es muy comodo cuando estas trabajando con cantidades, numeros o
monedas...
En VFP las funciones INKEY(), LASTKEY(), READKEY() y en evento KeyPress
devuelven el mismo valor para las dos teclas..
por lo que parece que desde el propio VFP no es posible saber cual de las
dos se ha pulsado...
Por lo que he investigado parece que la solucion podrias ser... Interceptar
via API el teclado antes de que llegue a la aplicación, cambiarla y darle el
mensaje adecuado a VFP
El problema es que no tengo base suficiente para llevarlo a cabo... ¿Alguien
sabe como resolverlo?...
Examinar el siguiente extracto... sobre todo la explicacion sobre.... el bit
24
24
Specifies whether the key is an extended key, such as the right-hand ALT and
CTRL keys that appear on an enhanced 101- or 102-key keyboard. The value is
1 if it is an extended key; otherwise, it is 0.
The window that receives the message can distinguish between these two
contexts by checking the context code in the lParam parameter.
WPARAM wParam
LPARAM lParam;
Parameters
wParam
Specifies the virtual-key code of the key being pressed.
lParam
Specifies the repeat count, scan code, extended-key flag, context code,
previous key-state flag, and transition-state flag, as shown in the
following table.
0-15
Specifies the repeat count for the current message. The value is the number
of times the keystroke is autorepeated as a result of the user holding down
the key. If the keystroke is held long enough, multiple messages are sent.
However, the repeat count is not cumulative.
16-23
Specifies the scan code. The value depends on the OEM.
24
Specifies whether the key is an extended key, such as the right-hand ALT and
CTRL keys that appear on an enhanced 101- or 102-key keyboard. The value is
1 if it is an extended key; otherwise, it is 0.
25-28
Reserved; do not use.
29
Specifies the context code. The value is 1 if the ALT key is down while the
key is pressed; it is 0 if the WM_SYSKEYDOWN message is posted to the active
window because no window has the keyboard focus.
30
Specifies the previous key state. The value is 1 if the key is down before
the message is sent, or it is 0 if the key is up.
31
Specifies the transition state. The value is always 0 for a WM_SYSKEYDOWN
message.
Return Value
An application should return zero if it processes this message.
The DefWindowProc function examines the specified key and generates a
WM_SYSCOMMAND message if the key is either TAB or ENTER.
When the context code is zero, the message can be passed to the
TranslateAccelerator function, which will handle it as though it were a
normal key message instead of a character-key message. This allows
accelerator keys to be used with the active window even if the active window
does not have the keyboard focus.
Because of automatic repeat, more than one WM_SYSKEYDOWN message may occur
before a WM_SYSKEYUP message is sent. The previous key state (bit 30) can be
used to determine whether the WM_SYSKEYDOWN message indicates the first down
transition or a repeated down transition.
For enhanced 101- and 102-key keyboards, enhanced keys are the right ALT and
CTRL keys on the main section of the keyboard; the INS, DEL, HOME, END, PAGE
UP, PAGE DOWN, and arrow keys in the clusters to the left of the numeric
keypad; and the divide (/) and ENTER keys in the numeric keypad. Other
keyboards may support the extended-key bit in the lParam parameter.
This message is also sent whenever the user presses the F10 key without the
ALT key.
Notification Requirements
--
Alexandre Hédréville
León - SPAIN
***@teleline.es (e-maill)
Nothing runs like the Fox...
Alexandre Hédréville
León - SPAIN
***@teleline.es (e-maill)
Nothing runs like the Fox...