I tried enabling the sRGB flag and yes, the text is rendered brighter. However, for larger size of text, it also makes the text bolder. Below is the capture (left side is Noesis with sRGB, right is WPF). Upper text is 9pt font. Lower text is 12pt font. sRGB.PNG From performance point of view, is the...

We don't plan this change for the upcoming 2.1 version.

Ok. I think we can live without it for now. The point is, I think you don't need to sacrifice the performance by forcing boxing/unboxing of non-component values.

BTW, How about the lambda support ? Is it coming soon ?

Ah, my bad. Didn't realize that the path can be absolute or relative. Thanks.

@nokola,

For C++, implementing a custom provider that can reads System fonts was easy by reusing the CachedFontProvider (see previous answer in this thread). Not sure about the C#/Unity one though.

Hi, thanks for the information ! I now understand some historical reasons behind this behavior. Here is a comparison of Noesis - UWP - WPF. It confirms what you said that UWP also drop colored anti-aliasing. Somehow, they render with higher intensity (I apply the same #FFFFFFFF as the font color). N...

Hi, Is there any way to make font rendering in NoesisGUI crisper ? Below is a screenshot comparing NoesisGUI on the left with WPF on the right. The font size is 9pt. (Please download the attach file and view it directly with an image viewer to see the difference better). FontRendering.PNG It might b...

Yes, problem is that the DependencyPropertyChangedEventArgs you receive cannot be a template, so you would need to cast it to the templatized version. I think it is OK if the framework does the casting (internally). The framework can make sure the casting always succeed. From the user perspective, ...

I have the following directory setup: <root>/Xaml/*.xaml <root>/Font/*.ttf and a xaml file which load a font "Fonts/#Arial Unicode MS", as follows. <UserControl x:Class="NoesisTutorial.Tutorial" xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation" xmlns:x=&...

The leak is related to PlacementTarget property for sure, I don't think Header binding has anything to do. I am not sure, but in my environment the leak doesn't happen if I removed the Binding. I filed the issue: #001153 BTW, is there any diagnostic techniques to detect memory leaks when it happens...

I filed the issues: #001151 and #001152.