Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 311199 - getNavigationNode().dispose() does not work as expected, renders in wrong order
Summary: getNavigationNode().dispose() does not work as expected, renders in wrong order
Status: CLOSED WONTFIX
Alias: None
Product: Riena
Classification: RT
Component: navigation (show other bugs)
Version: 2.0.0   Edit
Hardware: PC Windows Vista
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Thorsten Schenkel CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-04-30 11:52 EDT by Christian Campo CLA
Modified: 2016-09-29 09:28 EDT (History)
0 users

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 Christian Campo CLA 2010-04-30 11:52:47 EDT 
I insert a feature into the Riena Demo to jumps from the customer Overview RCP-View to the Email Subapplication with jump. In the open view, I added a jumpBack() (if isJumpTarget()). I also wanted to dispose my view and remove it from the navigation after the jump back.

The jumpBack works but disposing the view left the navigationView in an inconsistent state. The disposed module moved to the top of the list, after I clicked on it, the sequence of modules is correct again but switching does quit work.

The best is to sync the latest CVS state and try yourself
Comment 1 Christian Campo CLA 2010-05-03 03:32:49 EDT 
I think what I did wrong here was I removed the SubModule and left the Module there (with no childs). So I will correct that bug in the demo. Still having a Module with no childs should not corrupt the sequence of the Modules in the NavigationTree.
Comment 2 Christian Campo CLA 2010-05-09 14:45:10 EDT 
I think disposing the last submodule is my fault. the bug tracked here is that the modules are temporarilty rendered in the wrong order