Eindhoven, the Netherlands
See my homepage at https://proycon.anaproy.nl for further details and contact info. Projects also at https://codeberg.org/proycon
From Maarten van Gompel to ~mil/sxmo-devel
On Tue Apr 22, 2025 at 9:38 PM CEST, Aren wrote: > On Sat, Apr 19, 2025 at 04:22:54PM -0700, Anjandev Momi wrote: >> There are devices that use the same device name but different form >> factor. For example, a raspberry pi may have a touch screen or may be in >> a blackberry form factor. >> >> Remove this prompt cause it is annoying for users > > I think there's still some cases where the user experience will be worse > if there isn't a device profile. The one that comes to mind is using the > volume keys to scroll in the menus is significantly slower if > SXMO_VOLUME_BUTTON isn't set. I agree, I'm concerned that if we remove it entirely users may try sxmo
From Maarten van Gompel to ~mil/sxmo-devel
On Sun Apr 20, 2025 at 9:57 PM CEST, Anjandev Momi wrote: > Lets make sure we dont accidentally ship broken docs and have to redo > the release. Moreover, we should catch failing html docs in this repo > becuase sxmo.org relies on it. Great idea, applied! -- Maarten van Gompel (proycon) web: https://proycon.anaproy.nl gpg: 0x39FE11201A31555C
From Maarten van Gompel to ~mil/sxmo-devel
Merged! -- Maarten van Gompel (proycon) web: https://proycon.anaproy.nl gpg: 0x39FE11201A31555C
From Maarten van Gompel to ~mil/sxmo-devel
Thanks! Merged along with the other drawing patches -- Maarten van Gompel (proycon) web: https://proycon.anaproy.nl gpg: 0x39FE11201A31555C
From Maarten van Gompel to ~mil/sxmo-devel
On Wed Apr 16, 2025 at 6:00 PM CEST, Willow Barraco wrote: > Ah, great o_O I might need more clues here. I have tested on River just > now, and I do not reproduce those issues. Which version are you running? Interesting, on my laptop with 0.4.0-dev.49+5597498 everything seems fine indeed. On my desktop with 0.3.7 the problem does occur. Not sure if it's just the river version or maybe the fact that I'm on a dual screen setup on the latter? In any case it only happens with this patch, without it things work fine. -- Maarten van Gompel (proycon)
From Maarten van Gompel to ~mil/sxmo-devel
The crash is indeed fixed now; but I do run into two other issues with this patch now (on river in landscape mode): 1. switching layers doesn't work anymore (button does nothing) 2. the compose layer doesn't work anymore -- Maarten van Gompel (proycon) web: https://proycon.anaproy.nl gpg: 0x39FE11201A31555C
From Maarten van Gompel to ~mil/sxmo-devel
(Marked as applied)
From Maarten van Gompel to ~mil/sxmo-devel
Thanks! This looks very promising. I hadn't really noticed the tearing before but double buffering is definitely a good solution. There's one major issue currently though, I'm getting a segfault when launching on a landscape monitor with -L 300 (or any other value above 200 for that matter). Marking as need revision. -- Maarten van Gompel (proycon) web: https://proycon.anaproy.nl gpg: 0x39FE11201A31555C
From Maarten van Gompel to ~mil/sxmo-devel
ΠΡΠΊΡΡ! Applied with a minor fixup for spacing on the next padding line. -- Maarten van Gompel (proycon) web: https://proycon.anaproy.nl gpg: 0x39FE11201A31555C
From Maarten van Gompel to ~mil/sxmo-devel
* focused window detection for menus * fixed river config file permission * switching to next/previous workspace (tag actually) --- Makefile | 2 +- configs/appcfg/river | 3 ++ .../{srmo.desktop => sxmo_river.desktop} | 2 +- .../default_hooks/sxmo_hook_contextmenu.sh | 32 -------------- configs/profile.d/sxmo_init.sh | 5 +++ docs/sxmo.7.scd | 3 +- scripts/core/sxmo_dmenu.sh | 2 +- scripts/core/sxmo_migrate.sh | 2 +- scripts/core/sxmo_togglewm.sh | 2 + scripts/core/sxmo_wm.sh | 42 ++++++++++++++++++- [message trimmed]