Sometimes, when searching a very small directory,
the Search Results window display found nodes but
the root node claims that "No matching nodes were
found." It seems that the set of displayed nodes
is correct, only the text of the root node is wrong.
The bug is in method Manager.startSearching(...). It calls
callOnWindowFromAWT("setResultModel", resultModel). This call
schedules method call ResultView.setResultModel(resultModel) to the
end of the AWT event queue (invokeLater(...)). If a matching node is
found before this call is processed, the result model does not notify
the root node so that it is not updated.
Fixed in the trunk.
I fixed the bug by replacing calls of EventQueue.invokeLater(...) with
EventQueue.invokeAndWait(...). I also reviewed which methods are
called from which threads and removed some unncessary redirections to
the AWT dispatch thread.