On Thu, Aug 23, 2012 at 12:19 PM, Roger L. Whitcomb
<[email protected]> wrote:
> I'm kind of struggling with what to (succinctly) call the style....
> "setDisableUIOnDisabledNodes(boolean)" seems a bit unwieldy.... any
> suggestions?
>
So:
A.1) First the node would need to be disabled. For this we could
create a new setEnableNode(boolean). But this setter shouldn't block
the UI. Because some nodes might still
want to show a different menu when they are in this state.
A.2) Second, if users want to disable event propagation then they can
invoke setDisableUIOnNode(). And the pivot-code can internally always
call setEnableNode(false), first and then proceed with the
event-blocking code.
Or
B.1) How about a JSON style argument? I love this Pivot approach now ;).
setNodeAttributes ("{enableNode:No, 'disableUI:Yes'}");
I don't know how much parsing-work this JSON-style will involve but we
will be able to extend the attributes in future without adding more
setter calls.
In future:
B.2) setNodeAttributes ("{EnableActivityIndicator:Yes'}") ;)
> ~Roger
thanks
