5 ms·

I've often wondered why this kind of confirmation couldn't be conditional on the confidence that the click / touch was intentional? As an example, my favourite

I've often wondered why this kind of confirmation couldn't be conditional on the confidence that the click / touch was intentional? As an example, my favourite pet peeve was using Visual Studio with old-school, upfront locking source control (like TFS), and then accidentally drag and dropping a file or folder due to lag in remote desktop, or a failing mouse which sent two click events in 1 ms or something. VS duly pre-emptively locks the 10k files in the folder you just dragged, and begins a 5 minute operation you'll have to somehow undo later, even though it should be fairly obvious from the click events that it was non-intentional. Going back to the meeting example, surely solid, accurate taps in the center of the hang-up icon could be taken as intentional, but a kind of glancing, less accurate one needing confirmation?

EarthLaunch 6y ago
That type of approach is the way forward in UI. Maybe if we call it something silly like MLUX it will catch on sooner. Another instance of the same principle is that if an unexpected button/element appears and I click it in <30ms or whatever the fastest possible read+react time is, the click isn’t intentional and should be ignored or confirmed. This should scale over time based on user familiarity and speed. This culminates at: > as the technology became more sophisticated the controls were made touch-sensitive - you merely had to brush the panels with your fingers; now all you had to do was wave your hand in the general direction of the components and hope. [HHGTG]
- tpxl 6y ago
  Changing the way buttons behave that is completely opaque to the end user is a good way backwards. > if an unexpected button/element appears and I click it in <30ms Easily solvable by locking the buttons for a few seconds (or less).
  - EarthLaunch 6y ago
    Disadvantage there is advanced users know where the button will land and have to wait.

EarthLaunch 6y ago

That type of approach is the way forward in UI. Maybe if we call it something silly like MLUX it will catch on sooner. Another instance of the same principle is that if an unexpected button/element appears and I click it in <30ms or whatever the fastest possible read+react time is, the click isn’t intentional and should be ignored or confirmed. This should scale over time based on user familiarity and speed. This culminates at: > as the technology became more sophisticated the controls were made touch-sensitive - you merely had to brush the panels with your fingers; now all you had to do was wave your hand in the general direction of the components and hope. [HHGTG]

tpxl 6y ago
Changing the way buttons behave that is completely opaque to the end user is a good way backwards. > if an unexpected button/element appears and I click it in <30ms Easily solvable by locking the buttons for a few seconds (or less).
- EarthLaunch 6y ago
  Disadvantage there is advanced users know where the button will land and have to wait.