CheckBoxTree and TreeSelectionListener

[robross0606]

I've read as much as I can find on this topic, and there seems to be a lot of it. I'm using the latest 3.2.4 version of JIDE common. My current setup has digin enabled and single event mode disabled. I need to be able to determine which checkboxes have been checked and ALSO which have been unchecked. In other words, I need to tell which checkboxes have changed state.

At startup, the nodes are read in via a custom TreeModel and initial checkbox selections are made during the #treeNodesInserted() callback of the TreeModelListener. I set the intial states using #addSelectionPath(). The nodes appear fine in the tree and are checked as expected. It looks something like this:

Code: Select all

x -- Group
   x -- node
   x -- node
   x -- node
   x -- node
   x -- node


However, the first time I check/uncheck any single "node" in the GUI:

Code: Select all

x -- Group
   x -- node
   x -- node
   O -- node
   x -- node
   x -- node


I get two TreeSelectionEvents:

• In the first one, "e" shows the "Group" node as areNew=[false] which is correct.
• A second TreeSelectionEvent has "e" with ALL the node elements showing areNew=[true,true,true,true,true]. These nodes are NOT new so this is making it very difficult to determine which nodes have been checked and which ones have been unchecked.

[robross0606]

I think what's happening is that, because "digin" mode reflects ALL "node" elements being checked by a single event on "Group", the subsequent uncheck of a single "node" element triggers follow-up events showing all the "node" elements asNew. I have yet with a combination of code that can elegantly react to this behavior.

[JIDE Support]

You could also invoke CheckBoxTreeSelectionModel#setSingleEventMode(true) to fire only one event in that case. Please give JIDE CheckBoxTreeDemo a try for your reference.

Thanks,

[robross0606]

I have given all the demos a try. The problem is NONE of these models appears to tell you when an item has ben UNSELECTED. They only tell you when an item has been SELECTED. SingleEventMode does not resolve the problem.

[robross0606]

To clarify, what appears to happen when an item is UNselected is that it disappears from the event's path list. Instead, it is supposed to stay in the path list so you can call TreeSelectionEvent#isAddedPath(path) on that item to see if it is has been selected or not. The problem appears to be that the unselected node simply disappears from the list completely.

[JIDE Support]

Your observation is a little bit different with mine. To make sure we are on the same page, a screencast to show my test is uploaded at http://screencast.com/t/M7IRSvUMykZZ FYI. Please let us know if that's not what you want.

Thanks,

[robross0606]

I was able to figured out the right combination of SingleEventMode and DigIn, along with some code to figure out what has changed. Thanks!