Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Dialog as a VCX... gotta be a better way
Message
From
22/11/2003 07:45:27
Cetin Basoz
Engineerica Inc.
Izmir, Turkey
 
General information
Forum:
Visual FoxPro
Category:
Coding, syntax & commands
Miscellaneous
Thread ID:
00852285
Message ID:
00852596
Views:
8
>Cetin,
>
>[With a show(1) you wouldn't need read/clear events. Hide() the form to continue on the line that follows read events. You'd get the value and release the for there.]
>
>That works. Thanks.
>
>
>[PS: I didn't understand why "but if the dialog required more complexity, a class would be better" other than preference.]
>
>In this class, I've got only one "parameter" (property). Other dialogs could have several properties which could be mutually exclusive. Rather than have to pass in parameters in a specific order, I'd rather set properties in which ever order I choose. Basic OOP design philosophy.
>
>Regards,
>Thom C.

What if you still pass a single array or object. I don't really see something related/breaking with basic OOP design philosophy here.
Regards
Cetin
Çetin Basöz

The way to Go
Flutter - For mobile, web and desktop.
World's most advanced open source relational database.
.Net for foxheads - Blog (main)
FoxSharp - Blog (mirror)
Welcome to FoxyClasses

LinqPad - C#,VB,F#,SQL,eSQL ... scratchpad
Previous
Reply
Map
View

Click here to load this message in the networking platform