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

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