Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Member of a parent class
Message
 
To
17/08/2001 17:44:12
Dragan Nedeljkovich (Online)
Now officially retired
Zrenjanin, Serbia
General information
Forum:
Visual FoxPro
Category:
Classes - VCX
Miscellaneous
Thread ID:
00545606
Message ID:
00546121
Views:
12
>>yes it is composite...
>>
>>Thanks
>>
>>Tommy
>>
>>>>>Lots of ways,
>>>
>>>Tommy,
>>>One more way is to Return .F. from Init and the object won't even exist. However, if it is a composite class, this can be dangerous because the programmer may not check before trying to access the object and if not, BOOM!
>
>Putting the .visible=.f. into the .refresh may be an overkill. I'd put it in form's .init, somewhere in the end and surely after any dodefault(). If it still gets to be visible, someone in the parent class is stubborn and brings the darn thing to life too often - then this sort of overkill does need a counter-overkill :)

Yeah, I had to resort to overkill!!! That was one stubbon set of controls... but all is well at the moment!!

Thanks
Tommy
Tommy Tillman A+ NetWork+ MCP
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform