Hi all,
I want to implement visual form inheritance, but there is one problem,
for which I don't see a good solution.
The situation: Both the ancestor and descendant forms are open in the
IDE.
The Problem: When the ancestor is edited, then the descendants need
to be updated.
The ancestor can be edited by:
Object Inspector: Here we can add detailed notifications if needed.
Designer: the same.
Anchor Editor: the same.
Some more tools: the same.
Component Editors: These can alter the component in various ways. They
only notify by an unspecific Modified event.
Experts: Same as Component Editors.
Descendants are loaded by applying first the ancestor values (.lfm) and
then the descendant overrides.
You can not clear/reset a component. You can only destroy it and create
it again.
To save the descendant values you need an ancestor instance to find the
differences/overrides and write them to the .lfm.
And last but not least:
Saving/Loading a component can take long, if it contains special data
like images and lists.
Mattias
_________________________________________________________________
To unsubscribe: mail [EMAIL PROTECTED] with
"unsubscribe" as the Subject
archives at http://www.lazarus.freepascal.org/mailarchives
