It should keep counting. It’s all based on the stored start time value and duration, if you had hit the pause button. Only time I think it wouldn’t work is if you are using user specific columns and you are not using sign in on an app. Then user specific columns are not stored after an app is closed
JackVaughan awesome that the stopwatch component has been added. I’d definitely like to use it in one of our apps.
Question; Does the StopWatch have to be used in a form in order to save the data for the user?
The RUN ONE example is using the Stop Watch in a form.
This means the user has to stay on the form screen while the timer is running, otherwise it resets.
Earlier today I was testing the Stopwatch outside of a form and it continued to track while you moved around the app.
However this has now stopped happening. When I move tab from the screen where stopwatch is it now resets to zero. Did something change?
I expect this is unlikely to fit most use cases.
Every app I can think of allows you to move away and come back to different tabs etc.
I think two things would make the Stop Watch 10X more usable in way more use cases:
Change the stop button to a ‘reset’ button (with text to make clear) to avoid user’s deleting data accidentally.
Re-enable the stopwatch continuing to track while moving off screen (like it was doing this morning and yesterday) - or check if it is a bug. Once this is done, you can have a button with an Action Workflow to save the Stopwatch data onto a different Sheet via the ‘add row’ function.
Starting a stopwatch will set the Start Time column to the time the button was clicked and the stopwatch calculates the difference between now and that start time.
Pausing the stopwatch will clear the Start Time column and set the Duration column with the elapsed time that was calculated between the previously set start time and the time that the pause button was clicked.
Starting the stopwatch after a pause will set the Start Time with the current time that the button was clicked and performs some behind the scenes math to add the duration value to the difference between now and the newly start date.
Clicking Stop will reset and clear everything.
I know it’s confusing and in my opinion, Stop should be Reset and Play/Pause should be Start/Stop, but once you understand how it works then it all makes sense. The columns used for the stopwatch should really be user specific columns and only thought of as temporary placeholders to make the stopwatch function properly. Some sort of action initiated by the user would be what’s used to permanently save any values you need from those temporary column values.
If you need to save values from the stopwatch, then you really need to have additional math columns to calculate your own duration in real time, or whatever you need, then a button with an action that will write those calculated values to whichever column you choose.
Glide… very nice component… one of the greatest coolest… but not really usable in real applications (like event picker)… so I started playing with it … when start time is ahead (-) mark is not in the right position! i know you guys add zero to complete view… but you did not test it for the countdown… and please add size of the component that is universal… that is request for all components! is so hard to mach without CSS space when we are replacing components with visibility… screen jumps… not professional…