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

Bug 317654

Summary: SubModule is not shown, when parent ist not selectable
Product: [RT] Riena Reporter: Steffen Kriese <steffen.kriese>
Component: navigationAssignee: Project Inbox <riena.navigation-inbox>
Status: CLOSED FIXED QA Contact:
Severity: normal    
Priority: P3 CC: christian.campo
Version: unspecified   
Target Milestone: ---   
Hardware: PC   
OS: Windows XP   
Whiteboard:
Attachments:
Description Flags
Patch for the SWT Exampleclient to reproduce this bug
none
Error
none
Expected visual representation none

Description Steffen Kriese CLA 2010-06-23 02:26:22 EDT
If we have a assembly like this:

- ModuleGroup
  - Module
    - SubModule1
      - SubModule 2
 
and the following configuration:
- SubModule 1 is not selectable
- the assembly has a autostart > 0

If  the user selects the module, an empty module is shown and no view will appear in the worarea. But if we navigate programatically to the SubModule2 node, the navigationtree will be displayed as expected.
Comment 1 Steffen Kriese CLA 2010-06-23 02:31:46 EDT
Created attachment 172480 [details]
Patch for the SWT Exampleclient to reproduce this bug

to reproduce this behavior follow these steps:
- start the SWT Exampleclient
- Go to playground and select the module "Selectable SubModule"
- nothing happens ...


to reproduce the correct behavior when navigating programatically:
- go to the module Shared View Demo
- klick on the button "Show selectable SubModule"
- the "Selectable Submodule" opens as excpected
Comment 2 Christian Campo CLA 2010-06-23 03:34:29 EDT
could you please attach a screenshot what that looks like ?
Comment 3 Steffen Kriese CLA 2010-06-23 03:44:20 EDT
Created attachment 172485 [details]
Error
Comment 4 Steffen Kriese CLA 2010-06-23 03:54:52 EDT
Created attachment 172487 [details]
Expected visual representation
Comment 5 Steffen Kriese CLA 2010-06-23 03:58:37 EDT
Don't pay attention to the weird looking Subapplicationtabs in the screenshots. This has nothing to do with this bug.
Comment 6 Christian Campo CLA 2016-10-04 07:47:58 EDT
I believe this was fixed