Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 343931 - Exception after activating a non-selectable SubModuleNode
Summary: Exception after activating a non-selectable SubModuleNode
Status: RESOLVED FIXED
Alias: None
Product: Riena
Classification: RT
Component: navigation (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: 3.0.0.M7   Edit
Assignee: Sabine Achilles CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-04-27 03:30 EDT by Sabine Achilles CLA
Modified: 2011-05-04 08:15 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Sabine Achilles CLA 2011-04-27 03:30:44 EDT
When a non-selectable SubModuleNode has no children, its activation throws an exception. The behavior of non-selectable SubModuleNodes should change -> if they have no children, disable them until at least one child is added.
Comment 1 Sabine Achilles CLA 2011-04-27 03:33:32 EDT
Fixed in head.
Comment 2 Thorsten Schenkel CLA 2011-05-04 08:10:29 EDT
The fix doesn't work in every situation. In the SWT Example Client in the module "Playground" all not selectable sub-modules WITH children are disabled. This is not correct.
Comment 3 Thorsten Schenkel CLA 2011-05-04 08:15:31 EDT
The  tree items of not selectable sub-modules will not be longer disabled. After a tree item of a not selectable sub-module was selected in the navigation tree the node will be not activated and the selection in the tree will be reverted.