jared, can you use this link instead - for both webapp and project version? i had just fixed the calendar so it displays the last week properly - the earlier version was “floating” the last few days of the last week into the center so the days are not lined up.
the incorrect_last_week error was reported by @paulovaz72 which i fixed in the above version. the other, more important error is that he couldn’t get it to display properly on his device. i also get the same behavior on my device - an android galaxy. i’ve tried changing the wait time in the clone blocks to longer values but they never fixed the display on live test on the device.
@jared , I tested in two devices: Galaxy S9 and Asus MemoPad (both androids, but different versions) and the behavior was the same wrong display of calendar.
@manyone, did you consider the possibility to store the calendar in a external table to improve the delay time (maybe you can generate an online google spreadsheet, or airtable, or Firebase Database (my personal choice), and just load & display later?
I think if you save data for the next 100 years, will more than sufficient to use in our projects, in this case you just load the data and display in the nice design you create, instead do calculations each time you change the month or year. I mean, you do the calculation but just one time. (Just put a “SAVE CALENDAR” button in your project, and store the data). After you can create another routine just to load & display using internal lists…
it worked! you’re a genius muneer!
it doesn’t speak well of thunkable though - i learned early on that screen_starts is executed at the very beginning, while screen_opens is executed after that whenever we navigate to the screen. now i have to unlearn that but only in certain cases - there is no consistency.
thanks for the suggestion!
Thunk-ing, i found myself in condition to execute some code only once after the app starts, on a particular screen, and some other action to be done as many times as a user switch between screens.
So if a screen is in that condition (have code that needs to be executed only once, and other code that needs to be executed as many times as that screen is accessed , i use both when screen starts - where i put code that needs to be executed only once, as soon as user access that screen, and when screen opens where i put code that needs to be executed as many times as user accesses that screen.
I found that both are launched same time, so error may occurs.
So i use a validation variable, to put some order in execution:
Let`s say validate=FALSE at the very beginning of the entire application.
Where that particular screen is accessed, on when screen starts i put validate=TRUE only after the entire code from that block is executed.
And i put at the very beginning of when screen opens something like: While validate=FALSE
This way i know for sure when, and what actions are done.