Btw: If you want to configure your monitor setup in Sway and are not keen on calculating pixel offsets yourself:
There's a handy tool "wdisplays" 👌
https://github.com/artizirk/wdisplays
It does all the nasty math for you 😝
Btw: If you want to configure your monitor setup in Sway and are not keen on calculating pixel offsets yourself:
There's a handy tool "wdisplays" 👌
https://github.com/artizirk/wdisplays
It does all the nasty math for you 😝
I've already assumed that my touch pad was broken (or the driver was buggy) because after a tap-and-drag action, the mouse button was not released when releasing the finger from the touch pad.
It was "sticky", e.g. after marking multiple lines of text.
Just found out that this was introduced a while ago in Sway (to follow libinput recommendations):
https://github.com/swaywm/sway/commit/bbadf9b8b10d171a6d5196da7716ea50ee7a6062
Setting "drag_lock disabled" in the touch pad's config fixes this. 😌
As a mini-follosup #sway 1.12-rc1 has been working beautifully past few days. HDR works, specific window screencasting works.
I switched to vulkan renderer to enable some of that and all-in-all the whole desktop feels smoother somehow (not measured, trust me bro)
As a major bonus - Zoom calls do not seem to hurt the system nearly as much and CPU is mostly idling. I don't know if that's related to Sway change or Zoom finally fixed something...
@qasimrashid Great article, but is this #Sway software / app open source?
Installed #opensuse. Configured #sway the way I want it. Installed all applications I need. All git repositories are cloned. Everything is working fine. Now I can really start using and enjoying my setup.
So guess it's time to find a new #linux distro and start all over again. #distrohopping #distrohoppersanonymous