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

Bug 354215

Summary: [Package Diagram] implicit navigation does not work
Product: [Modeling] Papyrus Reporter: Raphael Faudou <raphael.faudou>
Component: CoreAssignee: Project Inbox <mdt-papyrus-inbox>
Status: RESOLVED WONTFIX QA Contact:
Severity: normal    
Priority: P3 CC: cletavernier, klaas.gadeyne, papyrus-bugs, raphael.faudou
Version: 0.10.0   
Target Milestone: M7   
Hardware: PC   
OS: Windows XP   
Whiteboard:
Bug Depends on:    
Bug Blocks: 417673    

Description Raphael Faudou CLA 2011-08-09 03:13:21 EDT
When double clicking on a package from a "package diagram", nothing happens. If we use the "accelerator" to create a diagram, the window for navigation appears and we can create a sub diagram with implicit navigation but no decorator is created. And again when clicking on the package nothing happens.
Comment 1 Yann Tanguy CLA 2011-08-10 02:59:45 EDT
Fixed in 0.8.X branch (see Bug353859).
Comment 2 Raphael Faudou CLA 2011-09-24 09:25:08 EDT
(In reply to comment #1)
> Fixed in 0.8.X branch (see Bug353859).

No decorator is created so end user is not aware of possible implicit navigation
Comment 3 Raphael Faudou CLA 2013-03-13 17:10:58 EDT
Does not work in Kepler.
In class diagram or component diagram or UC diagram, when a package contains diagrams, there should be implicit navigation to this diagram from the package. It is not the case. No decorator nor navigation hyperlink.
Comment 4 Toni Siljamäki CLA 2013-10-10 08:35:43 EDT
See also Bug 417673.
Comment 5 Camille Letavernier CLA 2014-02-25 12:47:15 EST
The "implicit navigation" based on the Heuristic framework has been disabled (Too many mechanisms doing the same thing with different implementations, or different things with the same user action).

It has been replaced with the generic navigation service (Alt + Mouse over), which is compatible with all diagrams and the Model Explorer. However, this only supports navigation to diagrams located immediately under the hovered element (i.e. it will not navigate to State Machine diagrams located under a StateMachine of the hovered Class)

The legacy navigation strategies might be backported to the new navigation framework.

The decorators (Blue & Green arrows) have been removed, as they were confusing, and not compatible with the Decoration Service (overlapping images)
Comment 6 Raphael Faudou CLA 2014-02-25 13:23:15 EST
(In reply to Camille Letavernier from comment #5)
> The "implicit navigation" based on the Heuristic framework has been disabled
> (Too many mechanisms doing the same thing with different implementations, or
> different things with the same user action).

And why removing this mechanism and not another one? this is one of the issues with Papyrus that will have to be managed at some point in time. There are some features that are removed without discussion. Sometimes you discover that one feature has disappeared; so you ask why and answer is "was deprecated"... 

> It has been replaced with the generic navigation service (Alt + Mouse over),
> which is compatible with all diagrams and the Model Explorer. However, this
> only supports navigation to diagrams located immediately under the hovered
> element (i.e. it will not navigate to State Machine diagrams located under a
> StateMachine of the hovered Class)

So if it is not supported by current mechanisms it seems that the right conclusion should be: "it has not been replaced" ;-)
> 
> The legacy navigation strategies might be backported to the new navigation
> framework.

What "might" mean?
Anyway, till "legacy" strategy is not backported, I think that this bug should remain open.
> 
> The decorators (Blue & Green arrows) have been removed, as they were
> confusing, and not compatible with the Decoration Service (overlapping
> images)

Well, those decorators were used in TOPCASED with old editors and users appreciated. Who has decided that they are confusing? end users? I was never asked to give opinion about that.
 
Well i understand that it is important to close bugs but be careful when closing them: if it leads to removing features that were appreciated by end user community, I'm not sure that it give value to the community...
my two cents
raphaël