franksymons
asked on
Respond to arrow keys in form
Hello,
How do I make my form respond to the arrow keys (assigning my own procedures behind them) and ignore the default behavior (movement between components on the form) when pressing the arrow keys?
Regards,
Frank.
How do I make my form respond to the arrow keys (assigning my own procedures behind them) and ignore the default behavior (movement between components on the form) when pressing the arrow keys?
Regards,
Frank.
ASKER
Could you be more specific?
Set the form's KeyPreview property to True (in object inspector).
Then add code to the 'OnKeyDown' event.
Greetings,
MvZ
Then add code to the 'OnKeyDown' event.
Greetings,
MvZ
In the OnkeyDown event code something like:
if Key=VK_DOWN then begin
MessageBeep(0);
Key:=0;
end;
Set Key to 0 to prevent the default behaviour.
other key-values are VK_LEFT, VK_RIGHT.
Greetings,
MvZ
if Key=VK_DOWN then begin
MessageBeep(0);
Key:=0;
end;
Set Key to 0 to prevent the default behaviour.
other key-values are VK_LEFT, VK_RIGHT.
Greetings,
MvZ
ASKER
Thanks for your answer, providing there is nothing on the form this works, but try adding a button and an edit box on the form. Use tab to make sure the button has the focus, now when pushing the down arrow key focus whill shift from the button to the edit box without executing the procedure. Pushing the down key with the editbox in focus will perform the procedure.
That's not what I'm looking for, I want the procedure to run every time, regardless of what may be on the form.
That's not what I'm looking for, I want the procedure to run every time, regardless of what may be on the form.
Okay...the fix all for capturing keystrokes before they go to components...
use TPopUpMenu. The menu items have a visible property which you can set so that items are not shown to your users. If you need to know what component had focus look at Screen.ActiveControl. The Shortcut function will take virtual keystrokes and convert them to TShortCuts.
procedure TForm1.FormCreate(Sender: TObject);
begin
//Note the forms PopUpMenu Property is set to the PopMenu
Left1.ShortCut := ShortCut(vk_down,[]);
Right1.ShortCut := ShortCut(vk_right,[]);
end;
procedure TForm1.left1Click(Sender: TObject);
begin
Memo1.SetFocus;
end;
Rick
use TPopUpMenu. The menu items have a visible property which you can set so that items are not shown to your users. If you need to know what component had focus look at Screen.ActiveControl. The Shortcut function will take virtual keystrokes and convert them to TShortCuts.
procedure TForm1.FormCreate(Sender: TObject);
begin
//Note the forms PopUpMenu Property is set to the PopMenu
Left1.ShortCut := ShortCut(vk_down,[]);
Right1.ShortCut := ShortCut(vk_right,[]);
end;
procedure TForm1.left1Click(Sender: TObject);
begin
Memo1.SetFocus;
end;
Rick
ASKER
Thanks for the answer, but I don't wan't to solve it that way. There has to be a way to catch the windows message itself and then send it to whereever I want it to.
hallo,
i think you should kill the focus of the button or the edit field.
i did this with
button.enable:=false;
button.enable:=true;
then the button has no focus and you can handle the arrowkeys with the OnKeydownEvent (or OnKeypressedEvent)
i think its not elegant but it works.
regards
titz
i think you should kill the focus of the button or the edit field.
i did this with
button.enable:=false;
button.enable:=true;
then the button has no focus and you can handle the arrowkeys with the OnKeydownEvent (or OnKeypressedEvent)
i think its not elegant but it works.
regards
titz
Okay...tried this a couple different ways...tried to create a new button that overrode WndProc...but the Wm_ButtonDown never comes through this handler...it's dispatched by the Component ahead of it in Tab Order(watched it in WinSight to verify this).
So we went to the ultimate message handler...Application.OnMe ssage...th at works...
procedure TForm1.FormCreate(Sender: TObject);
var
myButton: TMybutton;
begin
Application.OnMessage := MyMessage;
end;
procedure TForm1.MyMessage(var Msg: TMsg; var Handled: Boolean);
begin
if (Screen.ActiveControl is TButton) and (Msg.message = WM_KeyDown) then
begin
if (Msg.WParam = vk_Left) or (Msg.WParam = vk_Right) then
Handled := true;
end;
end;
Rick
So we went to the ultimate message handler...Application.OnMe
procedure TForm1.FormCreate(Sender: TObject);
var
myButton: TMybutton;
begin
Application.OnMessage := MyMessage;
end;
procedure TForm1.MyMessage(var Msg: TMsg; var Handled: Boolean);
begin
if (Screen.ActiveControl is TButton) and (Msg.message = WM_KeyDown) then
begin
if (Msg.WParam = vk_Left) or (Msg.WParam = vk_Right) then
Handled := true;
end;
end;
Rick
Note certain controls handle the Left Arrow and Right Arrow different than Buttons...i.e. TEdit.
Rick
Rick
ASKER
Thanks titz, but I'll go with the comments that rickpet gave me. It's exactly what I need. Rickpet if you want the points form it in a question and they're yours.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
If you really want to do this, you need to inherit a new component from each one where you want the behaviour to change and then you need to watch for the CN_KeyDown message and then check if message.charcode is one of the VK_DOWN VK_LEFT VK_RIGHT or VK_UP. If so, dont call inherited and do your thing. otherwise, call inherited.
I'm pretty sure this would work.
Another solution for the more professional would be to hook your own process and then look out for WM_Keydown messages.
If you want the second one, write your e-mail and I'll tell you more.