We help IT Professionals succeed at work.

Check out our new AWS podcast with Certified Expert, Phil Phillips! Listen to "How to Execute a Seamless AWS Migration" on EE or on your favorite podcast platform. Listen Now

x

Tab Capture

aluiken
aluiken asked
on
Medium Priority
217 Views
Last Modified: 2010-04-06
Hi,

How can i trap the tab-key like a normal key instead of switching to the next control ? (TCustomEdit)

Kind regards,
Arijan
Comment
Watch Question

It's already doing that.... It's alwayus as a tab, and you can change it so it goes to the next control...

Author

Commented:
No, i want to use the tab key, if i write a proc for keypress or keydown then i can not trap this key. I want to use the tab key for a function in the control..
Commented:
Unlock this solution with a free trial preview.
(No credit card required)
Get Preview
How about in OnKeyDown() I think it accepts it....like

if key = VK_TAB then
  caption := 'The was just pressed ;->';

or OnKeyPress()

if key = #9 then
  caption := 'The was just pressed ;->';

Regards,
Viktor Ivanov
Rene, I have been struggling with this problem for some time.  I have converted a complex DOS based accounting system to Windows and have been able to mimic every single aspect of DOS behavior, procedurely moving a user through an extremely complicated agricultural accounting entry,  I have done everything, shut off the mouse, used the ENTER key to set focus to predetermined  controls, and on press of the ENTER key I need to update variables, which dictate the twists and turns the entry procedure will take.  When the user presses the TAB key however, Windows responds by sending focus on,  What I need to do is intercept the actual message, at the WndProc level, modify the keycode of 9 to 13, thus tricking the system into thinking that the ENTER key had been pressed instead.  

For the sake of code maintenance I don't want to update variables in the lost focus handlers because I don't want any reverse flows updating my flow flag variables.  which SHIFT+TAB provides.  I don't doubt that I could build a huge "mousetrap" to accomplish this, but I think that using your solution technique sounds a whole lot more appealing to me.

I tried your solution, with great anticipation, but found that the wparam that gets sent from the hook to my callback procedure is always 40, not 9 for TAB, 13 for ENTER, 27 for Escape etc... as I had expected, no matter which key is pressed.  

I used your code example verbatim.  Any ideas?  I really appreciate your concise, elegant solution,  It just didn't work for me.... I haven't done a lot of message hooking and am not really up to speed on the technique.

I am familiar with writing specific message handlers and I understand how to crack a message into wparam and lparam
I also am comfortable with function pointers.

Thanks,
Paul Steinbrueck
Windows Development Leader
FarmFact Accounting System
http://www.farmfact.com
Unlock the solution to this question.
Thanks for using Experts Exchange.

Please provide your email to receive a free trial preview!

*This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

OR

Please enter a first name

Please enter a last name

8+ characters (letters, numbers, and a symbol)

By clicking, you agree to the Terms of Use and Privacy Policy.