M
matt tagliaferri
I'm calling VB6 forms from my new .NET project so I can upgrade my
code in phases and not have to rewrite it all in one shot.
I've wrapped the VB6 form calls inside of ActiveX DLL classes, and
then reference the DLL in my .NET project and can display the VB6
forms.
This works fine unless I try to do it from any DoubleClick event in
..NET. When I do this, the form displays and has keyboard focus (I can
tab from control to control), but no mouse focus, unless I click on
the form once. For example, if I load the form and click immediately
on the Close button, the button doesn't click unless I do it twice
(once to bring focus to the form, once to click the button). Same
thing with dragging the window to a new location - the first drag
doesn't work, it acts to bring focus to the VB6 form.
If I load the same VB6 form from a click event instead of a
doubleclick event, focus is given to the form correctly.
any ideas?
matt tag
code in phases and not have to rewrite it all in one shot.
I've wrapped the VB6 form calls inside of ActiveX DLL classes, and
then reference the DLL in my .NET project and can display the VB6
forms.
This works fine unless I try to do it from any DoubleClick event in
..NET. When I do this, the form displays and has keyboard focus (I can
tab from control to control), but no mouse focus, unless I click on
the form once. For example, if I load the form and click immediately
on the Close button, the button doesn't click unless I do it twice
(once to bring focus to the form, once to click the button). Same
thing with dragging the window to a new location - the first drag
doesn't work, it acts to bring focus to the VB6 form.
If I load the same VB6 form from a click event instead of a
doubleclick event, focus is given to the form correctly.
any ideas?
matt tag