On January 2, 2004 09:56 pm, you wrote:
"Bill Medland" billmedland@mercuryspeed.com wrote:
I am just about to start concentrating on IsDialogMessage, especially in the non-dialog context. Our program (suite) uses ActiveX controls extensively and is difficult to use because the TAB handling in particular is totally wrong.
Probably what really makes Tab handling wrong is a not correct behaviour of GetNextDlgTabItem and GetNextDlgGroupItem. I was intending to fix them at some point, but it seems I have no time to work on them and won't have it in the near future.
Not that simple, but that might be a big part of it. I just started looking at them too on Friday. Currently IsDialogMessage passes the tab handling to the Dialog's WndProc by message, which is not always correct. Under some circumstances (to be clarified) it does the tabbing itself, presumably using GetNextDlgTabItem (which it doesn't do currently)
It would be great to have a test suite for that APIs as well.
Hopefully that will come out of it, but before we can write the test suite we need to figure out what the correct behaviour is.