Hi Thomas. I’m debugging threading issues in my application, which is based on JSVGCanvas. I wasn’t doing any correct Swing threading for a start, and now I want to ensure that all of my interactions with the JSVGCanvas are performed correctly.
Now I know (as we all do :)) that modifications to the document that is currently displayed in the canvas must be done in the UpdateManager’s RunnableQueue. What about any other calls to public methods on JSVGCanvas: should they be done in the Swing event dispatch thread? Canvas listeners (like GVTTreeBuilderListener) are fired in the Swing event dispatch thread, yes? And how about public methods on the BridgeContext: do they need to be done in the UpdateManager’s RunnableQueue too? For example, if I call BridgeContext.getGraphicsNode(), will that need to be in the RunnableQueue because the elementNodeMap will possibly be modified because of document modifications in the UpdateManager thread? Thanks, Cameron -- Cameron McCormack ≝ http://mcc.id.au/ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
