Strictly speaking, working with VisualLibrary off EDT thread might be
eventually valid - but then it's your responsibility to properly lock
between your manipulation thread and the EDT painting which uses the
same data strucures.
The Graphics Class View does not such locking and I am really not sure
if such locking is possible: the Visual Library itself registers e.g.
MouseListeners, ComponentListeners which runs in EDT, traverses widget
hierarchy and do not allow for any synchronization or locking.
So I think the assert I've added is obtrusive, but correct.
-S.
Dne 18.4.2018 v 15:39 Neil C Smith napsal(a):
On Wed, 18 Apr 2018 at 13:46 Efrem Mc <[email protected]> wrote:
java.lang.AssertionError
at org.netbeans.api.visual.widget.Widget.addChild(Widget.java:218)
at org.netbeans.api.visual.widget.Widget.addChild(Widget.java:208)
at
org.netbeans.modules.graphicclassview.JavaNodeWidget.<init>(JavaNodeWidget.java:127)
Where exactly did you get the Graphics Class View from? Plugins?
Looking at the recent history of Widget::addChild I think this is caused by
the added assertion to check it's being called on the EDT (which is line
218!). It looks like that plugin is adding widgets off the EDT? That's a
bug in the plugin not the Visual Library then.
Best wishes,
Neil
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
