Timeline for How to prevent accidental button press?
Current License: CC BY-SA 3.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 20, 2017 at 1:18 | history | tweeted | twitter.com/StackUX/status/887844244349534208 | ||
| Jul 19, 2017 at 9:31 | comment | added | DarrylGodden | I like this suggestion (TripeHound), make your reporting smart enough to filter out sub 5 minute entries and associate the time to the next task, or whatever works for your company. | |
| Jul 19, 2017 at 9:23 | comment | added | TripeHound | Avoid the issue. Trust your workers enough so they are able to delete/amend an accidentally started/stopped task. | |
| Jul 19, 2017 at 8:39 | answer | added | cameraman | timeline score: 3 | |
| Jul 19, 2017 at 7:22 | comment | added | DarrylGodden | How does the system know which task you are starting and stopping for? You have two tasks in your example, but only one button. | |
| Jul 19, 2017 at 7:08 | answer | added | Frantisek Kossuth | timeline score: 2 | |
| Jul 19, 2017 at 6:21 | comment | added | Darren H | Once the button is pressed to tell the system a task is stopped, can that same task be started again? If so, the user could simply press start again. You could have the system "smooth over" small gaps. For example if a user stops a task then starts the same task within 30 seconds (or whatever time is appropriate) the stop/start action is ignored | |
| Jul 19, 2017 at 5:34 | answer | added | DesignerAnalyst | timeline score: 2 | |
| Jul 19, 2017 at 4:59 | answer | added | Michael Lai♦ | timeline score: 1 | |
| Jul 19, 2017 at 3:55 | history | asked | catandmouse | CC BY-SA 3.0 |