Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Moving an app from modal to non-modal
Message
De
12/09/2005 11:00:50
 
 
À
09/09/2005 00:04:13
Dragan Nedeljkovich (En ligne)
Now officially retired
Zrenjanin, Serbia
Information générale
Forum:
Visual FoxPro
Catégorie:
Codage, syntaxe et commandes
Versions des environnements
Visual FoxPro:
VFP 9
OS:
Windows XP SP1
Divers
Thread ID:
01047940
Message ID:
01048779
Vues:
16
Thanks for the response.

Actually, I have no problems with opening all the right files or SET commands. Don't have (or understand, for that matter) dateenvironments. Also hardly ever used form's activate method, so that's not an issue either.

OK, I'm off to try this to see how it'll go.

Thanks

>>What are the difficulties from moving from an entirely modal application to make it non-modal?
>>
>>I have two applications in mind. Both are rather small, at least in the number of forms involved (about 40 each). They are similar in that both have hardly any input at all, as most of the data comes from a SQLServer database (maybe 4 or 5 forms in each accept input; the rest are just used to review data in different formats).
>>
>>I've been aware of the need for this for some time, so I have only a few global variables, and most of the forms could easily be modified to use private data sessions.
>>
>>So, what else will I need to be concerned with? I ain't never done no non-modal application before, and I assume there are common pitfalls to avoid (um, the first of which is to design it as modal in the first place, but it's a little late for that one ...)
>>
>>Any pointers will be appreciated,
>
>Switching the modality will be easy. The private DS's, however - you'll need to check that each form really opens the tables it needs, or actually pulls the data off the server, and does not rely on any of it being already there. The second is all the SET commands which will reset to default for each form as soon as it gets a private DS. You probably have your own code where you do the SETs - make sure it's called early enough, from either each form's de.beforeopentables, or .load (if no DE).
>
>Another one you may expect is that if your users may start flipping between forms (which they will be able to do, once they aren't modal anymore), any code in form's .activate will actually run again, not only once as it probably does on a modal form (unless you alt-tabbed back and forth - then too, with modal as well). So check your .activate()s, you may be doing something there that isn't reentrant.
Jim Nelson
Newbury Park, CA
Précédent
Répondre
Fil
Voir

Click here to load this message in the networking platform