| Summary: | getNavigationNode().dispose() does not work as expected, renders in wrong order | ||
|---|---|---|---|
| Product: | [RT] Riena | Reporter: | Christian Campo <christian.campo> |
| Component: | navigation | Assignee: | Thorsten Schenkel <thorsten.schenkel> |
| Status: | CLOSED WONTFIX | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | ||
| Version: | 2.0.0 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows Vista | ||
| Whiteboard: | |||
|
Description
Christian Campo
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. I think disposing the last submodule is my fault. the bug tracked here is that the modules are temporarilty rendered in the wrong order |