On Wed, 4 Oct 2006 08:59:32 +0200 (CEST)
Michael Van Canneyt <[EMAIL PROTECTED]> wrote:
>[...]
> > > Ok, and any idea how we can optomize the "subscribers" Update
> > > method, so they can know what changed. Normally the "subject"
> > > calls the Update method of all it's "subscribers" passing itself
> > > as a parameter. Maybe we could pass a second parameter (data
> > > object - maybe a list of some sorts) containing the names of the
> > > components that changed. Even a TStringList might do. Just
> > > another thought.
> >
> > Changing a property can change various others as well. For example
> > changing the Width can change child controls, siblings and parent.
>
> Yes, but applying this change to the child form should result in
> exactly the same consequences, unless the affected components were
> changed already... ?
Not necessarily, but I *think* this is so rare, we could live with it
and instead fix the component to allow this scheme.
The above would be an optimization to not stream the whole forms
every time.
But there is still the 'default values' problem:
If an ancestor property is changed to the default value it is not
written to the stream. So applying this stream to the descendants does
not change the property in the descendants.
Mattias
_________________________________________________________________
To unsubscribe: mail [EMAIL PROTECTED] with
"unsubscribe" as the Subject
archives at http://www.lazarus.freepascal.org/mailarchives
