MMM-CalendarExt3

almightyyoshi

@MMRIZE That’s perfect. Thanks. I just wasn’t sure if those attributes were available and I honestly just didn’t feel like experimenting at that moment. Last question (think): Is there a way to hide the default calendar module and still populate CX3. I found a way to hide the module (by editing the calendar module’s base config) on startup, but then CX3 doesn’t have any events. Here’s what I used (courtesy of @sdetweil from a thread a couple of years ago):

hidden: false, 


suspend: function(){
    this.hidden=true
},

restore: function(){
     this.hidden=false
},

notificationReceived: function(notification, payload, source){
   // this comes before the first call to getDom()
   if(notification === "ALL_MODULES_STARTED")
      this.hidden=true;
}.

getDom: function (){
var wrapper=document.createElement('div')
if(this.hidden==false){ 
     //create normal content
}
return wrapper;
},

sdetweil

@almightyyoshi I think you will have to use css to hide, vs code

MMRIZE

@almightyyoshi
You can hide it with CSS, or just drop out “position”.

almightyyoshi

@MMRIZE Dropping position worked. I thought I’d get an error or blank screen for that. Thanks again!

luisestrada

@almightyyoshi Every time i think this is fixed then it comes back again…

I have 3 calendars so I renamed calendar1 and calendar2, as I don’t want these calendars to conflict with CX3.
Then I have my calendar module and dropped the position as I don’t want to show it.
My CX3 loads empty and after a while the information appears, then it goes and then it comes back. I think I have not set up properly the refresh. I’ve tried many combinations but nothing works

{
module: “MMM-CalendarExt3”,
position: “bottom_bar”,
title: “Calendario”,
waitFetch: 10000, // (ms) waiting the fetching of last calendar to prevent flickering view by too frequent fetching.
refreshInterval: 1000 * 60 * 1, // (ms) refresh view by force if you need it.
glanceTime: 1000 * 60 * 1, // (ms) Return to original view when you move to other moment by notification.
//animationSpeed: 2000, // (ms) Refreshing the view smoothly.
rotateInterval: 0,
eventTimeOptions: {
timeStyle: “short”
},
fetchInterval: 1000,
config: {
mode: “week”,
instanceId: “WeeklyCalendar”,
locale: ‘es-CO’,
maxEventLines: 3,
firstDayOfWeek: 0,
weekIndex: 0,
weeksInView: 4,
broadcastPastEvents: true, // <= IMPORTANT to see past events
calendarSet: [‘Cal1’, ‘Cal2’, ‘Cal3’, 'Cal4, ‘Cal5’],
}
},

And Go Jays Go!! :beaming_face_with_smiling_eyes:

Screen Shot 2022-06-06 at 3.14.02 PM.png

sdetweil

@luisestrada do you have 3 instances of
module:‘calendar’
?

luisestrada

@sdetweil said in MMM-CalendarExt3:

@luisestrada do you have 3 instances of
module:‘calendar’
?

Yes, I have 3 modules, the holidays (shows 3), the birthday calendar (shows 2) and the normal calendar (shows 8).

sdetweil

@luisestrada each sends out its own list of entries. maybe calext3 is replacing a with b with c

luisestrada

@sdetweil said in MMM-CalendarExt3:

@luisestrada each sends out its own list of entries. maybe calext3 is replacing a with b with c

That’s exactly what i thought, so thats why I created 3 different modules by copying the entire module in a separate folder and renaming it, similar to this: https://forum.magicmirror.builders/topic/14724/run-two-instances-of-the-same-module-sometimes-tutorial

but still, if I have 3 modules called, calendar, calendar1 and calendar2, it does it

MMRIZE

@luisestrada
Well, I was worried about just that case when I developed this module - multiple calendar instances. I thought Nobody would use the calendar module like that. So I haven’t considered supporting that case. But I was wrong.

The current behaviour of this module is replacing whole events when the notification arrives, not combining each. So you cannot get proper whole events from multi-emitter of notifications.

I’ll modify the module in a few days to stack each event not replace it. Wait for a little.