Hi *,
Bob said:
I was thinking that when the user selects a model element that we
immediately call the model subsystem to determine if it is editable.
If not then we call a setEnabled(false) method on the prop panel that
will iterate through all controls and set their enablement status.
That would immediately indicate to the user that the element is not
editable by the greyed out fields.
Yes, but this not only applies to the properties panel, but also the
Documentation, Constraints, Stereotype and Tagged Values tabs.
But it does NOT apply to the Presentation tab!
The user should be able to add profile members onto diagrams, and alter
their appearance.
So, he has to understand why some elements are editable, and others are not.
Maybe we could alter the default appearance of newly drawn profile members a
bit, e.g. like a blue fill for profile nodes?
Some applications have the possibility to load read-only project files, and
then disable *all* editing. If ArgoUML would ever get this function in the
future, then that may impact the way we now are going to disable editing for
profiles. Let's try to be as generic as possible.
Regards,
Michiel
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
