MMM-CalendarExt2

[feverlabs]

@feverlabs I think it would be this in custom css:

.CX2 .agenda .event {
  max-width:var(--column-max-width);
}

[A Former User]

@feverlabs

Final part: how can I set the width on this?
Also, should I use a custom class for it?

You can globally control the basic size metric with this; (Hmmm. I think you’d better first read the GitHub wiki about this topic)
https://github.com/eouia/MMM-CalendarExt2/wiki/4.-Styling

.CX2 { /* default values which are used frequently or dependently */
  --row-min-width: 100px;
  --row-max-width: 1000px;
  --column-min-width: 300px;
  --column-max-width: 400px;
  --font-size: 16px;
}

For the specific view, you can set className to a specific view, then can control it in css.

then, in your css/custom.css

Will show like this; Only specific view has different width;

But CSS is not so simple how it looks like, so when you modify something, you might need much experience and knowledge.

[feverlabs]

@Sean Yes, thank you. I made the following change in custom css:

.CX2 .agenda .event {
    max-width:290px;
}

This mad ether changes I was looking for. I’ll modify and try your solution as well as implement a class for it.

Is there a bottom padding that is specified? I don’t see much for padding in there, but I can experiment.

Thank you for your help.

[A Former User]

@feverlabs
exactly, what kind of bottom? Image will be a help to understand.

[feverlabs]

@Sean

I am just looking to reduce that space on the bottom. Not entirely eliminate it, but reduce it.

You’ll also notice that the start time is in 24h format, the end time is in 12h?

[A Former User]

@feverlabs

1. Some footer is reserved for displaying counter of hidden events. (e.g: +1)

The red area is slotFooter, so you can control it like this;

.CX2 .mySpecificView .slot .slotFooter {
  display:none;
}

2. For the time format;
   Read this first;
   https://github.com/eouia/MMM-CalendarExt2/wiki/Event-Time

With your previous config, you’ve set timeFormat: h:mm A, but there be more. :D
Upcoming view is somewhat different with other views(e.g: daily view), so the events need date and time together.

Usual format in upcoming view is something like this;

• If the event starts on a specific day and ends on the same day, it would be good to show like this;
  start date/time - end time
• If the event starts on a specific day and ends on the other day, it would be;
  start date/time - end date/time
• If the event is a fullday event and starts/ends in a day;
  start date
• If the event is a fullday event and ends in another day;
  start date - end date
  And those could be combined with relative format, humanized calendar format, … :) Looks so complex!

Anyway, so, you need to set dateFormat and dateTimeFormat also with timeFormat

Set like this;

dateTimeFormat: {
  sameDay: "[Today] h:mm A",
  nextDay: "[Tomorrow] h:mm A",
  nextWeek: "dddd h:mm A",
  lastDay: "[Yesterday] h:mm A",
  lastWeek: "[Last] ddd h:mm A",
  sameElse: "M/D h:mm A"
},

Or simply like this;

dateTimeFormat:"M/D h:mm A",

It will show like this;

Or

[feverlabs]

@Sean Beautiful! Thank you very much!

[jani.karna]

I’m trying to use local .ics file for two of my calendars. They are holiday calendars that stay the same throughout the year so they don’t need to be fetched from the web. I just can’t get them to work.
I get the same error message on both of them:

[CALEXT2] calendar: Suomen juhlapyhät >> write EPROTO 1936543760:error:1408F10B:SSL routines:ssl3_get_record:wrong version number:../../vendor/node/deps/openssl/openssl/ssl/record/ssl3:record.c:252:

My url looks like this:

url: "https://192.168.1.187:8080/Pyhat.ics",

I tried using

localhost:8080

but it tried to force 127.0.0.1 which don’t work.

[A Former User]

@jani-karna
Well, it’s not the issue of my module, anyway…
It seems, your RPI is not available to handle SSL of itself.
Can you open “https://192.168.1.187:8080/Pyhat.ics” or “https://localhost:8080/Pyhat.ics” on the browser of your RPI when MM is running?
Try “http” instead of “https”

[jani.karna]

Have to see if the problem comes back after RPI reinstall. It seems my SD-card just came to the end of its life.