Read the statement by Michael Teeuw here.
MMM-CalendarExt3Agenda on a higher screen resolution?
-
@sdetweil
Thanks for your explanation always.
I’ll add small message in the screen on waiting - “Waiting calendar fetch…” or something informative in the next update… -
-
I have set refreshinterval at 180000 - 3 Minutes.
this may triggers appearance of MMM-CalendarExt3Agenda …I’m not able to identify the startup of MMM-CalendarExt3Agenda in the log.
If I consider the difference between Mirror-startup and first calender fetching as the “right” fetching time
[2025-01-24 10:44:49.288] [LOG] Starting MagicMirror: v2.30.0 [2025-01-24 10:45:05.760] [34m[INFO] [39m [34mCalendar-Fetcher: Broadcasting 22 events from https://www.feiertage-deutschland.de/ [2025-01-24 10:45:06.206] [34m[INFO] [39m [34mCalendar-Fetcher: Broadcasting 21 events from https://calendar.google.com/calendar
it should be around 16,9 seconds - is this the right assumption?.
At least with
waitFetch: 17000, // start: 0:45:06.206 - first calender fetch: 10:44:49.288 = 16.918 ms
MMM-CalendarExt3Agenda appears “faster” than before …
-
@rkorell you want more than last calendar for wait fetch
-
@sdetweil , sorry, I didn’t get you…
what do you mean by this?Ralf
-
@rkorell you want the time til after the LAST calendar broadcast not the first
10:45:06.206
He wants to wait til ALL the data is present
So waitFetch: 19*1000
-
@sdetweil
O.K. , sorry my fault…Wrong expression from my side “first fetch” means first complete fetch (so ALL data fetched).
In addition I accidentally switched the begin and end…
So correct view iswaitFetch: 17000, // MM starts: 10:44:49.288 minus complete calender fetch at: 10:45:06.206 = 16.918 ms
Sorry for my mistake.
And thanks for your explanation!
Warmest regards,
Ralf.
-
@rkorell and did that work?
-
@sdetweil , sorry - being offline for a while…
Yes, seems to work.
As you was afraid of, it takes LOOOONG until calender shows but earlier as without your suggested modification.
Thanks again!Warmest regards,
Ralf -
-
@rkorell awesome