You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On a more technical level, yes, you are right, KiCad can be compiled for Wayland natively. Yet, there is at least one thing which still breaks quite horribly then: dockable windows (KiCad uses wxAUI for this). And, at least a few months ago, when another user proposed to switch this flatpak to Wayland native, there was a serious issue with overflowing windows on displays with fractional scaling, see my comment on the PR for a screenshot None of these issues are KiCad's faults, but require work on other projects:
Wayland still missing certain protocols (most notably for dockable windows). There is work ongoing here for several years now, it's a massive effort. If you are interested, look at the discussion of the most recent proposal (which is the 3rd or 4th proposal, all of which were discussed at similar lengths): https://gitlab.freedesktop.org/wayland/wayland-protocols/-/merge_requests/264
wxWidgets having to implement the protocol (once Wayland stakeholders have settled on one) in an officially released version.
As it stands now, I would think that official Wayland support is still at least a year away, but I might be wrong. It all depends on Wayland + wx Devs though, not necessarily KiCad Devs.
I intend keeping this issue open for informational purposes until we can switch this flatpak over to Wayland native.
KiCad supports Wayland, any reason why is not enabled here yet?
The text was updated successfully, but these errors were encountered: