Posts made by MMRIZE

MMRIZE

@jrd
There could be several possible reasons; but most cases might be these two.

MMRIZE

/* config section of default calendar in config/config.js */
broadcastPastEvents: true,
sliceMultiDayEvents: true,

/* config section of CX3 in config/config.js */
eventFilter: (ev) => {
	const day = new Date(+ev.startDate).getDay()
	return (ev.fullDayEvent === true && (day === 0 || day === 6)) ? false : true
},

BEFORE

AFTER

ISSUES

sliceMultiDayEvents would not emit the passed multi-day event. That’s not my fault.
looks ugly. Do you really need these splits? Generally, multi-day event means the period, not the occurrence.

Of course, you can slice events yourself for your purpose with eventPayload instead of sliceMultiDayEvents option.

MMRIZE

@redfishbluefish
Slice first, then skip when the each event belongs to the weekends(with eventFilter or eventTransformer)

MMRIZE

@redfishbluefish
Consider to try Intl.dateTimeForamt.
https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Intl/DateTimeFormat

MMRIZE

@nic0rz

I just realized that if the screen is turned off, taking a screenshot only shows the background and not the modules.

I think that is out of this module’s business.

MMRIZE

@redfishbluefish
By the way, handling cell header would be possible with manipulateDateCell, You can refer this for your understanding.
https://github.com/MMRIZE/MMM-CalendarExt3/discussions/178

MMRIZE

@redfishbluefish
First, please clearly explain the rules that determine how Day 1 to Day 5 are decided.

It seems that the fundamental principle is: “Day 1 to Day 5 follow sequentially without interruption, excluding holidays.” While this appears to be a simple and straightforward rule, there might be hidden conditions that complicate its application.

Could there be exceptions where the Day 1 to Day 5 sequence is disrupted, even on regular weekdays? For instance, unexpected events like a school activity might occur, causing the rule to be temporarily suspended. In such cases, it’s unclear whether the sequence is skipped entirely or deferred to the next day. The handling of these exceptions could vary, and since such cases might not be planned in advance when running the schedule system (MM), they may need to be adjusted manually as they arise. While not impossible, this would be inefficient and impractical.
To apply this rule effectively, the start and end dates of the sequence must be clearly defined. In countries like Korea, where the academic year is typically divided into two semesters with fixed start and end dates and few extended breaks during the semester, applying this rule is relatively straightforward. However, in Western schools that follow a trimester system or have long breaks during the term (e.g., Easter break), creating a universally applicable calculation method becomes quite challenging. This is because periods during which the rule is inactive must be explicitly defined.

Perhaps the most reliable approach would be to designate events for each applicable date within a calendar manually. By manually specifying the dates to which the rule applies, it’s possible to adapt to changes in schedules or rules. However, this method could be quite tedious.

Alternatively, if there is already a schedule table in a digital format with these dates predefined, you could import it as a source and apply the rules automatically. (This would likely require creating a dedicated module to handle this task.)

MMRIZE

@Andreas1956
You are clicking the day cell, not event.

MMRIZE

@Andreas1956
OK. Look inside deeper.

Execute MM as dev mode.

If you are using pm2, stop it first.
In your MM directory, run this script.

npm run start:dev

Or alternatively, After MM’s normal execution, Ctrl + Shift + i (Or Alt+F12, it could be different by your system environment), Anyway, open the dev-console on the browser/client with hotkeys.
It will open this kind of dev-console as a side panel.

At the panel, you can see Elements or Console tab. Go to Elements Tab.

There would also be cursor icon (left side of the Elements Tab mark); select it and click to any event element

Now, the side Elements tab will focus on the HTML code for the element you clicked.
navigate into the title element

Check whether proper text exists there.

And See the Styles tab.(Somewhere in the side panel. Usually below the Elements window)

You can see there are --calendarColor and oppositeColor attributes there. And there is no other overridden colors.

Or you can check this in Computed tab.

There are some calculated results for the style.

Could you find any suspicious things on watching your case?

MMRIZE

@Andreas1956
I checked your config and css but nothing seems wrong.
From which version were you updated to new one? (I think you cannot remember, but how long has it been since the previous update?)
Anyway, I think you may have missed something in the last update.

Go to the CX3 module directory, then;

git pull
npm update

I doubt you may miss npm update part in your last update process.

If it still does not work, do this in your CX3 module directory

git submodule update --init --recursive

Still not working; remove the CX3 directory and then reinstall again.
Still not working; let’s discuss deeper.