MMM-CalendarExt3 not showing events on calendar, but does on list after 2.30 update

[sdetweil]

@tke499 calendar is broadcasting, so that’s not it

[MMRIZE]

@tke499

Generally,

This message is just an warning can be ignored.
However, in practice, stopping at that point usually corresponds to the following cases:

1. (Most common case): The CX3 module has not been properly installed. In most situations, this happens because the CX3_Shared library is not correctly installed. To resolve this, navigate to the CX3 directory, run git pull, and then execute npm install. This resolves most issues. If it doesn’t, simply delete the entire CX3 directory and reinstall it. It only takes about 15 seconds.

2. In very rare cases, other modules may cause errors during DOM creation, which can have an impact. However, this is highly uncommon, so the cause is typically case 1.

[tke499]

@MMRIZE I have re-installed CX3 3 times now. Still having the same issue

[tke499]

@MMRIZE I only have 2 other modules installed, one for nest and the other for traffic.

[MMRIZE]

@tke499
Send me your ics file or url. (eouia0819@gmail.com)

[sdetweil]

@tke499 what is the settings in the default calendar,
xxx out your url

set :maximumEvents:100,

[tke499]

@sdetweil I set it to 100. The events now show up, but low the list on the side goes to the bottom of the screen. Not the desired effect.

[sdetweil]

@tke499 use limitdays

there are 50 knobs to adjust

[sdetweil]

@tke499 you can try maximumEvents:12 or 15

there is also a way with css. i will test and document in a little while

this should hide more than 10 events in the default calendar
in custom.css

.calendar table tr:nth-child(n+10) {
  display: none;
}

[sdetweil]

@tke499 I have confirmed the css approach works…
in ~/MagicMirror/css/.custom.css

.calendar table tr:nth-child(n+10) {  /* 10 is the number of rows you want showing */  
          display: none;
}

I have maximumEvents:200
and only 10 lines show with the css posted
without it, it goes to the bottom of the screen

[Niggich]

@sdetweil thx this is working for me, but now the events doesn’t fade out… any solution?

[tke499]

@sdetweil this works, just no fade. Thanks

[sdetweil]

@tke499 yeh, fade is calculated based on the size of the list (200 in my case)
and the fade starts at 100, oops… cut off at 10…

fadepoint can get you a different start spot, BUT, its also changes the amount of fade (start at .02 (4 =line 4) BUT there are 196 steps in the fade, so I don’t see much…

looking thru the code, I don’t see any difference in the event broadcast

[sdetweil]

@tke499 i’ll give you a hack til next release

in ~/MagicMirror/modules/default/calendar.js
add this line

		fadePoint: 0.25, // Start on 1/4th of the list.  line 25
		fadeSteps:0,  // ------- this one

and

			startFade = events.length * this.config.fadePoint;   // line 255 after above added
			fadeSteps = events.length - startFade;
			if(this.config.fadeSteps)                  /* these two */
				fadeSteps=this.config.fadeSteps 

then in your config.js calendar

          fade:true,
          fadePoint:0.02,   //  use this to get into the top 10 (my 200 list gets to number 4)
          fadeSteps:6,         // use this to decide how many steps from full to gone

[tke499]

@sdetweil Thanks. Do we know why this is happening with this release? Assuming it had to do with the calendar update.

[sdetweil]

@tke499 I do not yet… I checked the code that sends the list to other modules and I don’t SEE anything … ps, I personally did all the calendar updates

both versions clip the list to the config.maxEvents: value. (10 default in both)

[sdetweil]

@tke499 looking at the code again, there WAS a bug in prior releases, where
you COULD specify to limit the number of entries produced BY calendar

    { 
       url: "some cal url",
       maximumEntries:xxx   // default whatever the base config has for this property
    }

so, I added code to fix that bug

SO, if one does NOT specify maximumEntries in the cal url section,
it will clip to the default value,
which it did NOT DO before…

the prior bug was maxEvents said 100 (including old)
1st cal contributed 20
2nd cal contributed 100
3rd cal contributed 5

1st 100 (maxEvents) is returned… so none of cal 3 got processed…

the code and limits were present in prior release, just not the clipping

[tke499]

@sdetweil so I am assuming that I should just keep the coding you provided earlier correct?

[sdetweil]

@tke499
if it works for you

yes, next release is April 1

[tke499]

@sdetweil appreciate being patient with me. Thanks again. I made this MM for my wife for Christmas and it has fought me every single step.