Thomas DeWeese wrote:
Hi Jorg,

   One other 'high level' thought occured to me.  Are you telling
the canvas to always be dynamic?  If not you can change the document
all you want and nothing will happen.

yup, i'm even adding a static rect element "dynamically" to see if it works, no problem.


The GVT tree building is done by the bridge.GVTBuilder class. It's pretty simple, it basically checks if it has a bridge registered for the element that was added. If so it will build it's node and then check it's children, otherwise it stops.

ok. stepping through for a <path> element

in GVTBuilder, buildGraphicsNode(BridgeContext ctx, Element e,CompositeGraphicsNode parentNode)
- an SVGPathElementBridge is built
- from this a graphicsnode is created , a ShapeNode more specifically
- this graphicsnode is added to the parentnode
- handleGenericBridges is called
- buildGraphicsnode is called again recursively


it seems to do this for pretty much every shape i add. Should i look for something more specific ? If there was a namespace problem, would it not find the registered bridge for this element? I can track the namespaces and prefixes down to getBridge(Element) in BridgeContext.

Thanks
Jorg


--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to