How to handle keystrokes properly in a window?

Question

0.00/5 (No votes)

See more:

Hello, friends
I created a window by calling win32 CreateWindow function, and put some edit controls on it, (Edit controls also created by CreateWindow function).
It works fine, To navigate between controld, I cachw WM_kEYDOWN and WM_KEYUP, and detect TAB and shift+TAB keys. It also works fine, execpt for a beep sound, which sounds every time TAB is pressed, bothering the user. I need a way to supress this sound for TAB, and some other keystrokes. Note that since this is win32 window and not a dialog, WM_GETDLGCODE is not sent to edit controls. any suggestions appreciated, any related articles also.
Thanks in advance
abzadeh

Posted 18-Mar-12 7:11am

mr.abzadeh

Updated 18-Mar-12 7:51am

v2

Add a Solution

Comments

Sergey Alexandrovich Kryukov 18-Mar-12 20:39pm

No sound should be generated unless you do it intentionally, so, it's hard to say where did you screw up. Could you make a short (short!) code sample to reproduce the problem? If so, use "Improve question".
--SA

mr.abzadeh 19-Mar-12 4:14am

Thanks for your comment.
It's the default behaviour of edit control. The edit control has focus and the window sends key stroke events such as tab, enter, ... to the edit control, and it generates sound since it does not process them. A dialog does not send this key strokes to controls, but process them to navigate between controls. Calling the IsDialogMessage function in the window's message loop processes these key strokes, navigation is done correctly, and sound is not generated,
I realy want to find a way to handle this events myself, in the windows message loop, without using IsDialogMessage. I want to navigate as I wish.
In other words, I want to build my own dialog.

Sergey Alexandrovich Kryukov 19-Mar-12 4:23am

Thank you for clarification. Still, a simple code sample could probably help.
--SA

Mohibur Rashid 19-Mar-12 4:18am

case WM_KEYDOWN
switch(LOWORD(wParam))
{
case VK_TAB:
return 0;
}
}

try this and see if works

mr.abzadeh 20-Mar-12 21:16pm

Thanks for your reply.
I have tested it, and the sound still is played,

mr.abzadeh 20-Mar-12 21:28pm

It does not work, but solution 1 is the currect answer.

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Jochen Arndt · Accepted Answer · 2012-03-19T03:10:00

Solution 1

The beep is emitted when the edit control processes specific keys. To avoid this, you may ignore these keys (WM_CHAR message) in the message processing of the edit control or handle them in the parent windows (dialog) message processing.

Posted 19-Mar-12 3:10am

Jochen Arndt

Comments

mr.abzadeh 20-Mar-12 21:25pm

Thanks, This is the case. It worked
I put this code in the message loop of edit control, and sound was bypassed.

case WM_CHAR: if ( wParam == VK_TAB ) return 0; break;