Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
How to make sure class A init runs before class B's init
Message
From
14/09/2004 09:11:02
Lutz Scheffler (Online)
Lutz Scheffler Software Ingenieurbüro
Dresden, Germany
 
 
To
14/09/2004 08:58:17
Cetin Basoz
Engineerica Inc.
Izmir, Turkey
General information
Forum:
Visual FoxPro
Category:
Classes - VCX
Miscellaneous
Thread ID:
00941850
Message ID:
00941875
Views:
31
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]
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform