Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
How to make sure class A init runs before class B's init
Message
De
14/09/2004 09:11:02
Lutz Scheffler
Lutz Scheffler Software Ingenieurbüro
Dresden, Allemagne
 
 
À
14/09/2004 08:58:17
Cetin Basoz
Engineerica Inc.
Izmir, Turquie
Information générale
Forum:
Visual FoxPro
Catégorie:
Classes - VCX
Divers
Thread ID:
00941850
Message ID:
00941875
Vues:
28
Cetin,

I can not belive it. (No, No it's true, I can trace it on my comp)
So it means the backmost object is instantiated first and all following are drawn over it. What a solution!

I guess I have learned enough for this day.

Agnes

>Agnes,
>Yes AFAIK changing Zorder affects instantiation order.
>Cetin
>
>>Hi Cetin,
>>
>>You are right that dealing with problems like this in an objects INIT is no good idea.
>>
>>But I have no idea what "send to back/front" you mean. The only "send to back/front" I know deals with ZOrder. Does this realy change the order of creating objects at runtime?
>>
>>Agnes
>>
>>
>>
>>>>I had to add a class (optiongroup) to a form.
>>>>
>>>>Another class (combo) init relies on the optiongroup already being initialized.
>>>>
>>>>How can I change the order of things being initialized in the form designer?
>>>>
>>>>TIA
>>>
>>>Peter,
>>>You might change that by 'send to back/front'. However instead of trusting it (and later form might be touched) I generally move their custom init code to form init.
>>>Cetin
Words are given to man to enable him to conceal his true feelings.
Charles Maurice de Talleyrand-Périgord

Weeks of programming can save you hours of planning.

Off

There is no place like [::1]
Précédent
Suivant
Répondre
Fil
Voir

Click here to load this message in the networking platform