Probably would fall into scope of a compositer in Wayland, rather than the protocol. I suspect it originated with old CRT displays. Sometimes they can appear scan diagonally.
Even without that usecase, I think it’s great to have around in order to support novel displays and display-like devices.
Looks through the algorithm bits in the various sections. How would you implement that? The answer is invariably by copying the highly nested statements of the spec directly into your language. Maybe there’s a better way, but you’d have to understand all that nested logic first, and you’d be exhausted at that point and just want to move on.
Rotating the display by a custom angle is possible through xrandr on X.org.
There’s no Wayland protocol for custom angle rotation, and I don’t expect anyone to create a protocol extension without a use-case.
My wild guess: Theoretically it should be possible for a compositor to support similar custom rotation, as applications simply draw to their surface (window), without knowing how and where it is displayed on the viewport (display).
But it might require quite a bit of work, depending on the project, so I don’t expect to ever see custom rotation on anything besides smaller/niche compositors.
There’s no Wayland protocol for custom angle rotation, and I don’t expect anyone to create a protocol extension without a use-case.
Puh-lease. It’s Wayland; the devs fully and honestly expect every app developer (eg.: calc, Libreoffice, notepad.exe) to implement custom angle rotation on their own.
No one does this kind of stuff because someone asked them to do it. This is the kind of useless, insane stuff you do for the lulz, or because someone dared you.
That, right there, is a perfect example of why folks need to stop trying to shoehorn web apps everywhere they don’t belong. It’s a use-case for a proper native mobile app if ever there was one.
That’s why you should’ve just handled arbitrary rotations instead of inventing a finite predefined set of orientation “modes” in the first place.
Things get a lot easier in the long run if you aggressively look for commonalities and genericize the code that handles them instead of writing bunches of one-off special cases.
programmer_humor
Hot
This magazine is from a federated server and may be incomplete. Browse more on the original instance.