Hi Jan,
I will have a look at the code asap.
In the meanwhile - some background info about the following:
You wrote:
It seems that Argo has a bug, when I load new project, the project
properties are set to new project instance, but rendering uses old project
instance.
Yes, this is a known issue ...(I do not seem to find the number now).
When loading a new project, the new project is created and filled from the
.zargo file being loaded. And only AFTER the load was completely done, the
"currentProject" is changed from the old project to the new one, and old
project is removed. The reason for this IIRC, is that it enabled falling
back on the old project when the load process fails.
However, if during load of the project, Figs are build, which use the
ProjectManager.getManager().getCurrentProject() function, then they get the
settings from the old / wrong project.
This is why I said before (in this mail chain):
[quote]
Look at AssociationNameNotationUml.toString(): you need to extend this to
make use of some parameter, like
if (isValue("showAssociationName", args)) {...}
This parameter is to be set in the FigAssociation.
[unquote]
This moves the dependency on the project from the Notation subsystem to the
UI, i.e. the Figs. The notation subsystem should not depend on the
Project(Manager) at all. But that is only part of the solution - I do not
yet know how to solve this.
Kind regards,
Michiel
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
