Bugzilla – Full Text Bug Listing
| Summary: | Navigation-Delayer-Thread activated after programmatic navigation | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [RT] Riena | Reporter: | Nobody - feel free to take it <nobody> | ||||
| Component: | UI | Assignee: | Nobody - feel free to take it <nobody> | ||||
| Status: | RESOLVED FIXED | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | P3 | CC: | christian.campo, elias | ||||
| Version: | unspecified | ||||||
| Target Milestone: | 3.0.0.M2 | ||||||
| Hardware: | All | ||||||
| OS: | All | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
Created attachment 176882 [details]
Fix handling the Threading problem
Fix applied |
If I have a Module with 3 SubModuleNodes A,B,C with active Node C the following Code executed in C´s SubModuleController will activate A which is wrong behaviour. getNavigationNode().setVisible(false); getNavigationNode().navigate(new NavigationNodeId("B")); B should be activated. A gets activated by the Delayer-Thread.