Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Forms still in memory after Doform()
Message
General information
Forum:
Visual FoxPro
Category:
The Mere Mortals Framework
Miscellaneous
Thread ID:
00637801
Message ID:
00640598
Views:
18
Hi Armin,
I put a suspend() in the cmouseoverfx.cleanup(). When I ran my app, it did not suspend when I closed the login form. The cleanup() did get called when I exited the application. The same thing happened when I put code in login.Destroy(). It didn't execute when the form closed, only when I exited the app. I don't understand why this is happening, but it's causing us some problems with our high volume customers running out of resources.

Thanks for your help.



>Randy,
>
>>Now for the hard question. How to fix it. I deleted the controls from the form and then used addobject() in the init of the form to see if that would release it, but it didn't. I've tried putting a chighlighteffect.release() in the form.destroy(). That doesn't do it either.
>>Any suggestions?
>
>Set a breakpoint in the cMouseOverFX.Cleanup() or .Destroy() and check, if execution stops there when releasing the form. The class holds two references. One to the control and one to the form. This could prevent the form from closing properly. I haven't used the class so far, so this is just a guess.
>
>Regards,
>Armin
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform