Clock remains active when changing screen

Discuss
#8

Thank you I will see to adapt it to my project.

1 Like
#9

@Still-learning
Hello,

I just tested.

The countdown starts well at 5 min and decreases.
On the other hand, when I go to another screen and return to the countdown screen, the countdown no longer decreases but resets to zero and increases.

Example :
I leave screen 1 with a timer at 0d 0h 4m 34s
When I come back it goes to 0d 0h 0m 0s and makes an increasing countdown.

#10

See solution provided in

#11

Try this
countdown_5.aia (9.8 KB)

#12

firebase.apk (5.2 MB)

I have used the above procedure…

Just hit start button, go to screen 2, press back button to return… also close the app and reopen… and tell me whether it is continue from where it left or restarting from zero…

#13

@dora_paz @Still-learning

Thanks for your help.
I will look at your 2 proposals.

1 Like
#14

I mis read your topic, I think… actually you want where you left… But my design is just it will goes on decreasing… little arrangement will solve, just save the remaining time in tinydb and start from that point when screen initialise

#15

@dora_paz

In the spirit, yes it is that of going from one screen to another and when we return to the 1st screen the countdown continues.

But I misspoke when I said that when I returned to the 1st screen, the countdown resumed where I was. I actually meant it continues to count down while I’m on screen 2.

Example :
I leave the 1st screen at 4m 30s
I’m going to the 2nd screen for a while
I return to the 1st screen afterwards with the countdown updated to for example 3m 30s if I spent a minute on screen 2.

#16

Ok let me modify it. Also what will happen in both screens if time elapsed ?

#17

@Still-learning
that’s exactly what i want to do yes.

It also works well with the app closed and when switching screens.

what is your aia?

1 Like
#18

@dora_paz @Still-learning

Thank you @dora_paz , your solution is good but @Still-learning brought me the solution beyond my expectations with the stopwatch which continues even with the app closed.
It remains to be seen the aia he uses.

2 Likes
#19

@dora_paz

To answer your question, once the time is up, a button appears.

1 Like
#20

@Still-learning

I used airtable instead of TinyDB to store the time values.

I can try to adapt what you put there Clock remains active when changing screen - #7 by Still-learning

but I do not get the result of your APK.

#21

the point is, where and all i used get tinydb tag value, you must use your airtable value… and where and all i use save the tinydb value you must use save to airtable…

1 Like
#22

@Still-learning

finally I succeeded.

I resumed all my components and I had an error that directed to global_final and not global_initial

Which is why it was reset to zero instead of continuing the countdown.

It works perfectly as you had shown.

blocks (1)
blocks (1)1610×1031 120 KB

A big thank-you.

I still have to adapt to put on airtable.

Sujet résolu. :heart_eyes:

2 Likes
#23

@Still-learning
I have one last problem, I would like the counter to be in the format 0m 0s and not 0d 0h 0m 0s

i tried with this

blocks (4)
blocks (4)717×81 6.69 KB

it doesn’t change anything

#24

try split the vaue at spaces and use select list item list index 3 and 4 alone… simple

try like this (modified as per your requirement)

blocks(11)
blocks(11)1065×1597 92.7 KB

1 Like
Show screen every five or six hours
#25

@Still-learning

Hello,

Sorry for the late response.

It’s perfect.

I concluded that the Gobal_initial component was no longer useful.

Many thanks to you.

#26

Yes, actually i removed it but without saving it I sent it to you it seems…

1 Like
#27

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.