Read the statement by Michael Teeuw here.
module calendar showing full day events one day to long
-
Here’s the relevant code:
} else { /* Check to see if the user displays absolute or relative dates with their events * Also check to see if an event is happening within an 'urgency' time frameElement * For example, if the user set an .urgency of 7 days, those events that fall within that * time frame will be displayed with 'in xxx' time format or moment.fromNow() * * Note: this needs to be put in its own function, as the whole thing repeats again verbatim */ if (this.config.timeFormat === "absolute") { if ((this.config.urgency > 1) && (event.startDate - now < (this.config.urgency * oneDay))) { // This event falls within the config.urgency period that the user has set timeWrapper.innerHTML = this.capFirst(moment(event.startDate, "x").fromNow()); } else { timeWrapper.innerHTML = this.capFirst(moment(event.startDate, "x").format(this.config.fullDayEventDateFormat)); } } else { timeWrapper.innerHTML = this.capFirst(moment(event.startDate, "x").fromNow()); } } if(this.config.showEnd){ timeWrapper.innerHTML += "-" ; timeWrapper.innerHTML += this.capFirst(moment(event.endDate , "x").format(this.config.fullDayEventDateFormat)); }
You can see in the end, that an end to the date is created if showEnd is true. So as far as I can see it, it all comes down to what
event.endDate
generates.
-
@AnduriI I agree that this is a kludge to get the calendar working. I had tried out MMM-MyCalendar which didn’t appear to have this issue (all day events like holidays and birthdays displayed the correct date). It’s a great module BUT, I decided not to use it because I can’t change the colors of the calendars and I could not use a custom icon for different calendars. For example, on my calendar, I have three calendars (US Holidays - white, Birthday calendar - purple with cake icon, and appointments - green). It helps to highlight the different events showing up in the list. I didn’t reach out to the module developer to request this yet. Give it a look, it might be what you are looking for.
Unfortunately Magic Mirror has issues which need a kludge hack to resolve (I need to cron a restart of the Magic Mirror application every 5 hours otherwise it goes black (not a screen saver or power saving thing). This has been present for since at least the previous build. Still, I love the Magic Mirror platform and the community is amazing! I am grateful every time I come here and see people helping each other out…
-
Well this MAY be it. calendarfetcher.js
if (typeof event.end !== "undefined") { endDate = eventDate(event, "end"); } else if(typeof event.duration !== "undefined") { dur=moment.duration(event.duration); endDate = startDate.clone().add(dur);
if duration is EXACTLY 24h for a full day event, we would land up at the next day with this .add-function
You COULD try the following:Go into calendarfetcher.js and change in line 96
endDate = startDate.clone().add(dur);
to something like
endDate = startDate.clone().add(dur-10000);
I can’t do it, I’m at work and REALLY need to go back to it now :-)
EDIT: …well, I needed to try. That’s not the solution. But it should be somewhere in that file :-)
-
@striiker
I need to disagree here.
MagicMirror does not need kludge hacks!
It needs development!I am 100% sure your 5-hours-restart-hack can be solved without the workaround.
-
@lavolp3 said in module calendar showing full day events one day to long:
@striiker
I need to disagree here.
MagicMirror does not need kludge hacks!
It needs development!I am 100% sure your 5-hours-restart-hack can be solved without the workaround.
I absolutely agree that it needs development. Unfortunately that’s outside of my realm of expertise (and others who have these types of issues). In the absence of someone actively developing a solution to a defect which should be widely known (I have had this crash happen on multiple fresh, new base installs) we are left with using what we can to work around the issues.
The only responses I had to my query around the crashing was from others who had this happen and one person who suggested the cron restart. There was another post by someone else with the same issue as well.
Beggars can’t be choosers and I’m not complaining about this. I am hopeful that these issues will get addressed some day but in the mean time, here we are.
-
@striiker I guess this forum got too crowded to have everything solved properly. I feel you.
-
@andurii OK I found a way to properly deal with one-day events. Will send a PR to the develop branch.
If you want to include it already:Exchange the if-clause starting at line 292 with this.
if(this.config.showEnd){ if(event.endDate - event.startDate > oneDay) { timeWrapper.innerHTML += "-" ; timeWrapper.innerHTML += this.capFirst(moment(event.endDate , "x").format(this.config.fullDayEventDateFormat)); } }
BEWARE OF CHANGING THE MODULE FILES THEMSELVES.
Only do it if you know what you’re doing.
(You’re not breaking anything irreversibly however)This only shows the end date for a more-than-one-day-full-day-event.
However, still a workaround. Still searching into the problem itself -
@lavolp3 thank’s a lot man, you are much faster and way more skilled than me :-)
Just a little discussion: your code only adds the if clause to check if it’s longer than a day to prevent single full day events to be displayed as two day. But what about a multi day event beeing displayed one day to long (which is also happening right now)? -
@andurii
Yeah that’s what is still missing and why i said this is still only some type of workaround.
However, the if-clause will be needed in the end because for a full one-day event you do not want to be shown an endDate. As soon as the full-day-event is longer than one day, you may want it again.
E.g.
Mario’s birthday Nov 16th
(and NOT Nov 16th - Nov 16th)
Luigi’s Holiday Nov 16th - Nov 23rdWhat you’re pointing at is the root cause and it lies somewhere else. I’m sure it can be solved. Give me one weekend ;-)
-
So I guess I have found a “solution”.
This is in fact a systemic problem.A full day event is given by the ical source as starting at 0:00 on a day and ending at 0:00, but one day ahead. The duration is exactly a multiple of 24h.
There is a one-liner as workaround, but I’d invite everyone to find a more gentle solution.
The workaround: subtract one second from the endDate time:
Include this line into calendar.js just at the beginning of the if clause in line 262:event.endDate -= 1000;
So it looks like this:
if (event.fullDayEvent) { event.endDate -= 1000; if (event.today) {
This should solve the issue. It worked for me at least.