Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 329033 - setBlocked(final boolean blocked) on NavigationNode doesn´t honor current blocked state
Summary: setBlocked(final boolean blocked) on NavigationNode doesn´t honor current blo...
Status: RESOLVED FIXED
Alias: None
Product: Riena
Classification: RT
Component: navigation (show other bugs)
Version: unspecified   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: 3.0.0   Edit
Assignee: Steffen Kriese CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-10-29 07:54 EDT by Nobody - feel free to take it CLA
Modified: 2011-03-08 20:33 EST (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 Nobody - feel free to take it CLA 2010-10-29 07:54:10 EDT 
Current implementation of setBlocked() in class NavigationNode looks like this.

/**
	 * @see org.eclipse.riena.navigation.INavigationNode#setBlocked(boolean)
	 */
	public void setBlocked(final boolean blocked) {
		this.blocked = blocked;
		notifyBlockedChanged();
		// taken out because it has caused some problems
		//		for (final INavigationNode<?> child : getChildren()) {
		//			child.setBlocked(blocked);
		//		}
	}
	
	
notifyBlockedChanged() gets called even if nothing has changed.
Comment 1 Steffen Kriese CLA 2011-03-07 03:46:44 EST 
Fixed in HEAD