Start stopwatch and leave it running while visiting other tabs

My students will find it more practical if I am able to set the stopwatch to run in the background while they use the other tabs in the app. As it is, once they start the stopwatch, they are blocked from using the other features of the app. Most of the time this will make using the stopwatch a no go since they are waiting several minutes and need to get other work done. Is there a way to alter things so that this can be overcome?

How is it blocking them from using the app? I have a stopwatch on one tab, can start it, and still navigate around the app while it’s running. All it’s doing is writing the start time and/or duration to the sheet so the stopwatch knows where it’s at while counting. The stopwatch is just performing a realtime calculation based on that start time and duration set in the columns. It just makes that calculation look pretty with the stopwatch display and realtime count.


Hmm, that is not working for me… but let me login and try again. Last night it was not working but last night some weird things were happening with Glide- could hav been my internet connection or Glide team doing some behind the scenes work…

Still getting the same issue. I think now looking at it fresh, my problem may be that I am launching the stopwatch from a form button and it is in the form until I click submit. I used the first stopwatch demo app that Glide released last week because it allows my students to log their timings. I think I will need to make a second stopwatch component elsewhere for instances where the timer needs to be left to run in the background.

1 Like

Yep, that was it. Problem solved- I will add a second stopwatch component elsewhere for those scenarios. Thanks Jeff


If you still need the stopwatch values in a form later, you can have the stopwatch outside of the form, run it, then pull the stopwatch values in through the column value components in the form.


Oooohh, thanks a great tip, thank you!

1 Like

Hi all,
I have the same problem @Todd_Lichtenwalter was having. I have two stopwatches implemented in a tab (detailed layout) and, as soon as I hit “back” to work on other tabs, the counts disappear.
I tried to create a tab dedicated to stopwatches, but it behaves the same (as I change tab, stopwatches reset to zero).

Is there a solution for it? Shouldn’t the stopwatch only pause/reset when the pause/reset buttons are tapped?

Does the start time stay in the sheet after you start the stopwatch and change tabs? Are you sure that your stopwatch is not inside of a form?

Actually I have noticed it does not write any values in the table. I had two stopwatches, now I only have put one. In the related sheet tab, I have two columns: Stopwatch and duration. they have been edited in glide as “time” and “number”.
Am I doing something wrong on the table itself?

Is your stopwatch inside of a form or in a details screen?

Do you have the stopwatch set to fill those columns you created?

Does your screen have a row that it is attaching to, so it can update those columns in that row?

I am not sure I fully understand, I’ll try.

the stopwatch is in a details (layout) screen, added as component.

The referring Google sheet tab only has two values: “Stopwatch” and “duration 1”. These have been recognized by Glide as column headers, and I have set them as “time” and “number”. I do not know what you mean by “speedy set”

there are still no row values in the Google sheet or in the glide editor.

1 Like

Yeah, I tend to fat finger my words. I fixed my comments.

I think the problem is that you don’t have any rows. Glide can’t update a row that doesn’t exist. I would add another column heading (can be anything) and put something in row 2 of the sheet for that column. Your detail screen is currently not linked to row and doing this will give it a row to update.

Thanks, I fixed the issue.
I needed to create a new tab (using the Glide editor), properly set the type of columns (“time” and “number”), put on a number on the first row (1 works ok) and then start using the stopwatch.
At that point, the count will continue also if I browse on other tabs.
I created 2 stopwatches now (2 sets of columns), and they both work as they should (independently).
I think the key fix was to create a new tab using the Glide editor, but I might be wrong…

1 Like

The key is having a row to update. Creating a new tab shouldn’t have made the difference, but once you added data manually to create the first row, then glide had a row to update and write values to.