38
Hi. This is an odd question because I'm not sure if it's a bug or if this is how it is supposed to behave, however what is happening is I have a main window of my application that is passed to Application.Run, and then I have a secondary window (a welcome screen) which is created afterwards and shown on the same thread. However, the problem is that when the first window shows a dialog window, which is supposed to be tied to it, the secondary window no longer accepts input--it just beeps when you attempt to click anything within it. Oddly, though, it can be brought to the front, overtop the dialog, but it won't allow any interaction, not even to be moved.
So obviously I don't want this--the welcome dialog should be freely interactive regardless of any dialogs that the main window has open.
I am suspicious that this might have something to do with the fact that both windows are running on the same thread, and that the "modality" of the dialog is affecting all windows on the same thread.
The question is, then, is there a workaround that will allow this to work? I've heard it is a bad idea to have user interface elements running on more than one thread in Windows.
