General information
Title:
Subclassing VFP base controls
I'm still not totally OO literate in syntax from memory here so please bear with me. I read one of, if not the first step to setting up OOP in VFP is to subclass _all_ VFP base controls and have an include file for each of them.
Is that "all" as in every one of them including ole, olegeneral, custom, etc controls or just the common ones: textbox, combobox, and so forth? Don't you do this just once or every time you write an application?
And why would I want an include file for each control? I don't have anything to put in the include files. ha
The next question is what code gets put in your VFP subclassed controls and what at the next subclass level which I suppose is the "application level"? At my first level I can see like adding input masks for phone and zip or states in a state list etc. So you'd have for example a state listbox that would be pretty much common to all applications. Is that what you put in your sub'd VFP base classes? Or do you leave them plain vanilla and add that at another level? I begin to see 3, 4 or more levels or 'generations' of subclassing here by the time you're finished with your application.
vfp base
|_sub level 1 > common to all applications
|_sub level 2 > common at application level
|_sub level 3 > 'tweaks' at form level
Thanks
Next
Reply
View the map of this thread
View the map of this thread starting from this message only
View all messages of this thread
View all messages of this thread starting from this message only