Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 353193

Summary:	[SysML Block Definition Diagram] Inconsistent preference key management
Product:	[Modeling] Papyrus	Reporter:	Yann Tanguy <yann.tanguy>
Component:	Core	Assignee:	Yann Tanguy <yann.tanguy>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	P3
Version:	0.8.0
Target Milestone:	---
Hardware:	PC
OS:	Windows 7
Whiteboard:

Description Yann Tanguy

2011-07-27 06:33:18 EDT

Preference keys mostly rely on notation type in this diagram which is not always a good choice, especially for label nodes of the same type that can possibly be reused in several parent nodes.
The policy for view of the same type reuse for different kind of semantic elements need also to be clarified.

Comment 1 Yann Tanguy

2011-07-27 06:37:31 EDT

Incorrect key used in getPreferredValue() fixed in r5135 (0.8.0).
Merge in trunk : r5136.

Comment 2 Yann Tanguy

2011-08-01 10:33:00 EDT

In r5164:
Label preferences (default location, parser options) now use a different preference key that include their owner link or node.
ChildLabelNode are not concerned by this.

The LabelSnapBackEditPolicy has been modified relatively to these changes (the default implementation only rely on the label notation type).

Comment 3 Yann Tanguy

2011-08-01 12:30:25 EDT

(In reply to comment #2)
> In r5164:
> Label preferences (default location, parser options) now use a different
> preference key that include their owner link or node.
> ChildLabelNode are not concerned by this.
> 
> The LabelSnapBackEditPolicy has been modified relatively to these changes (the
> default implementation only rely on the label notation type).

Merge in trunk : r5168.

Comment 4 Yann Tanguy

2011-09-05 05:49:17 EDT

Fixed.