Forums | NoesisGUI

I had one quick question you noted we no longer needed to have a .font file for fonts. I'm having a hard time using a different FontFamily then the default it comes with I tried doing like FontFamily="../HUD/Fonts/fontname.ttf" I'm guessing this is incorrect way to do it since my xaml wont build with this. Any help is appreciated.

FontFamily="Fonts/#Roboto"

I had one quick question you noted we no longer needed to have a .font file for fonts. I'm having a hard time using a different FontFamily then the default it comes with I tried doing like FontFamily="../HUD/Fonts/fontname.ttf" I'm guessing this is incorrect way to do it since my xaml wont build with this. Any help is appreciated.

Effectively, .font files are no longer needed. But the way you use fonts is the same as in v1.1. You must set the property FontFamily to the desired family. For example:

Code: Select all

FontFamily="Fonts/#Roboto"

This will use a .ttf file in the Font folder that includes the Roboto family.

Some newly failing properties:

Ignoring unknown member Image.FlowDirection
Ignoring unknown member ContentPresenter.RecognizesAccessKey
Ignoring unsupported property 'IsGrouping' setting Trigger.Property

Also, the resolving of font paths seems to have changed, and it's now looks from the root of the Unity project. This is fine if it is intentional (much more consistent with Blend), just want to ensure it is so a fixup can be written. Image references still appear to be relative to the XAML though.

These properties were never really implemented, just defined (like many others) to make the xaml files build without errors. But sometimes people write about these properties not working (of course, there was no code using that properties), so we decided to remove the properties (and functions) from the API that are not doing anything, and just warn users that they are not supported (yet).

About the font/image paths we tried to solve the problems described in the issue 351 you posted in our bugtracker.

Now, when a URI is found in a xaml that uses the format "/ReferencedAssembly;component/Some/Path/Folder/image.png", we look up in the directory tree for the Blend project file. If the .csproj is found then we convert the resource path relative to the xaml path using the project file as the common path point to resolve it. If the .csproj is not found, then we treat resource path as a subdirectory of where xaml is located.

This is done for any resource reference: font, image, even merged dictionaries, so the behavior should be the same in all cases. If you are experiencing problems with this, please explain what is happening in the aforementioned issue in the bugtracker.

Thanks for your collaboration

Hi,

can you tell me whether the latest changes of version 1.1.12 are already implemented in v1.2b?

• Fixed: Button not reacting to interaction when changing Visibility per frame.
• Fixed: DefaultStyle padding bindings.
• [Unity] Under certain conditions, Image Effects affects to NoesisGUI.
• [Unity] Exposed UIElement.UpdateLayout() to C#.
• [Unity] Support for passing string to HeaderedContentControl.SetHeader().
• [Unity] Fixed: Noesis.UserControlSource not needed in not final classes.