1. OTF fonts format seems to not supported anymore. I've converted fonts to TTF to fix that, but it was just guessing as NoesisGUI doesn't display any meaningful error for that, just "font not found". Also I can't find any tutorial regarding fonts and Unity3D.

[dx9] Assets/Test/Test.xaml
Parsing TextBlock.FontFamily (@41,8).
'Fonts/Arial' string cannot be converted to FontFamily

2. for MouseEventArgs the "e.position" replaced with "e.GetPosition()" (and you need to provide value for that, "null" (like in WPF) is crashing Unity - I've reported the issue to the bugtracker).

3. some controls like ScrollViewer, ItemsControl and WrapPanel now have Border or/and Background by default, so you need define default style for them and set these fields to {x:Null} (previously it works without issues).

About the error, if a resource is not found a message should be logged to the console when building the xaml, something like this:

Code: Select all

[dx9] Assets/Test/Test.xaml
Parsing TextBlock.FontFamily (@41,8).
'Fonts/Arial' string cannot be converted to FontFamily

3. some controls like ScrollViewer, ItemsControl and WrapPanel now have Border or/and Background by default, so you need define default style for them and set these fields to {x:Null} (previously it works without issues).

Yes, our default style sets a border and background to base control classes (Control, ContentControl, ItemsControl, ScrollViewer... but not to Panels like WrapPanel) to give some kind of visual feedback to the user if they don't provide a suitable template. Do you think it is better to leave these properties to the default null?

I've spent much time to found all grey borders/backgrounds controls and override them in styles, it was really surprising as my custom controls (inherited from ContentControl and other base types), for which I didn't set Border or Background in 1.2.0, was rendered with them. And I'm sure it will confuse new users, who develop their UI in WPF prototype and them copy-paste XAML to use with NoesisGUI. So I would like if you remove borders/background...

I've spent much time to found all grey borders/backgrounds controls and override them in styles, it was really surprising as my custom controls (inherited from ContentControl and other base types), for which I didn't set Border or Background in 1.2.0, was rendered with them. And I'm sure it will confuse new users, who develop their UI in WPF prototype and them copy-paste XAML to use with NoesisGUI. So I would like if you remove borders/background or at least mention about them in documentation with a "reset styles" XAML code presented nearby (to help people who don't need these borders/backgrounds get rid of them).

+1! NoesisGUI rendering should be as close to WPF and/or Blend (design-time) rendering as possible! So please remove/fix all the styles those break this compatibility!

I've spent much time to found all grey borders/backgrounds controls and override them in styles, it was really surprising as my custom controls (inherited from ContentControl and other base types), for which I didn't set Border or Background in 1.2.0, was rendered with them.

+1! NoesisGUI rendering should be as close to WPF and/or Blend (design-time) rendering as possible! So please remove/fix all the styles those break this compatibility!

Ok, I understand and agree with you. We should behave like WPF as much as possible.
We will change our default styles in the following release.