Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
#define Preprocessor Directive on VCX properties
Message
De
19/03/2003 13:41:50
 
 
À
19/03/2003 11:04:40
Information générale
Forum:
Visual FoxPro
Catégorie:
Autre
Divers
Thread ID:
00767607
Message ID:
00767708
Vues:
17
One problem I see here is that #DEFINE constants are used to replace a token that you type in code with the value of the constant at compile time when building the object code.

The properties are read in at run time. At run time there are no defined constants.

So, all I can see it doing is replacing the contants at compile/save time of your class with the value for the #define. This doesn't help much if you change the #define.

But, why don't you init the properties in code using your contants.

Have you actually submitted this somewhere? I think this is the first I have ever seen it, and I usually keep up with the wish lists.

BOb


>Hi all
>
>I waited for VFP8 in order to see this great problem resolved, but...
>
>VFP does not replace the constants defined in a #include file.h in the properties of a VCX class or SCX form.
>
>I have tons of directives!
>
>I can resolve the problem without to create a VCX clone,
>to process the field properties and recompile the VCX clone ?.
>
>To the face of RAD IDE
>
>I will wait for VFP9, 10...
>
>Fabio
Précédent
Suivant
Répondre
Fil
Voir

Click here to load this message in the networking platform