[ http://issues.apache.org/jira/browse/WICKET-139?page=all ]
Jim McLaughlin updated WICKET-139:
----------------------------------
Attachment: defaulttreestate.patch
separate selected == true processing into two stages:
1. if allowSelectMultiple == false, remove nodes except the one being selected,
if it is present
2. add the selected node if it is not already selected.
> DefaultTreeState allowSelectMultiple == false not evaluated when selecting
> node already selected
> ------------------------------------------------------------------------------------------------
>
> Key: WICKET-139
> URL: http://issues.apache.org/jira/browse/WICKET-139
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Reporter: Jim McLaughlin
> Priority: Minor
> Attachments: defaulttreestate.patch
>
>
> selectNode will not process the change from allowSelectMultiple == true to
> allowSelectMultiple == false when selectNode is called on a TreeNode that is
> already in the selectedNodes set
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
