On Jun 18, 2008, at 1:20 PM, Paul McNett wrote:
> I guess I should bow out, but it seems much more complex than it needs
> to be. Why does it need to compare against anything? If you are
> modifying a third-generation, then you know which properties have been
> changed because there's a property assignment in that third-
> generation.
> Whatever the values of the other properties are, come from the
> second-generation, whether they are assigned there or in the first
> generation (and we don't care, because we are editing the third-
> generation).
I took the approach you described at first, and it worked well with
simple subclassing. But if you created a composite class, it got messy
real fast, especially when you went back and modified the original
class.
-- 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]
