Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Opinion: Who Should Move a Control
Message
De
17/07/1999 16:21:42
Timothy Enright
Coos Bay Public Schools
Coos Bay, Oregon, États-Unis
 
 
À
17/07/1999 11:38:43
Information générale
Forum:
Visual FoxPro
Catégorie:
Classes - VCX
Divers
Thread ID:
00242574
Message ID:
00242790
Vues:
24
Erik,

Again, good points! I modeled for performance but probably did not add enough controls to notice a difference. Also, I am creating my base classes and want to keep them as thin as possible.

My solution:

Added two properties (WithBottom,WithRight)to all movable ojects in my base class (1=Float, 2=Size, 3=Float+Size, 4=Lock, 5=Lock+Float, 6=Lock+Size, 7=Lock+Float+Size). I didn't like the way size gradualy put space between the control and the edge - lock will maintain the right/bottom spacing.

Then I copied the FFC _resizer class (nice code BTW) and modified the .SetSize() to handle the additional functionality. This was the only change I needed to make for everything to work.

Do you think using FOR EACH instead of a FOR NEXT to loop through the controls will help improve performance? Now, If performance becomes an issue I believe that your method remains open to me and I can subclass my base class and make a smarter control.

Thanks again for your help!

...tim

PS I am going to post the FOR EACH vs FOR NEXT in the Coding, Syntax & commands forum.
Précédent
Suivant
Répondre
Fil
Voir

Click here to load this message in the networking platform