Non capisco perchè non funziona più

[Nicola_Imperati]

Hello everyone,
I can't figure out why the expired medicine check doesn't work anymore. What am I doing wrong?

Regards
Nicola

[ABG]

You call this procedure at the start of Screen1:

The procedure iterates over the global variable Medicine_Dates:

But you did not yet load the global list yet (from TinyDB?)

Mistakes like this are easier to spot if you include those global variables as parameters in your procedure calls.

[Nicola_Imperati]

I followed your advice

but the strange thing is that even though "prova" corresponds to 7/19/2026 and prova2 to 6/19/2026, it tells me that only prova2 has expired.

[ABG]

I don't see why the 7/19/2026 date wasn't caught.

I have only two guesses:

• Your test device has the current date set wrong, or
• The tool tip on the MakeInstant block does not mention a possible localized reinterpretation of MM/dd/yyyy as dd/MM/yyyy, changing the comparisons.

I suggest applying Companion Do Its to hard coded samples of those blocks, to see the intermediate results on your device.

[davidefa]

You can also do the other way round ( hey, there is always someone telling to do in the opposite way… this time it’s me ; - ).

I mean, I prefer saving a timestamp (clock.systemtime ), it is a simple number, easier to compare ( without any conversion ).

You only need to convert in a readable form when you need to display it ( use clock.makeinstantfrom millis and then format the instant as you like )

[Nicola_Imperati]

[Nicola_Imperati]

But if label4 sees the two dates, why does it only show me one?

[davidefa]

You have to move the block highlighted below, outside the for cycle

[Nicola_Imperati]

What do you mean outside the for loop?

[davidefa]

before the for each loop ( otherwise each time the then is executed the label4 text is overwritten ):