#if SKIA_GTK/WPF support in main project

[DmitryBorodiy]

What do you need help with?

Previously, I used #if to write platform-specific code for a specific platform, but now this feature has been partially removed. How can I, for example, now call specific APIs of WPF/GTK projects or work with their controls?

[jeromelaban]

Thanks for the answer. What do you mean by partially removed?

[jeromelaban]

An update on this thread: With the introduction of Uno 5.2, differentiating for each underlying target is changing with the removal of Gtk by default. It is a scenario we'll be working on in a near future, to provide the ability to determine which is the active target in order for native libraries to integrate properly.

[DmitryBorodiy]

So, Is gtk still supported by Uno?

[jeromelaban]

We will not be removing support for it, but we're not going to make improvements to the GTK support in the future. We'll be moving to native X11/WPF/macOS support directly, and the airspace support will improve soon around these targets.

[lindexi]

After conducting tests in Avalonia, I found that using the GTK framework as the underlying layer results in subpar performance. This is due to the fact that the GTK layer informs X11 to render the entire screen for each frame, leading to potential performance issues. However, if X11 is used as the underlying layer, performance can be improved by controlling the rendering range of X11 through XPutImage. The bad news is that I don't seem to have found a mechanism in UNO to refresh only the dirty range.

[MartinZikmund]

We will be improving rendering performance as we go, dirty rect rendering is something we would like to introduce as part of it, but there are other things to tackle first (e.g. separate compositor thread)