Hi All
Happy New Year to everyone and Welcome Back to Alexandre
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.
I will be using a trivial program with IsDialogMessage inserted into the main loop and will be trying to figure out the undocumented behaviour of this function (e.g. I am sure it internally handles redirecting to children etc.)
The only comments I've noticed so far (about a year back) suggest that we really don't know much about this function, but I thought I'd ask if someone else has notes about what is wrong with it, how it should work, alternative web sites etc. or has uncommitted patches etc., just so that I don't duplicate work.
All comments welcome
"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.
It would be great to have a test suite for that APIs as well.
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.
On January 2, 2004 09:56 pm, Dmitry Timoshkov 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.
BTW can you tell me what incorrect behaviour you are aware of; I'll see if I can fix it while I am working in this area.
It would be great to have a test suite for that APIs as well.
"Bill Medland" billmedland@mercuryspeed.com wrote:
BTW can you tell me what incorrect behaviour you are aware of; I'll see if I can fix it while I am working in this area.
Attached is an one year old test app which gave very different results under win2k and Wine. I didn't run it for a while, but I don't think that something has changed in that area in Wine.
-
Bill Medland -
Dmitry Timoshkov