Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Moved event before Init()?
Message
 
 
À
10/02/2002 15:44:39
Information générale
Forum:
Visual FoxPro
Catégorie:
Gestionnaire d'écran & Écrans
Divers
Thread ID:
00617898
Message ID:
00618377
Vues:
11
This message has been marked as the solution to the initial question of the thread.
Jim,

I think these couple of rules will help define for you what's happening.

Property values set via the property sheet occur before the Init() event for an object. These happen for every level of your class hierarchy.

Setting .Left or .Top is going to trigger the Moved() event. Just like setting .Height or .Width is going to trigger .Resize().

Have you anywhere in the form class hiearchy set either .Top or .Left to 0, in code or on the property sheet?

>Not as I can tell/see. The coverage log NEVER went to Moved() through the whole Init().
>In addition, it DID execute my method for the new placement of the form and later testing showed that the input to it are Top=0 and Left=0 despite the fact that the memo field (loaded to a property of my 'framework' in MAIN) does have other values at startup (but the Moved() event code *does* (well, did, until I made the change you suggested) change the values in the property).
>So I can only conclude that the Moved() event was triggered BEFORE the Init() event and that does not seem correct (or at least logical) to me.
>
>It's not a problem doing it the smart way (at close only) so now it is only a matter of academic interest.
df (was a 10 time MVP)

df FoxPro website
FoxPro Wiki site online, editable knowledgebase
Précédent
Suivant
Répondre
Fil
Voir

Click here to load this message in the networking platform