> * Joerg, can you explain what is the aim of
> auto props, how to use it...
> on a properties dialogue within freemind to set
> options graphically...
> freemind.props should have the highest priority
> and must never be overwritten
I not agree.
For example, users can change the background color by a dlg box (it's like
a property dlg). If we want to save the background color and then put it
in the autoprops. In the next session, background color in userprop will
overright the last saved color.
I think that autoprop must be after userprops but must be almost empty
except for modified parameters.
In fact, the bg color is not a good example as I think it must be saved
(and loaded) with the model. Because if we define a set of color for nodes
and edges that use gray colors (something not to do, just a example :-),
if the default bg ground is gray too, we will see nothing. The bg color
must be in adequation with the others colors.
> > freemind.props should have the highest priority
> > and must never be overwritten
> I not agree.
> I think that autoprop must be after userprops but must be almost empty
> except for modified parameters.
> Don't know..........
I would think that if the user does set some props by hand (what he normally would not do),
he wants them to be loaded... But anyway, I gave autoprops the highest priority because that
makes many things easier (technically). So, now only the essential properties (those changed
during the run of freemind) are actually saved.
I'm working on an intuitive editor for tree-structured data: