Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Text box tooltip
Message
De
14/01/2005 13:22:34
 
 
À
14/01/2005 11:09:43
Information générale
Forum:
Visual FoxPro
Catégorie:
Gestionnaire d'écran & Écrans
Versions des environnements
Visual FoxPro:
VFP 7 SP1
OS:
Windows '98
Database:
Visual FoxPro
Divers
Thread ID:
00977082
Message ID:
00977304
Vues:
42
>>>>>>Hi all,
>>>>>>I want my textbox tooltip content be equal with Textbox.value at runtime.
>>>>>>how can i do this?
>>>>>>Thanks
>>>>>
>>>>>
>>>>>* MouseEnter
>>>>>this.ToolTipText = m.this.Value
>>>>>
>>>>
>>>>Thanks Dear Fabi.
>>>>It Solve my problem.
>>>>
>>>>also thanks for Borislav
>>>
>>>One tiny thing however. I don't agree with Fabio about the use of 'm.this.Value'. It should be 'this.value', so without the mdot. The mdot is complicating things here and does not add quality to the code. Fabio, you are giving a bad example and the risk is that it may become widespread to even specify the mdot when refering to this, thisform and the like. I know you can prove that 'this' could also be the name of a field, but that's really too academic.
>>
>>Personally, I don't use the m. in this case either, but it's really only a complication if you are not used to it. Fabio does one thing very properly - he remains consistent. If you handle your code in a completely consistent way, then it is not a complication. Again, I don't do it myself, but I can't find any justification in arguing with anyone that someone's code should not be entirely consisent (even if mine isn't).
>
>Alan,
>Read my sig and understand why I commented. Consistency is not the only issue. Standards are also important. Nobody writes m.this, so it is a de facto standard NOT to write m.this. The discussions have shown when mdot is useless. Even Fabio recognizes those cases. For example, the left argument was without the mdot. We should all agree that it's also not done to write m.this, even if it's in the right argument.


It is consistent because to the left of an assign equal '='
can to be a variable or a property, not a field ,
and therefore the command is not ambiguous.

Others examples of consistent commands:
x=thisform.objref.property
x=ALEN(someArray)
&x
someproc(@m.x)
The standard does not mean null.
Every standard can be right or mistaken, in this case it is mistaken.

Fabio
Précédent
Répondre
Fil
Voir

Click here to load this message in the networking platform