Ed Leafe wrote:
> On Jan 31, 2005, at 10:42 AM, Paul McNett wrote:
>
>> However, take dPageFrame, an example of a VFP 'container class': it
>> contains dPage's that can control themselves and be controlled
>> directly by user code.
>>
>> Now: menus. A menu bar contains menus, and a menu contains menus and
>> menu items, all of which can control themselves independently of their
>> parent.
>
>
> OK, then, we're talking about two completely different things, then.
> I'm using 'container' to mean a class that other objects can be added
> to: buttons, textboxes, labels, etc. I don't mean something that can
> have a specific child type.
I think we are talking about the same thing, but that in addition to
_IsContainer, which is a flag for "can I have children?", we also need a
separate list of _ChildClasses or something, which explicitly states the
list of possible children. This would be the same for dPanel, dForm,
dDialog, but would be much more limited for dPageFrame and dMenu.
> What do you suggest I name the class attribute that determines if a
> particular class can have *any* type of control added to it? Or maybe
> just drop it altogether and test every instance in the designer to see
> if it is a form, panel or dialog?
--
pkm ~ http://paulmcnett.com
©2005 Paul McNett |
