Guest afrinspray Posted August 22, 2002 Posted August 22, 2002 Hello, I'm having a few problems converting a visual basic 6 program to visual basic .net. In my old program, I used the activate events of mdi children frequently. While converting to .net, I've run into problems because the Activate event isn't being triggered in the child forms. Why does the activate event not fire in an MDI child form? Did Microsoft replace that event with MdiChildActivate? I would prefer not to use the MdiChildActivate event if possible... Any response would be greatly appreciated. Thanks, Mike :D PS - Some other people were having the same problem http://discuss.develop.com/archives/wa.exe?S2=dotnet&L=DOTNET&q=&s=urgent+rtm+bug+mdi+child+forms+activate+event&f=&a=&b= Quote
*Gurus* divil Posted August 22, 2002 *Gurus* Posted August 22, 2002 Yes, that behaviour has changed. The MdiChildActivate event of the parent form will fire when the user switches between MDI children, and when the last one is closed. 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 August 23, 2002 Posted August 23, 2002 Why would they do that? Activate isn't necessary, but it sure was convenient. Also, for anyone having problems using the MdiChildActivate event: I just call functions from inside the MdiChildActivate event, to simulate the old Activate function of Mdi Children. For anyone who has trouble using that event, the solution to your problem might be to use the addhandler/ removehandler functions inside the MdiChildActivate event. That way you can manually activate individual forms to your desires, without the event being fired twice. Thanks, Mike 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.