SVG to XAML conversion problems
#3
I have just published a new version of ReaderSvg v 4.5 that has an additional OverrideMiterLimit property.

Unfortunately there is no way to render miter limits as in svg specifications. But with the OverrideMiterLimit it is possible to minimize the problems that are crated with different WPF rendering. The property overrides the miter limit that is set in svg file and use any other value instead.

For backwards compatibility the default value in RaederSvg is set to 0. This value disables overriding and used value defined in svg file - when the miter limit is not defined in svg file a value of 4 is uses because it is the default value for svg. (note: in ViewerSvg the value of 2 is used by default).

When there are some problem similar to those described in the previous posts, you can set the OverrideMiterLimit to 1 or 2. When you would like to minimize the artifacts created by WPF rendering and can "live" with some sharp edges being cut, set the value to 1. Setting the value to 2 would still produce some small artifacts (but much less as before) and would not cut the sharp edges so soon.
Andrej Benedik
  


Messages In This Thread
SVG to XAML conversion problems - by adeburie - 07-25-2011, 02:12 PM
RE: SVG to XAML conversion problems - by abenedik - 07-26-2011, 11:10 PM
RE: SVG to XAML conversion problems - by abenedik - 08-01-2011, 09:51 AM
RE: SVG to XAML conversion problems - by adeburie - 08-01-2011, 01:35 PM
RE: SVG to XAML conversion problems - by Crown123 - 11-27-2013, 07:55 AM

Forum Jump:


Users browsing this thread:
1 Guest(s)