Bug 502351 - [Model Explorer] [FACET] Papyrus-RT Protocol menu item is not expanded when create a protocol message from the new child menu
Summary: [Model Explorer] [FACET] Papyrus-RT Protocol menu item is not expanded when c...
Status: UNCONFIRMED
Alias: None
Product: Papyrus-rt
Classification: Modeling
Component: tool (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows 7
: P3 normal
Target Milestone: Future   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard: depends_on_papyrus
Keywords: Documentation, readme
Depends on: 496486
Blocks:
  Show dependency tree
 
Reported: 2016-09-28 00:59 EDT by smaoui asma CLA
Modified: 2017-06-19 08:54 EDT (History)
3 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description smaoui asma CLA 2016-09-28 00:59:59 EDT 
The aim of this bug is to track Bug 496486. Whenever this bug is fixed, the workaround proposed for Papyrus RT in Bug 480403 should be removed.

The main issue is the fact that model explorer view did not well interface with facet: newly created child item is not automatically selected (container item menu is not expanded) if the parent semantic element is not the real container of the child sementic element 

Example in Papyrus RT that illustrates this bug: when creating a protocol message, the Protocol menu item is not expanded and the newly created protocol message is not automatically selected
Comment 1 Peter Cigehn CLA 2016-09-28 03:32:21 EDT 
Could we give this Bugzilla some other name, more indicating what should be done in Papyrus-RT, instead of repeating the same name as the Papyrus Bugzilla it tracks? The notification mails from Bugzilla becomes quite confusing with two different Bugzillas with exactly the same name.
Comment 2 Charles Rivet CLA 2016-10-31 14:32:57 EDT 
Is this still an issue?
Comment 3 smaoui asma CLA 2016-10-31 17:14:24 EDT 
(In reply to Charles Rivet from comment #2)
> Is this still an issue?

This is only a track of a Papyrus bug : Bug 496486. In Papyrus RT, I already proposed a workaround in Bug 480403 (0.8.0 bug).

So this will still an issue until the Papyrus Bug is resolved.
Comment 4 Charles Rivet CLA 2016-11-16 14:05:54 EST 
Assigned to Rémi to reassign/close when Papyrus bug is closed.
Comment 5 Peter Cigehn CLA 2017-03-06 12:33:37 EST 
I guess that since Bug 496486, which this bug depends on, will not make its way into Neon.3, that we re-plan this one for 1.0 (or Future).
Comment 6 Remi Schnekenburger CLA 2017-03-14 12:26:45 EDT 
I agree, we should postpone it to a later release, this is only a tracker for a Papyrus generic solution. The feature is working in our case thanks to a workaround, fixing it now or later will not affect end users.
Comment 7 Remi Schnekenburger CLA 2017-03-14 12:27:43 EDT 
(And removing me from assignee, as I no longer assign tasks to CEA employees).
Comment 8 Simon Redding CLA 2017-04-25 12:28:09 EDT 
Bug 496486 will not be fixed for R1 so this bug needs to go to future.