🚀 go-pugleaf

Test1:
Create a new GUI app with a form and 4 buttons on  it
and code your formkeydown event handler (don't forget
KeyPreview = true).
You'll see that the FormKeyDown event is never fired
for the arrow keys, ENTER or TAB (but it is fired for
ESC or SPACE, for instance).
You might even code a ButtonKeyDown event it will
have the same behavior.

Test2:
Now drop a memo on the form above and you'll see
the key event is fired when the memo has focus (note
the TAB key won't fire the event either). If you set
the memo's WantTabs to true then the TAB key fires
the form's keydown event.

You see, the behavior depends on what control has the
focus on your form. My understanding is that the OS sends
a WM_GETDLGCODE directly to the *focused* control (bypassing
the form) and the TAB or arrow key events will be sent to
the control depending on its response. If the
the control responds to WM_GETDLGCODE with DLGC_WANTARROWS
or DLGC_WANTTAB or a combination, then such events will
be send to the control and the form wll be able to
intercept them. Otherwise not.
That's why you need to work at the control level.

What I don't know is the mechanism by which the focus
changes on a form, by pressing the arrow keys, from a button
to another, for instance. Who gets this message?

Hope someone else can explain this better.

Eudy


Nicholas Gessler wrote:
> At this point I am more confused than ever.  The applications I have written
> in which the ArrowKeys WORK are virtually identical to those in which the
> ArrowKeys DO NOT WORK.  The Form1 Properties and Events are identical as are
> the includes and Unit1.h files.
> 
> So I don't understand why one WORKS and one DOES NOT.
> Also, FAQ-78 says NOT to create a handler for my Form1.  But that's
> precisely where I want the ArrowKeys to register.
> 
> I am sure I must be missing something quite obvious to others on this
> newsgroup, but I just can't figure it out.
> What is going on?  And how can I make it right?
> 
> Thanks,
> Nick
> 
> "Remy Lebeau (TeamB)" <gambit47@yahoo.com> wrote in message
> news:3ed1839d$1@newsgroups.borland.com...
> 
>>The arrow keys do not produce OnKey... events by default.  You must
>>explicitally request them before Windows will then issue them as expected.
>>
>>    Receive key events for the arrow keys or the TAB key
>>    http://www.bcbdev.com/faqs/faq78.htm
>>
>>Gambit
> 
> 
>