I've noticed that this perticular Storyboard property behaves static, that is, it changes on every object instance of the same class, independently of where it's played. However all other properties appear normal and affect only targeted instance.

I've noticed that this perticular Storyboard property behaves static, that is, it changes on every object instance of the same class, independently of where it's played. However all other properties appear normal and affect only targeted instance.

There are two problems:
-The FontFamily property exported by inkscape does not include a hash (#) character, causing a parsing error. Is it really necessary to have this in there?

-Inkscape does not put the actual text in the Text property, but uses span instead, which looks like this:
<Span whiteSpaceCollapse="preserve" FontSize="60">Some text here</Span>
Any chance in supporting this?

I am trying to reduce the manual work required on an XAML exported by InkScape and this will help a lot.

-The FontFamily property exported by inkscape does not include a hash (#) character, causing a parsing error. Is it really necessary to have this in there?

When FontFamily doesn't include a hash, it refers to OS installed fonts. In NoesisGUI we don't use support that. We can interpret FontFamily="Arial" the same as FontFamily="#Arial", but remember that you have to copy the corresponding .ttf fonts next to the xaml file so it can be found.

-Inkscape does not put the actual text in the Text property, but uses span instead, which looks like this:
<Span whiteSpaceCollapse="preserve" FontSize="60">Some text here</Span>
Any chance in supporting this?

Full support for inlines is planeed after 1.2 release. If you need it now we can transfer Span text into the outer TextBlock easily. But the properties set in the Span (like FontSize) will be lost, unless we override TextBlock properties with the properties of the first Span found inside the TextBlock.

We can interpret FontFamily="Arial" the same as FontFamily="#Arial", but remember that you have to copy the corresponding .ttf fonts next to the xaml file so it can be found.

It would be great if you can add this fallback. Placing the fonts in the same folder is no problem for me and is a nice compromise to get out of the box functionality.

Full support for inlines is planned after 1.2 release. If you need it now we can transfer Span text into the outer TextBlock easily. But the properties set in the Span (like FontSize) will be lost, unless we override TextBlock properties with the properties of the first Span found inside the TextBlock.
Do you think this will work for you?

Yes, that will be great! My text is not fancy anyway and it will surely help to get my project up and running quickly. It will speed up my workflow a lot because it looks like:
Edit file in InkScape -> Export to xaml -> Test in Unity -> Edit file in InkScape -> Export to xaml -> Test in Unity, etc. If I have to open up the exported file and move the text out of the span all the time is a lot of work. I will deal with the FontSize issue later.

I noticed that if the rotation center is at the center of the bounding box (default, 0.5,0.5) it is not even added to the xaml file when using Blend, so presumably this is part of the spec. However, if you want to rotate an object from code using NoesisGUI, you have to force the rotation center to be 0.5,0.5 because it defaults to zero. Shouldn't it default to the center instead?