Read the statement by Michael Teeuw here.
MMM-CalendarExt2
-
@JRB1988 I can confirm that 7 calendars works fine. I wonder if you have a syntax issue on the last one in your list. You should be able to look at the log window and see each of the calendars being read and the number of entries that are selected.
-
@JRB1988
Did you happen to figure out why MMM-Todoist was causing the green underline on calendars ? I’m having the same problem and can’t seem to find a solution.
Thank you in advance -
@mscrawford5
add this into yourcss/custom.css
.today { text-decoration: inherit; } .tomorrow { text-decoration: inherit; } .MMM-Todoist .today { text-decoration: underline #03a05c; } .MMM-Todoist .tomorrow { text-decoration: underline #166cec; }
Not tested, but you can catch the idea.
-
@Thekk Thanks for this, just implemented it and it work like a charm. Took me a while to find node_helper.js until I did a find on it and found it in the MMM-CalendarExt2 folder (as well as everywhere else). I’m still a noob with the RPI so not all things are obvious.
It took me no time at all to find the place to make the change and then I added the filter to the upcoming view while leaving the monthly view alone; exactly what I wanted! Thanks again.
Now just need to make sure that this gets incorporated into the next module.
-
@Sean
That worked.Thank you for your help! -
@Thekk
Thanks. I haven’t thought about that method. Now I updated that part in the module. -
Experiencing a new problem. I have MMM-CalendarExt2 configured with two calendars and two views. I have one view that shows upcoming events, top_left, looking out in the next 90 days (we don’t have a lot of events at the moment) and a second view that is monthly fullscreen. Both calendars are listed in both views and have css entries to color code which calendar the event comes from.
When MM first starts up, only the first calendar appears in each view; however, when MMM-CalendarExt2 refreshes, both calendar events appear and are properly color coded. This doesn’t change unless I restart MM and then the process repeats.
Both calendars are defined exactly the same way.
Since the events in the second calendar eventually appear, I’ve ruled out potential errors in the config file.
-
@EdO
try to set “firstDrawingDelay” to 1000 or 2000 something, or shorten ‘updateInterval’ or ‘rotateInterval’.
The reason would be; all your events are not loaded or parsed yet on its first drawing cycle, so only some of them will be displayed at that time. Remains will be parsed and displayed on next cycle when prepared. -
@Sean
Thanks for getting back to me so fast.Ok firstDrawingDelay and rotateInterval are both at default values while updateInterval is set to 300000.
I’ll first try setting rotateInterval to 1000 to match firstDrawingDelay to see if that fixes the problem. If that doesn’t work, I’ll experiment until I find something that does. -
@EdO
if you are using only one scene or you don’t mind change of event applied instantly,
you don’t need to keep interval so shortly. I think 1 -2 sec for firstDrawDelay would be enough.