OK, I guess I spoke too soon. I tried the code below in a Cocoa-Java
app and it hangs. I checked with the debugger and it's hanging down in
some Swing code that's trying to instantiate menus. This is a problem
because there are already menus.
The JSVGComponent does _not_ create menu's, the JSVGViewerFrame (from the svgbrowser/squiggle application) does create menus but you aren't using that. I would look carefully at the stack trace that is creating menus to try and figure out who is trying to create them.
So I tried to implement the basics of
what JSVGComponent does in the loadSVGDocument() method:
This code looks about right to me.
This starts to work b/c documentLoadingStarted() gets called, but that's as far as it gets. Also, an extra menu gets added to the menubar, so apparently some Swing code is still getting called.
Anyone have any suggestions?
I don't think it is Batik calling the Swing code. In fact at the point you reach (document load) nothing having anything to do with Java2D/AWT has been called by Batik, it's all just XML Parsing and DOM Document construction. Not until you start the GVT builder does it do anything real with AWT/Swing stuff.
I strongly suspect the problem is somewhere else in your code. Does your system use any custom DOM elements with our DOMImplementation?
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
