Bad Arguments on Clock Duration

[Matthew_Smith]

I'm getting Bad Argument error when checking for a duration using the clock app. I have used the clock app to build both of the arguments, so it seems I must be missing something. I've tried a number of different variations on creating the starting instant, but here's where I'm at now. Hopefully someone can see what I'm missing.

Here is the block where I create the FV1StartInstant value stored in TinyDB:

Here is the block where I check the duration. It is comparing the FV1StartInstant with Clock1.Now:

Here is the bad argument error I am getting. Any ideas?

[ABG]

Your TinyDB default value, 0, is not an Instant.
The Duration block only accepts Instants.

Try a different notfound value, like Now().

[Matthew_Smith]

So I definitely like the Now() option better, but unfortunately it doesn't help. I added it and still get the same error.

What my pictures don't show is that the duration is nested in an IF statement that only runs it the TinyDB returns a value, so it can't get to this block if there is no value, so it really can't hit the default value.

As you can see in the error dialogue it shows the arguments as two java.GregorianCalendar values.

[ABG]

Show us the big picture?

Please export your project and post it here.

[ABG]

Another possibility is to store time as Milliseconds from 1970, a big number.
There are clock blocks to convert back and forth, and it is math-friendly.

[Matthew_Smith]

@Matthew_Smith

What my pictures don't show is that the duration is nested in an IF statement that only runs it the TinyDB returns a value, so it can't get to this block if there is no value, so it really can't hit the default value.

TankTracker.aia (12.0 KB)

[TIMAI2]

You are not wrong, this should work....

but it errors out

[ABG]

So don't rely on TinyDB for Instant storage, only store milliseconds.

Also see FAQ Section: Screens
for proper screen switching techniques.
Reopening Screen1 will fill RAM eventually.
(Your blocks)

[TIMAI2]

Do it like this:

[Matthew_Smith]

Thanks, I changed my Open Screen1 functions to Close Screen functions, that seems to work ok and I think takes care of the RAM issue. I still need to add my Close Application.

[Matthew_Smith]

So I'm doing it this way and for some reason I'm getting 0 as the result every single time. I'm having a harder than normal time tracking that down though because I can't use the companion app or emulators when I'm at work and have to build the APK for testing. I'll try some more when I get home tonight.

[Anke]

@Matthew_Smith

So I'm doing it this way and for some reason I'm getting 0 as the result every single time.

Try this:

Time Format Extension - Millis to [HH:mm:ss] - [days + HH:mm:ss] - [HH:mm] - [mm:ss] etc

Here is an extension to format the time / duration (millis) in different ways: → [ HH:mm:ss ] → [ days + HH:mm:ss ] → [ HH:mm ] → [ mm:ss ] → etc. This is asked very often and always requires a lot of questions / answers and posts in the forum. (Last here: Creating a Chronometer - #17 by PizzaGuy07) Hence this extension (some of it can also be implemented with the on-board methods, but I want to simplify it:): Version 1 (May 20, 2020): TFormat.aix (5.5 KB) Version 2 (Oct 20, 2021): TForm…