If a filter is in effect, and you edit one of the
properties of a task such that it no longer matches
the filter, the task is not removed. It probably
I changed some things in TaskListener in order to solve this.
But get following exception each time I edit a task.
java.lang.IllegalArgumentException: An explored context (B) must be
within the root context (Summary).
Are you trying to set the node selection, or change the root node? If
changing the node selection, you have to be careful that the node
you're selecting is actually a descendant of the root node in effect.
This gets complicated when filter nodes are in use.
TaskNode.find(Node, Task) can help you (and to get the root to use
during the find, use view.getExplorerManager().getExploredContext(),
NOT view.getRootNode() - since that always returns the "base" root,
not the filtered one if one is in effect.
If you're trying to change the root itself, make sure that no nodes
are already selected. There's an example of this (workaround) in
TaskListView.setFilter: the first thing it does is remove the
selection (by setting the selection to an empty array) and THEN it
calls setRoot() to change the root node being explored.
By the way, your commit commented out javahelp related classpath stuff
in build.xml. That was not intentional, right? If you're having
problems building with that code in, your nbbuild module is out of date.
The only problem now is:
If you change a task in the filtered view the whole tree of nodes will
be recreated and the tree will be collapsed. Is there a way to remove
children from nodes to prevent this?
It colapses only if there is empty intersection between old and new
I doubt that a usertask should disappear as result of property
editing. But I can imagine task disappearing while moving (gesture
that I'm done with it) to next task i.e. leaving current 'record'.
If a user marks for example a task as completed and the current filter
does not accept those tasks the task will disappear from the list.
NB 4.1 is out