Okay, this seems simple enough, but when I try it, it won't work. I've created two edit boxes by using the CreateWindow() function. I have given them the styles of WS_TABSTOP|WS_DLGFRAME|ES_UPPERCASE|WS_VISIBLE|WS_CHILD
and I have given them the handle to the parent window. Now, when I run this program and I try to tab between the two edit boxes, nothing happens...it just "dings" at me. I can't seem to intercept either the tab or the enter keys for that matter. If I remember correctly, in MFC I used the On_Command function thingy to trap for the enter keys, but I never had to worry about the tab not working. Now, MSDN docs say just to create the control with the WM_TABSTOP style and it will "magically" tab from one control to the next that has the WM_TABSTOP style. I've tried using GetNextDlgTabItem() to see the next possible control it could tab to and it "says" that the other control will be the next one. Can someone please shed some light on this subject? Thanks in advance.
Niky Williams
NTS Marketing, Inc.
and I have given them the handle to the parent window. Now, when I run this program and I try to tab between the two edit boxes, nothing happens...it just "dings" at me. I can't seem to intercept either the tab or the enter keys for that matter. If I remember correctly, in MFC I used the On_Command function thingy to trap for the enter keys, but I never had to worry about the tab not working. Now, MSDN docs say just to create the control with the WM_TABSTOP style and it will "magically" tab from one control to the next that has the WM_TABSTOP style. I've tried using GetNextDlgTabItem() to see the next possible control it could tab to and it "says" that the other control will be the next one. Can someone please shed some light on this subject? Thanks in advance.
Niky Williams
NTS Marketing, Inc.