Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Text box tooltip
Message
De
14/01/2005 14:30:28
 
 
À
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:
00977327
Vues:
36
>>>>>>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.

As I said, I don't do what Fabio does either, but what on earth is the point of having a standard if one is not consistent? Fabio has a standard, and I can't argue that it's a poor standard. His rules for himself are fairly rigid, and for him, and anyone he mentor's, that leads to no confusion or complications at all. For Fabio, variables use 'm.' where they can possibly (even remotely) be confused with aliases or fields, and don't where they can only be variables. Sounds fairly simple and straightforward to me.

I still go back to my original statement. It's about what one is used to. We'd all like the standards to be set according to what each of us finds comfortable, but one man's meat is another man's poison, so whatever the standard, somebody is going to be unhappy. If that somebody is me, then so be it. If it's you, then also, so be it.
Précédent
Répondre
Fil
Voir

Click here to load this message in the networking platform