On Tue, Mar 9, 2010 at 00:58, Hans-Peter Diettrich wrote:
> JoshyFun schrieb:
>
>> AK> Although I have no particular need for this change, I support it
>> AK> on the general principle. I would go even further and call KeyPress
>> AK> _before_ built-in handler, so that user code could turn off
>> A
JoshyFun schrieb:
AK> Although I have no particular need for this change, I support it
AK> on the general principle. I would go even further and call KeyPress
AK> _before_ built-in handler, so that user code could turn off
AK> default handling by setting the key code to zero.
I'm not sure that
Hello Lazarus-List,
Sunday, March 7, 2010, 4:12:59 AM, you wrote:
AK> Although I have no particular need for this change, I support it
AK> on the general principle. I would go even further and call KeyPress
AK> _before_ built-in handler, so that user code could turn off
AK> default handling by se
On Sun, Mar 7, 2010 at 09:23, JoshyFun wrote:
> Hello Lazarus-List,
>
> Maybe somebody had noted that all keys that perform some action in a
> DBGrid by default are never passed to the KeyPress event, like return,
> delete, keyup, keydown,... The reason is that this actions are handled
> in the ke
Hello Lazarus-List,
Maybe somebody had noted that all keys that perform some action in a
DBGrid by default are never passed to the KeyPress event, like return,
delete, keyup, keydown,... The reason is that this actions are handled
in the keydown event and to note that they are handled by the DBGri
