Guest afrinspray Posted July 29, 2002 Posted July 29, 2002 I know why you don't follow my problem! Because it had nothing to do with activation. The MDIForm was my startup form, and then the definstance function was creating another object (I think). So for some reason, when I would hide a form, one instance would have one active child form and then the other would have a different active child form. Somehow, VB was coordinating the two instances so that it would only show one active form, but there could be more than one active mdi child! I can't really understand how it would do that. Maybe my explanation is wrong; however, I removed the DefInstance function in the MDIForm and the problem was solved! Quote
*Gurus* divil Posted July 29, 2002 *Gurus* Posted July 29, 2002 Definstance? Was this the product of you running VB6 code through the upgrade wizard? Quote MVP, Visual Developer - .NET Now you see why evil will always triumph - because good is dumb. My free .NET Windows Forms Controls and Articles
Guest afrinspray Posted July 30, 2002 Posted July 30, 2002 Absolutely. But, I had significantly changed the code since then. The only part of the "upgrade support" that still remained was the MdiForm's DefInstance function. I honestly had no idea that this had anything to do with the problem I was having. I also didn't know that two MdiForms could be open at the same time in VBNet. I understand it now though; VBNet is completely object oriented and all these forms are all objects. So it makes sense that two can be open. Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.