6 ms·
> Yeah the hold and drag interaction model sure looks fancy but isn't very ergonomic. I beg to differ. I find hold-and-drag menus faster to interact with when
by funcDropShadow 3y ago
> Yeah the hold and drag interaction model sure looks fancy but isn't very ergonomic.
I beg to differ. I find hold-and-drag menus faster to interact with when using a mouse, trackback or a touchpad. But it is possible to support it, while not requiring it. On button down the system enters a state where one of three things can happen.
1. The button is released. Then the menu should togle open and wait for another click and relase to select an entry.
2. The pointer moves more than a threshold. Then the hold-and-drag behavior is initiated.
3. 50ms or similar pass and the hold-and-drag behavior in initiated.
The last case is to avoid flickering in case somebody has a slow click and release cycle.
This or similar behavior used to be (still is) default behavior of many desktop UI toolkits.
- cush 3y ago> I beg to differ. I find [them] faster I think you’re measuring a different dimension than I am. I’m talking about ergonomics and accessibility, not speed. Stretching several inches up a screen in a single gesture breaks most fundamental UI design guidelines. It’s hard for people to pull off quickly and accurately. Not to mention the fact that it doesn’t allow for longer lists so just isn’t useful in general, unless the menu is toggled open to be scrollable.