I'm finding that quite a lot when I intend to triple press the volume down button to close a program, that I end up getting two presses registered, and need to try again. I'm young and fairly agile, it may be that less agile people really will struggle to press 3 times in quick succession.
My suggestion would be to have closing a program be two presses on the volume down button rather than three.
~ozzeruk schreef:
I'm finding that quite a lot when I intend to triple press the volume down button to close a program, that I end up getting two presses registered, and need to try again. I'm young and fairly agile, it may be that less agile people really will struggle to press 3 times in quick succession.
My suggestion would be to have closing a program be two presses on the volume down button rather than three.
FYI, instead of pressing 3 times, you can also use 1 long press.
Works fine for me, and I'm some old 50+ dude ;)
-- Met vriendelijke groetjes - Jan Wagemakers -
Linux #1 SMP Debian 4.19.118-2+deb10u1 (2020-06-07) x86_64 GNU/Linux
Well I'm not that old but double press makes me ill. I would rather move out of buttons in general. They are not that endurable and are not for frequent use. I'd leave one press and long press. No multi-clicking IMHO.
Agreed that multiple presses are irritating for some people, and there could be a better/alternative solution. The problem becomes, what do you replace it with? If we cut out double press and triple press (but leave long press), we're left with only 6 total same-button combos. Of course, we're yet to leverage multi-button combos, and button-plus-gesture combos.
Triple presses are pretty much never needed (just hold down the button).
Wouldn't be opposed to make a 3 finger gesture for closing windows / launch surf / or menus. It wouldn't be necessarily a bad idea to have gestures for everything that the buttons can do in parallel, now that lisgd is freed up (..if the gestures were thought out well). Not sure if I'm a fan of the chording idea. In my ideal world the pinephone would have 10 physical buttons :)
I am planning on adding another way to open the menu via clicking on the right side of the dwm status bar - I think that will be pretty nice. Also could have the application context-menu come up for clicking on the window title. Not entirely sure - but seems like that might be an easy fix for buttonpress-less use.
I like dwm status bar approach. For three buttons we have the most important actions (imho) are: -- Launch st; -- Kill client; -- Activate screen lock; -- Shift current client in stack. With two of them on double click which I really hate now ;) Adding convenience -- Toggle svkbd; -- Launch menu we have comfortable six actions. The rest I've never used and/or they are easy accessible from menu.
Just a couple ideas of some things I've tried: I added the dwm-statusbutton patch for a button on the left side of bar to click and open the menu. I've also added statuscmd to be able to click on the statusbar to open svkbd.
My physical phone buttons are: Volume Up: 1 click = volume up, 3 clicks/long press = a screenshot script Volume Down: 1 click = volume down, 3 clicks/long press = kill app Power button: only using the single click for lock screen, but thinking about 3 clicks/long press to toggle flashlight.
Objectively, a lot of my double clicks seem to get misinterpreted as either a single click or triple click.
Subjectively, if I was the developer, I would move out of relying on the buttons altogether. One tap on the dwm bar would bring up a massive 3x3 grid overlay (sort of like an android dialpad). 9 buttons ought to be enough to replace all the button bindings. The grid can be enlarged to 3x4 or a second page can be added if more buttons are needed.
Closing for now - more or less this is by design. Users can change the keybindings / build their own dwm based on the multikey patch if desired. Also we have much more comprehensive gestures now that can do most of the things keybindings can.
~tahayassen - very delayed response, but in response to the grid idea. I did build a 'grid' feature (1) into dmenu so hypothetically a 3x3 or 3x4 grid is possible if you combine that patch with the mouse patch, I plan to do something atleast like a 2x6 or similar at somepoint for most Sxmo menus to save some space when I free up eventually.
