This problem was found with the 3.3.3 jar. Single event mode and digin are enabled.
I have a new section of code which is building a tree in an iterative fashion. Based on some boolean value, the node may be checked after it is added. This can cause problems when digin is enabled. For example, say I start with this tree:
Now I add a leaf node C, but it has a property that requires that it be checked.
Now I add another leaf node D as a child of B, but that node must *not* be checked:
Unfortunately, the result in this case is that both C and D are checked in the UI. If I verify the selections via a call to getSelectionPaths(), the returned path is for node B, which seem to imply some problem with digin mode where a state isn't cleared when a new node is added to the model.
As a workaround, I removed the code which checks nodes as they are built, and after the entire model is built I iterate over the nodes again to set the check boxes. The problem is that after the model is built, it will be modified over time, and the same problem could occur again, and I have found no workaround yet.
Thanks in advance.