Hi Jorg,
Thomas DeWeese wrote: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.
Jorg Heymans wrote:
ok. stepping through for a <path> element[...]
it seems to do this for pretty much every shape i add. Should i look for something more specific ?
No, this means it's building them.
If there was a namespace problem, would it not find the registered bridge for this element?
Correct, the bridges are registered on Namespace and tag name. So if it didn't know that they were SVG paths or what ever it would not have found a bridge. You can give up the whole namespacea are the problem thing ;)
I can track the namespaces and prefixes down to getBridge(Element) in BridgeContext.
The problem is now a question of why aren't your shape nodes being drawn, or if they are being drawn why aren't they showing up? I generally find the best way to address this is to add print statements to the 'paint' and 'primitivePaint' methods on some of the key GraphicsNode subclasses, in this case I would look at CompositeGraphicsNode and ShapeNode. I would do things like print the Bounds of the GraphicsNodes to see if they are someplace odd. You might want to map the bounds to the 'global' coordinate system (using getGlobalTransform) in case a odd scale/translate snuck in.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
