@Kelemvor
1.
That’s an issue with the Weather module. Sometimes, the weather module sends incorrect units in the broadcasting notification, which is different from the settings used for screen display. I don’t know why it happens, but you may need to ask the MM developers. Anyway, that example you read is created for such cases in my favour. The responsibility for this issue does not lie with this module.
.CX3A .event .description,
.CX3A .event .location {
display: none;
}
Put into your Custom.css, .
Why is it not served as a config value? Sorry, it’s my design.
Presentation and logic should be separated. Maybe showDescription would be useful, but how about these? showEventTime, showDayWeatherIcon, showDayWeatherTempMax, showDayWeatherTempMin, … Maybe those also are useful. But I cannot prepare all the configurable values for all the things. This module still has too many options.
But just for the presentation, only CSS overriding could solve many things without much code and for various cases.
3 . The default calendar modules spit out events when each calendar is fetched. The problem is, there is no way to know all the calendars are fetched. So, if your calendars are too many and big, some calendars may need time to finish fetching; that calendar will not be rendered at the first cycle of this module’s refreshing. From next cycle(I hope), it will be shown. So, wait to be refreshed. (default refreshInterval is 30 minutes)
Alternatively, you can use waitFetch to delay the rendering of the first cycle. By providing a sufficient value, you can ensure that the parsing of calendars is completed within that time. Since the duration of parsing for each calendar is unknown, it may require a considerable amount of time. Perhaps around 30 seconds should be sufficient, although it depends on the specific calendars being parsed.
Default waitFetch is set as 5000 ms,
