Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Form Class keeps switching base class upon compile
Message
De
14/02/2003 21:20:49
Dragan Nedeljkovich
Now officially retired
Zrenjanin, Serbia
 
Information générale
Forum:
Visual FoxPro
Catégorie:
Programmation Orientée Object
Divers
Thread ID:
00752241
Message ID:
00753603
Vues:
24
>>> After you hack the vcx do you compile it? (i.e. COMPILE CLASS whatever) I >> can see the object code either not being rewritten or getting confused
>>> after manually hacking the vcx.
>
>No reason to recompile the class. This is a development time/compile time setting. the compiler uses this settin to see where to pull code from during compile. Once you make the change it is immediate in the class. In other words after you make the change when you modify the class you see what your parent class is by both how VFP displays the parent class in the properties sheets as well as the right PEM's showing up or not.

I think this is where you were wrong - after hacking the class or form, you must recompile it explicitly, or do some changes using the editor, so it will be recompiled when saved.

When you hack a vcx/scx, and then open it in the appropriate editor, you see them in the PEM window because it reads the text from class, classloc, properties, methods and other memos. However, there's objcode memo, which keeps the compiled version of all that, and it gets updated only after a compile, or after an edit+save. If you only open it and don't change anything, it doesn't recompile (why would it, there were no changes), and your next build uses the previously compiled values.

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
Suivant
Répondre
Fil
Voir

Click here to load this message in the networking platform