On Dec 2, 2008, at 9:52 PM, Paul McNett wrote:
> The defaults will be the default from the single superclass. You
> don't have to ask
> layers of superclasses. Instantiate your subclass, and then find out
> what the
> property value is. That is the default.
Ah, there's the rub. Instantiating an object can have all sorts of
wonky side effects.
It's kinda gratifying to see you following the exact same thought
patterns that I went through when I worked on this stuff. We still
instantiate all the base Dabo controls in the Class Designer to get
the defaults; this was problematic enough, but manageable. When I
started instantiating custom classes, which could have all sorts of
code that executed at instantiation, things got a lot messier. So I
started exploring creating a property graph for each class, but of
course each level of inheritance required knowing a lot about all of
its superclasses, and I quickly came to the conclusion that this was
unwieldy with anything over one level of inheritance. Hence the design
decision that I came to and we are currently discussing.
-- Ed Leafe
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-users
Searchable Archives: http://leafe.com/archives/search/dabo-users
This message: http://leafe.com/archives/byMID/[EMAIL PROTECTED]
