Windows Form z-order?
-
I am essentially running an application that creates a thread to run a Form, say Form1 by calling...
Application.Run(new Form1()); //new thread has already been created and this is run on that new thread
Then, the application runs another process. This creates a Form, say Form2 in the same way that Form1 was created, by calling Application.Run(). The problem is that Form1 is on top of Form2, even though right before the Application.Run() call of Form2, I call BringToFront(), which is supposed to place it at the front of the z-order. Why is Form1 on top of Form2 even though Form2 was created afterwards, and explicitly brought to the front? I would like to do this without having to call SendToBack() on Form1, since I don't want to send it all the way back, I just want it to be behind Form2.
-
I am essentially running an application that creates a thread to run a Form, say Form1 by calling...
Application.Run(new Form1()); //new thread has already been created and this is run on that new thread
Then, the application runs another process. This creates a Form, say Form2 in the same way that Form1 was created, by calling Application.Run(). The problem is that Form1 is on top of Form2, even though right before the Application.Run() call of Form2, I call BringToFront(), which is supposed to place it at the front of the z-order. Why is Form1 on top of Form2 even though Form2 was created afterwards, and explicitly brought to the front? I would like to do this without having to call SendToBack() on Form1, since I don't want to send it all the way back, I just want it to be behind Form2.
Wrong forum. This is for WPF, WCF and WF - not Windows Forms.
"WPF has many lovers. It's a veritable porn star!" - Josh Smith
-
Wrong forum. This is for WPF, WCF and WF - not Windows Forms.
"WPF has many lovers. It's a veritable porn star!" - Josh Smith
-
No problems - and an easy mistake to make.
"WPF has many lovers. It's a veritable porn star!" - Josh Smith