Page 1 of 1

Geometry Group vs Canvas Performance for SVGs

Posted: 18 Aug 2023, 19:25
by stonstad
When converting from SVG, Is using a Geometry Group faster or more memory efficient than a Canvas? i.e. what the recommended best practice?

i.e.

<Canvas><Path ... </> vs
<GeometryGroup><Geometry ... </>

Is the Noesis team aware of any differences in quality of output betrween Figma2xaml vs Inkscape export?

Thank you!

Re: Geometry Group vs Canvas Performance for SVGs

Posted: 23 Aug 2023, 17:16
by sfernandez
If different paths have different fill/stroke you have to use a Canvas.

If all the paths share the same fill/stroke it would be more performant to use a GeometryGroup, unfortunately it is not correctly implemented in Noesis (#1777). Although you can export as separate paths, select them in Blend and open the context menu 'Path' > 'Make Compound Path', to merge all geometry data in the same path.
Is the Noesis team aware of any differences in quality of output betrween Figma2xaml vs Inkscape export?
Inkscape export is a lot more reliable than Figma2xaml (which is very very primitive).

Re: Geometry Group vs Canvas Performance for SVGs

Posted: 24 Aug 2023, 18:01
by stonstad
Thank you!