Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Forms still in memory after Doform()
Message
From
04/04/2002 10:36:32
 
 
To
04/04/2002 09:42:53
General information
Forum:
Visual FoxPro
Category:
The Mere Mortals Framework
Miscellaneous
Thread ID:
00637801
Message ID:
00640891
Views:
21
Hi Chris

>Are you calling the login form manually, or letting the framework start it for you?

Standard framework stuff.

When you use DoForm with a modal form like the login form, the default behavior is to hide the form, not destroy it. This is to let DoForm continue executing and process any returned value. Try moving your suspend to the loginform.hide().

We use cbizobjmodalform for most of our forms because we need the return value. It seems that the cmouseoverfx control is interfering with the release of the form. If I'm understanding the code properly, when loObject goes out of scope in the utility.prg after uretval has been returned, the form should get destroyed. Is that the way you see it?
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform