3 ms·

Window restoration was not recently released, it was put in as experimental and it'll probably be another 5 years before it's available on stable distros as a n

Window restoration was not recently released, it was put in as experimental and it'll probably be another 5 years before it's available on stable distros as a non-experimental flag protocol. >A significant portion of the problems listed, e.g. performance, "unpredictable focus", glitches, freezes, etc., will generally be purely KiCad bugs The issues have been looked into and they are purely Wayland bugs. If things work on Windows, macOS and X11 without any platform specific ifdefs, the problem is Wayland ;)

arghwhat 1y ago
> Window restoration was not recently released, it was put in as experimental and it'll probably be another 5 years before it's available on stable distros as a non-experimental flag protocol. That's not how Wayland protocol maturity works. Protocols of interest are picked up immediately and graduate to stable after wide adoption. The naming was also changed to "staging" instead of "unstable" to clarify this. (Case in point, linux-dmabuf was only recently stabilized, and many protocols in mainstream use are not "stable"). > The issues have been looked into and they are purely Wayland bugs. Bugs reproducible only with their Wayland platform code ≠ Bugs in Wayland. > If things work on Windows, macOS and X11 without any platform specific ifdefs, the problem is Wayland ;) Not at all how things work, no. :)
- IshKebab 1y ago
  > Protocols of interest are picked up immediately and graduate to stable after wide adoption. Yeah... good luck changing your protocol after it's been "staging" for 5 years and everyone has adopted it.
  - arghwhat 1y ago
    Again, not how Wayland protocol maturity works. All released protocols are versioned, and do not break existing clients. Servers offer a maximum version number for their protocols, and clients can request any version up until that maximum version. If they request an older version, the server will behave in accordance to the older specification. A staging protocol may end up being replaced and slowly deprecated, or have more breaking changes in new versions than you would find in a stable protocol, but a client using a particular protocol can rest assured that a server offering the protocol will adhere to the same version of the protocol contract the application was written against.
- duped 1y ago
  > Not at all how things work, no. :) It is, though. If something works as you expect on the platforms where the majority of your users are then the weird one is just going to be ignored.
  - arghwhat 1y ago
    No, having bugs in home-grown platform specific code is not at all related to whether or not the platform is "weird". Platform integrations are a lot of code, which you might have bugs in, and why people tend to use toolkits that do the work and abstract it away for you. Even if platforms look like they're providing similar high-level features, they will look nothing alike underneath. If you roll it yourself and have bugs in your code, that's fine but not the platforms fault.

arghwhat 1y ago

> Window restoration was not recently released, it was put in as experimental and it'll probably be another 5 years before it's available on stable distros as a non-experimental flag protocol. That's not how Wayland protocol maturity works. Protocols of interest are picked up immediately and graduate to stable after wide adoption. The naming was also changed to "staging" instead of "unstable" to clarify this. (Case in point, linux-dmabuf was only recently stabilized, and many protocols in mainstream use are not "stable"). > The issues have been looked into and they are purely Wayland bugs. Bugs reproducible only with their Wayland platform code ≠ Bugs in Wayland. > If things work on Windows, macOS and X11 without any platform specific ifdefs, the problem is Wayland ;) Not at all how things work, no. :)

IshKebab 1y ago
> Protocols of interest are picked up immediately and graduate to stable after wide adoption. Yeah... good luck changing your protocol after it's been "staging" for 5 years and everyone has adopted it.
- arghwhat 1y ago
  Again, not how Wayland protocol maturity works. All released protocols are versioned, and do not break existing clients. Servers offer a maximum version number for their protocols, and clients can request any version up until that maximum version. If they request an older version, the server will behave in accordance to the older specification. A staging protocol may end up being replaced and slowly deprecated, or have more breaking changes in new versions than you would find in a stable protocol, but a client using a particular protocol can rest assured that a server offering the protocol will adhere to the same version of the protocol contract the application was written against.
duped 1y ago
> Not at all how things work, no. :) It is, though. If something works as you expect on the platforms where the majority of your users are then the weird one is just going to be ignored.
- arghwhat 1y ago
  No, having bugs in home-grown platform specific code is not at all related to whether or not the platform is "weird". Platform integrations are a lot of code, which you might have bugs in, and why people tend to use toolkits that do the work and abstract it away for you. Even if platforms look like they're providing similar high-level features, they will look nothing alike underneath. If you roll it yourself and have bugs in your code, that's fine but not the platforms fault.