[RESOLVED] Subclassing usercontrols (Previously: App closing sequence)

[Jim Davis]

Here is an example project that will show you simplified the problem, im facing with. Theres dont need to put these controls to a usercontrol-container, its just enough to place them to an mdi child, to get the crash.

The code will create 10 clones of form1, each form will contain 10 instances of ccXpButton.

I had to modify the usercontrol, to avoid the Client Site not available error, i included the InDevelopment "hack". I think this is not the reason of the crash, because the compiled code is also crashing. But if you feel like, you can double check it of course. Its better to close the child forms one by one (even better to use the ctrl+f4 for mass closing them). The crash will occur immediately, but in rare cases it just doesnt. In case you didnt got any crash, just restart the app, do the mass-closing, then the crash will occur i am sure.


I know, that bugfixing someone else's code is stinks, i dont ask you to do. What i only to ask you, about experiences how did you avoid crashes, using subclassed usercontrols.

12/22/2004 11:23:03 PM: James...

Hi Chris i tried to email but got returned email form the email supplied. I think there is a problem when you run it in a MDI environment as a complied exe. Have not been able to pinpoint it but it will cause a random crash when the form is unloading. Only happens when the control and project are comlpied.

12/29/2004 4:14:14 PM: Chris Cochran

James,
The problem you mentioned above is related to the mouseleave trapping. I am working the issue.
Not sure why you are having problem with the e-mail link, it works for all others.
Chris

Ok, it seems like the control have the issue, ive just missed this conversation