Read the statement by Michael Teeuw here.
MMM-MonthlyCalendar, config and .css
-
@Fuergrissa never edit main.css it will stop upgrades. never edit any file we ship
all your config for css goes in css/custom.css
if it doesn’t exist create it
-
@Fuergrissa there needs to be spaces between the classes unless u mean they are in the same element
-
@Fuergrissa use the dev window link I posted to be able to see and fiddle w css live without file edit , try , no, edit, try, no loop
-
Thanks I did all of the things you suggest. The developer pane is really handy, but when I drill all the way down to individual calendar events there is no difference in class for events coming from different calendars (which do have the titleClass assigned). Looking in MMM-MonthlyCalendar.js there is a section at the end that looks like it is intended to inherit the color information from the event, but this doesn’t actually happen?
if (e.color) { var c = e.color; if (e.fullDayEvent) { div.style.backgroundColor = c; if (getLuminance(div.style.backgroundColor) >= self.config.luminanceThreshold) { div.style.color = "black"; } } else { div.style.color = c; } }
-
@Fuergrissa don’t know this module’s workings
-
@Fuergrissa so it looks like this module gets it’s events from the base calendar
and if the base is not shownanyhow, use multiple { url: …}
blocks in the based calendar add a name: attribute to eachthat will carry forward on the event. I don’t know if this cal will use it
but then u could set styles for events by cal name