Read the statement by Michael Teeuw here.
Absolute date
-
Anyone? Does anyone have absolute date working as I describe? Can someone post the relevant portion of their config file so I can see what you’ve done?
Thanks.
-
Any word on this? I’m using a 7" raspberry pi display and that ‘Tomorrow at 10:00 AM’ eats up a lot of real estate.
Here’s my config:
{ module: 'calendar', header: 'My Calendar', position: 'top_right', config: { calendars: [ { symbol: 'calendar-check-o ', url: '[redacted]' } ], maximumEntries: 10, maxTitleLength: 12, titleReplace: {'Appointment':'Appt'}, displaySymbol: false, timeFormat: 'relative' } },
-
… and by
{
timeFormat: ‘relative’
}I mean
{
timeFormat: ‘absolute’
}
ugh. -
This post is deleted! -
Turns out my problem came down mostly to not really understanding the difference between ‘absolute’ and ‘relative’… I fixed my problem by modifying the code in calendar.js slightly.
// Otherwise just say 'Today/Tomorrow at such-n-such time' timeWrapper.innerHTML = moment(event.startDate, "x").calendar(null, { sameDay: 'H:mm', nextDay: '[Tomorrow] H:mm', nextWeek: 'dddd', lastDay: '[Yesterday]', lastWeek: '[Last] dddd', sameElse: 'DD/MM/YYYY' });
I sort of hijacked this thread. Sorry (but I think my solution might help out the OP ).
-
@mjtice What lines did you implement that code on?
-
@mjtice Thanks man, that solved my problem too. Except I added NextWeek: ‘dddd DD/MM/YYYY’
Cheers!
-
@daikaiju it’s on line 245 in the current release. Keep in mind that if you upgrade you’ll lose those changes (as I did exactly 2 days after I made that post…).