.NET mod window over VB6

We have a VB6 application showing a .NET WPF modal window (on the main VB6 thread).

It correctly blocks interaction with VB6 UI because the thread is blocking in window.ShowDialog ().

We also have a timer in VB6. Since the timer loops on the main thread ( Does the VB6 Timer control create a separate thread? ) I would expect the timer to also block until the modal is closed. This is not the case. The VB6 timer keeps ticking, executing the VB6 code on the tick and updating the locked VB6 UI. Also, as soon as the timer loops for the first time, the WPF window LOSES its modality - which means I can go back to the VB6 screen and the WPF window will move behind the VB6 window.

Any idea what's up with this? Is WPF handling WNDPROC messages and then suddenly allowing VB6 code to execute and losing IsThreadModal for some reason?

Thank.

+3
vb6 wpf wndproc


source to share


No one has answered this question yet

See similar questions:

five
Does VB6 Timer control a separate thread?

or similar:

28
How can I tell if a WPF window is modal?
8
WPF modal progress window
6
How do I properly implement a modal dialog on top of a modeless dialog?
3
What was the VB6 threading pattern?
2
Stack Legacy VB6 Timer Ticks or skip if previous tick is still running
2
Close all open modal dialogs
1
Application-modal MessageBox from WPF modeless window
1
Can I run Windows WPF invoked by VB6 without the Interop Toolkit?
1
Form interop is blocking when calling VB6 form from .NET?
0
How to make WPF ShowDialog () Block parent window



All Articles
Loading...
X
Show
Funny
Dev
Pics