Forum Discussion
_anomDiebolt_
8 years agoQrew Elite
I have a novel solution and halfway through creating a demo. The demo will work from a report or view record page and timers will continue to count if started even when the page holding the counters is not displayed! And you will be able to have multiple counters active at the same time.
- JessicaHaskins8 years agoQrew CadetThanks Dan. I've seen some of your demos and their very useful. When do you think you'll finish the demo?
- _anomDiebolt_8 years agoQrew EliteProbably by the end of the week - I tend to work on these demos at odd times and refine it. The code is actually the easiest part. Here is a screenshot of what I am playing with now:
Normally you would not see the fields [Last Start Time] and [Last End Time] as these fields store an internal state of milliseconds values and allows the timer to "calculate the passage of time" even if the page is not currently being displayed. - JessicaHaskins8 years agoQrew CadetHey Dan looks great. I've found different javascripts for stopwatches, but this one seems to have the most features https://codepen.io/_Billy_Brown/pen/dbJeh . I found one of the challenges is creatinga stopwatch that can have "laps" and can start and stop and start again at any moment.
- _anomDiebolt_8 years agoQrew Elite>creating a stopwatch that can have "laps" and can start and stop and start again at any moment.
I probably won't go quite so fancy on the display as that demo does because my intention is to have the ability to have multiple timers displayed in a report as well as a single timer on a view page.
This isn't going to be too complicated in the end. It is the practical workflow and navigation that takes a little time to nail.
By storing the last start and last stop times in fields you can resume the display of the counter and it will just display the current elapsed time and continue counting (if it had been started) despite the fact that the page may have been closed in the intervening time.