4 ms·
Wayland messes up Visual Pinball as well [0]. VP depends on being able to place the main playfield window, the backglass window, and the Dot Matrix Display wind
by MegaDeKay 1y ago
Wayland messes up Visual Pinball as well [0]. VP depends on being able to place the main playfield window, the backglass window, and the Dot Matrix Display window in specific locations on specific monitors mounted in the cabinet.
[0] https://github.com/vpinball/vpinball https://github.com/vpinball/vpinball
- 0points 1y agoI'd place those windows exactly where I want with a sway config in about 2 minutes effort. Not a wayland issue.
- delfinom 1y agoThe fact you have to edit a config file means it's missing the boat by mile. A user should not have to learn config file formats in a graphical GUI interface.
- 0points 1y ago> The fact you have to edit a config file means it's missing the boat by mile. No. That's how i3 and sway works, on purpose, by design. I use sway, hence I claim to know how to do it in less than 2 minutes. i3 precedes wayland, so again, not a wayland issue. > A user should not have to learn config file formats in a graphical GUI interface. If <app> requires user to <insert skill>, then user will need to <insert skill> in order to use <app>. Well said, anon!
- MegaDeKay 1y ago<app> should not require user to <insert skill>. <app> should be permitted to do reasonable things without requiring user to come up with workarounds for missing functionality.
- 0points 1y agoIf that's your pet peeve, consider using another <app> with said guard rails and fluff. Meanwhile, maybe stfu with your opinions about my work flow.
- queenkjuul 1y agoWith X11, neither the application nor the user requires a window manager to place the window at all. The application can just put itself where it wants, even with no running window manager. That's the point.