Use WinUI for the interface.
Use WinUI rather than FluentWPF for the interface of this software, because as a first-time user, the current interface is not visually aesthetically pleasant during observation of it, especially its side-bar.
The claim that it is not visually pleasant is surely a personal opinion. However WinUI3 is not ready to be used with unpackaged applications yet. We have looked into it, and it was not mature enough for our deployment scheme when Version X development picked up pace.
The settings page is not scrollable with touchscreen. Could this be caused by FluentWPF?
Fluent WPF is only used for Acrylic. I will see what the cause of Touchscreen scrolling is.
thanks for reporting, didn't knew that!
The settings page is not scrollable with touchscreen. Could this be caused by FluentWPF?
this is now fixed. You can track its state in #309 However, in the future please create a new issue (if it hasn't already reported before and could be found with the search function). Touchscreen not scrolling is enough of an issue on its own to warrant creating one! But also thank you for trying to be convservative with opening new issues!
I take it WinUI3 is still not ready?
I take it WinUI3 is still not ready?
It is ready, but it's too time consuming to quickly realize, as we have to rebuild the entire frontend from scratch and figure out a way to ship the WinAppSDK unpackaged stand-alone.
It's unlikely to happen before 2025.