Documentation update and feature request

[EletroMe]

I encountered two main issues after the latest update on Bazzite (Fedora Atomic/KDE Plasma):

Documentation Gap: The docs state Bazzite is unsupported and recommend the AppImage (Affinity-3.2.0-x86_64.AppImage), which failed on my system (opened the DPI selector and Wine, but the app itself never launched). However, using Distrobox with the Python GUI installer worked flawlessly.

Suggestion: Explicitly document the Distrobox method as a primary solution for immutable distributions like Bazzite. This would significantly help users on similar systems.
Minor UI Glitch: The app icon duplicates in the taskbar briefly during the loading phase before consolidating once the app is ready. It’s not critical, but worth noting.

Feature Request (Global Menu): I discovered that integrating the app’s menu into KDE’s Global Menu is possible, but only with Wine versions 12.0+ (which include the necessary appmenu patches). The current recommended version (11.x) lacks this support.

Question: Are there plans to upgrade the bundled Wine to version 12.0 or higher? Achieving 100% system integration via the Global Menu would be a major quality-of-life improvement.
Thanks for the great work on this project.

[MLuc24]

Your reading of the docs is right, and there is a detail that makes the documentation request stronger than "please add Distrobox". The README does send unsupported distros to the AppImage, but that AppImage is published under the Affinity-wine-10.10-Appimage release tag, while the Python installer's default is Wine 11.12. So what Bazzite users are pointed at is not a repackaging of the supported path, it is an older Wine than the supported path. That is a plausible reason yours reached the DPI selector and then stalled while Distrobox plus the installer worked cleanly — you were not really comparing AppImage against Distrobox, you were comparing Wine 10.10 against 11.12.

On the Global Menu question, the version numbers are less comparable than they look. The installer's Wine switcher offers 11.12, 11.12 v4 for Zen 4/5, 10.10 and 9.14, and all four are ElementalWarrior builds — a fork carrying the AMD GPU and OpenCL patches Affinity depends on. So 12.x is not a bump of upstream Wine here; it needs that fork to publish a 12.x carrying those patches, with appmenu support sitting on top rather than in place of them. Whether it is planned is the maintainer's to say, but "is there an ElementalWarrior 12.x yet" is the more answerable form of the question, and it also explains why staying on 11.x is not simply conservatism.

The taskbar duplication has a concrete cause you can check. Nothing in the installer sets StartupWMClass on any of the .desktop files it writes, so during launch KDE has no way to match the Wine window back to the launcher entry and tracks it as a second, unmatched task until the window settles. Adding StartupWMClass= with the class the window actually reports — xprop WM_CLASS on the running app will tell you — should collapse it to one icon. Cosmetic, but a one-line fix rather than a Wine-level problem.