Hey Aren,
The first part, with default bindsym on media keys to emulate Return, Up
and Down, is a brillant idea. I think it should works by itself, and
offer a good enough alternative if sxmo_menumode_toggler.sh fails to
switch the layout.
But I disagree with most of the changes from sxmo_swayinitconf.sh:
First it is pointless to use the legacy sxmo_multikey.sh if we can't set
the input delay and rate. It expects those values.
Then I'm not sure we want to map every media key to bonsaictl. Only the specific
inputs should behave like this imo.
I'd like to know what others thinks about that last part.
Willow
On Sat, Sep 16, 2023 at 09:31:52AM +0200, Willow Barraco wrote:
> Hey Aren,> > The first part, with default bindsym on media keys to emulate Return, Up> and Down, is a brillant idea. I think it should works by itself, and> offer a good enough alternative if sxmo_menumode_toggler.sh fails to> switch the layout.
Cool, I'll split this part into a separate patch so it's not blocked by
discussion on the rest of this patch.
> But I disagree with most of the changes from sxmo_swayinitconf.sh:> > First it is pointless to use the legacy sxmo_multikey.sh if we can't set> the input delay and rate. It expects those values.
Perhaps it would make sense to only bind a single button press
(bypassing multikey) if we can't set the repeat rate? That way the
buttons will still work for basic tasks like unlocking.
> Then I'm not sure we want to map every media key to bonsaictl. Only the specific> inputs should behave like this imo.
I'm firmly of the opinion that not mapping every input adds extra
complexity without much benefit. Currently we have to maintain a
database of every possible input device that should trigger the
inputhandler, which is already getting bulky. If we drop this
requirement it would be a big step towards not needing deviceprofiles
for every new device.
It's inconsistent that dwm maps every input device, and sway only maps
specific ones. And I find it a bit counter-intuitive that some input
devices work one way and others another.
> I'd like to know what others thinks about that last part.> > Willow
> > But I disagree with most of the changes from sxmo_swayinitconf.sh:> > > > First it is pointless to use the legacy sxmo_multikey.sh if we can't set> > the input delay and rate. It expects those values.>> Perhaps it would make sense to only bind a single button press> (bypassing multikey) if we can't set the repeat rate? That way the> buttons will still work for basic tasks like unlocking.
Agreed! And we could bypass the multi key script completly in this case.
> > Then I'm not sure we want to map every media key to bonsaictl. Only the specific> > inputs should behave like this imo.>> I'm firmly of the opinion that not mapping every input adds extra> complexity without much benefit. Currently we have to maintain a> database of every possible input device that should trigger the> inputhandler, which is already getting bulky. If we drop this> requirement it would be a big step towards not needing deviceprofiles> for every new device.>> It's inconsistent that dwm maps every input device, and sway only maps> specific ones. And I find it a bit counter-intuitive that some input> devices work one way and others another.
Okay but then let's limit this to non desktop SXMO_DEVICE_NAME. Vol keys
are important when we don't have access to lisgd left edge swipes.