See issue #37802 for justification. This patch
appears to solve the symptoms reported in that bug.
Created attachment 12462 [details]
Since #37802 was pushed off into the future, treating this as the
What? Should any Children.Key client wrap setKeys call to Runnable?
Why it's not done in setKeys directly.
TTV custody. OK, just another workaround. However rather early in dev
In nodes_eq_35833, Children.Keys.setKeys *does* automatically replan
itself to EQ. In that branch it has to because children can only be
accessed in EQ. In the trunk this is not generally required and you
can use any thread, under Children.MUTEX, and e.g. BeanTreeView
handles it fine; but it seems TTV is buggy in its use of
VisualizerChildren, and it seems that restricting yourself to EQ-only
access (which is anyway the long-term goal) avoids those bugs.
Do you think you could increment tasklist/core/manifest.mf so that
this critical workaround gets published on AU? The current AU version is
org.netbeans.modules.tasklist.core/1 [1.15 200312111900]
which does not have the fix.
Please, reporter, could you verify fixed issues. Thanks a lot.