Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Release
Message
De
10/09/2007 16:47:19
Dragan Nedeljkovich (En ligne)
Now officially retired
Zrenjanin, Serbia
 
Information générale
Forum:
Visual FoxPro
Catégorie:
Gestionnaire d'écran & Écrans
Titre:
Versions des environnements
Visual FoxPro:
VFP 9 SP1
OS:
Windows XP
Database:
Visual FoxPro
Divers
Thread ID:
01253375
Message ID:
01253555
Vues:
30
>I jumped in here because I thought you might have answered a problem I have which is that sometimes in my simplest apps (a PRG calls a FORM and then follows it with a READ EVENTS and some cleanup and then exits, sometimes it leaves the form window open (in development mode -- of course it closes in compiled mode)... and I don't know why, since I CLEAR EVENT and thisform.release as the last two things under the "click" method of an "exit" button...
>
>Ah... oh... hmmm... maybe I need to put those somewhere other than click?
>
>Cheers,
>
>Kevin
>
>PS (Sorry if I hijacked this thread...)

I don't mind, as long as questions get answered.

Sounds like you're closing your form properly, it's probably something else - you may have a dangling object reference, or a buffer which wasn't tableupdate()d nor tablerevert()ed, which may be the reason why would your form refuse to die gracefully. Check for those.

As for returning .f. from form.init (or any other class's, for that matter), it means the form dies before it shows, i.e. it only existed as a sort of unfinished object until its init exited, but then it vanished. So it didn't open at all, and this can't count as closing.

back to same old

the first online autobiography, unfinished by design
What, me reckless? I'm full of recks!
Balkans, eh? Count them.
Précédent
Répondre
Fil
Voir

Click here to load this message in the networking platform