Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Object as form property
Message
De
05/10/2007 12:01:57
Dragan Nedeljkovich (En ligne)
Now officially retired
Zrenjanin, Serbia
 
 
À
05/10/2007 09:26:17
Jay Johengen
Altamahaw-Ossipee, Caroline du Nord, États-Unis
Information générale
Forum:
Visual FoxPro
Catégorie:
Gestionnaire d'écran & Écrans
Versions des environnements
Visual FoxPro:
VFP 8 SP1
Divers
Thread ID:
01258596
Message ID:
01258972
Vues:
12
>>While the other advice you've been given is correct, unless there's a good reason, I'd add the property in the Form Designer and just assign it in Init.
>>
>>Tamar
>
>What would drive the decision to do it one way or another?

It being allowed/possible or not would influence it :).

Also, if the property is added at design time, it will pop up in the intellisense which would at least help you keep the spelling consistent. Also, if your code happens to fire in a wrong order (i.e. reference this object before it's instantiated), you'd get a different kind of error message :). That is, instead of "PEM not found" you'd get "is not an object". Third, if you add it at design time, then it can have _access and _assign methods - the former being a perfect place to instantiate it on demand.

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