News for hackers. Stuff that matters.

A comment on Try quickly typing 1+ 2 + 3 into the iOS 11 Calculator. Parent comment

Re:Try quickly typing 1+ 2 + 3 into the iOS 11 Calculator by jamesrom on Tuesday October 24, 2017 @09:59AM (#15541532)
An example that comes to mind is a slider switch (iOS is famous for them)

You don’t want the switch activated until it’s all the way left or right.

[ Parent | on HN ]
Re:Try quickly typing 1+ 2 + 3 into the iOS 11 Calculator by stult on Tuesday October 24, 2017 @10:01AM (#15541553)
An even simpler example is page-based navigation. Can't register UI hits while pages are animating in and out.
[ Parent | on HN ]
Re:Try quickly typing 1+ 2 + 3 into the iOS 11 Calculator by dajt on Sunday November 05, 2017 @06:18PM (#15632380)
What if you want to quickly flick through pages? Having to wait for each page to render would be awful.
[ Parent | on HN ]
Re:Try quickly typing 1+ 2 + 3 into the iOS 11 Calculator by mannykannot on Tuesday October 24, 2017 @10:35AM (#15541830)
Slider controls might be a better example, I think. In that case, the position reached by the moveable element is the data, and it is appropriate to take the value from the UI element (of course, if it lags noticeably, that is a UI design issue.) With slider switches, you could argue it either way, so long as program and UI remain consistent, but again there is a problem if the UI response lags the gesture.
[ Parent | on HN ]