| Summary: | User can't modify the name of an artifact using Properties view | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Technology] Tigerstripe | Reporter: | Navid Mehregani <nmehrega> | ||||||
| Component: | UI | Assignee: | Navid Mehregani <nmehrega> | ||||||
| Status: | RESOLVED FIXED | QA Contact: | |||||||
| Severity: | major | ||||||||
| Priority: | P3 | CC: | chrhartl, erdillon | ||||||
| Version: | unspecified | ||||||||
| Target Milestone: | 0.5M0 | ||||||||
| Hardware: | PC | ||||||||
| OS: | Mac OS X - Carbon (unsup.) | ||||||||
| Whiteboard: | |||||||||
| Attachments: |
|
||||||||
|
Description
Navid Mehregani
All renames need to go through the Refactoring framework (In reply to comment #1) > All renames need to go through the Refactoring framework In that case, we need to disable this functionality from Properties view. It's obviously incorrect to throw an exception when user does this and I assume most "Eclipse users" will, since EMF and other Eclipse projects support modification of model objects thorough Properties view. This may be a duplicate of the other bug on "renaming associations". To be verified. THIS MUST USE THE REFACTOR FRAMEWORK! :-) Created attachment 176997 [details]
Patch
This patch disables editing of properties for Entities in Property view. The view can still be used to view properties, but the user has to go through the expected route (e.g. refactor framework) to modify properties of the model.
Modified files:
AbstractArtifactItemProvider
QualifiedNamedElementItemProvider
NamedElementItemProvider
Created attachment 177003 [details]
Patch#2
This patch also makes the changes for instance diagrams.
Modified files:
InstanceItemProvider
NamedElementItemProvider
AbstractArtifactItemProvider
NamedElementItemProvider
QualifiedNamedElementItemProvider
Submitted patch. |