Description
Is there a reason that in updateDisplayedColor (and the matching opacity method) that the check to cascade is commented out? (line 1685 on current code)
From what cascadeColorIfNeeded is doing it would appear to make sense to have that line back in - ie only change the color of the nodes children if the current node is set to cascade the color down.
As the code currently is if one node in a hierarchy has cascadeColorEnabled set to YES then its color will cascade right down to the lowest level regardless of what that flag is set to in other nodes.
Enabling that check has fixed the specific problem I was having of not being able to control the displayed color of a node, but introduced a load of other issues where I obviously need to be a lot more explicit in the number of nodes I set cascadeColorEnabled on - I guess that is why the change was made.
The documentation ("to cascade down to it's children") doesn't explicitly mention is goes all the way down the hierarchy, but could be read either way to be fair.