Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
User defined methods pre-empt necessary processing?
Message
De
16/07/1999 19:36:30
 
 
À
Tous
Information générale
Forum:
Visual FoxPro
Catégorie:
Gestionnaire d'écran & Écrans
Titre:
User defined methods pre-empt necessary processing?
Divers
Thread ID:
00242642
Message ID:
00242642
Vues:
67
As a VFP newbie, I have just begun to use forms and I'm a little worried that if I define custom code for event methods of various controls on my form, the processing that would otherwise be done by the default methods inherited through the class hierarchy will not be done correctly.

As a rule of thumb, is it good practice to place DODEFAULT() in every method inherited from VFP's native baseclasses to which I add custom code?

Or is all of the really necessary processing for these events done regardless of whether or not I add custom code to a method with the form designer?

I ask this because I've encountered some unusual behavior with one of my forms and I'm wondering if it is because one of the control methods I modified might no longer be performing some vital task that would otherwise be performed by its default counterpart inherited from the native baseclass hierarchy.

If it is a good idea to execute DODEFAULT() in methods inherited from native baseclasses (which one intends to customize) how can one determine whether it's better to execute the default code before or after the new custom code?

Is there a specification for all of the methods inherited by default from native VFP baseclasses? If so, where?
"The Iron Fish: The water is cold...but the fish don't mind"
...Jay Jenks, boyhood chum
Suivant
Répondre
Fil
Voir

Click here to load this message in the networking platform