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

Bug 340154

Summary:

[All Diagrams] Diagrams are not updated when a default value is changed.

Product:

[Modeling] Papyrus

Reporter:

Fabien Gautreault <fabien.gautreault.ext>

Component:

Diagram

Assignee:

Project Inbox <mdt-papyrus-inbox>

Status:

NEW ---

QA Contact:

Severity:

normal

Priority:

Version:

unspecified

Target Milestone:

---

Hardware:

All

OS:

All

Whiteboard:

Attachments:

Description	Flags
test model related the task.	none

Description Fabien Gautreault

2011-03-16 09:26:24 EDT

Build Identifier: 20100617-1415

[Default Value] When user add a property it's created with a default LiteralString value. Then user delete this default value and add a new default value. As a result this type LiteralString is removed from the list of type proposed to him. User can redo this "delete/add new default value" untill the list of type proposed would be empty. The list shouldn't change. Even more, it seems that the default value proposed in the list are the default value created in the project. When user assign this value he is just deplacing this value to the new object so the value is removed from another object and user don't know.

Reproducible: Always

Steps to Reproduce:
1.Created a default value in the properties or a property
2.Delete a default value
3.This default value is now not available anymore in the list be cause it havent't been created but just deplaced from another element.

Comment 1 Fabien Gautreault

2011-04-13 10:52:10 EDT

A "+" in HMI make the user thinking he's going to create another element, not deplace. It should appear a button "add" AND et button "create".

(In reply to comment #0)
> Build Identifier: 20100617-1415
> [Default Value] When user add a property it's created with a default
> LiteralString value. Then user delete this default value and add a new default
> value. As a result this type LiteralString is removed from the list of type
> proposed to him. User can redo this "delete/add new default value" untill the
> list of type proposed would be empty. The list shouldn't change. Even more, it
> seems that the default value proposed in the list are the default value created
> in the project. When user assign this value he is just deplacing this value to
> the new object so the value is removed from another object and user don't know.
> Reproducible: Always
> Steps to Reproduce:
> 1.Created a default value in the properties or a property
> 2.Delete a default value
> 3.This default value is now not available anymore in the list be cause it
> havent't been created but just deplaced from another element.

Comment 2 Sébastien Gérard

2013-03-13 12:19:58 EDT

The issue is not moe reproductible. However, cheking the task, I notices that when the default value is edited and its value changed. When the update is done within the property view, the diagram is not updated automatically. I rename the bug consequently.

Comment 3 Sébastien Gérard

2013-03-13 12:21:22 EDT

Created attachment 228368 [details]
test model related the task.

Comment 4 Camille Letavernier

2014-03-28 15:23:30 EDT

The issue described in Comment 0 was related to the properties view and is now fixed

Issue described in Comment 2 is now related to the diagrams