Sorry, the Previous version was not tested, I have shown the code only with my brain, not with a real device.
Here is the tested code.
eventTransformer: (ev) => {
if (ev.title.search('Uitje') > -1) ev.color = 'gold'
if (ev.title.search('Verjaardag') > -1) ev.symbol = ['birthday-cake']
return ev
},
@Sam-0 sorry, it would not be ‘icon’, it would be ’ symbol’
@Sam-0
First,
You can assign colour or class per each calendar. So check if your events are separated by different calendars. Check it first.
In case your events are in one calendar and want to distinguish each by title of event, you can do this;
eventTransformer: (ev) => {
if (ev.title.search('Uitje') > -1) ev.color = 'blue'
if (ev.title.search('verjaardag' > -1) ev.icon = 'birthday-cake'
/* and so on ... */
return ev
},
@sdetweil
Unfortunately override display:flex into .container is not so easy. Because, MM’s hide/show mechanism depends on container’s display value (none/block) and it is hard-coded in the HTML tag. (I think it would be a bad legacy approach to be fixed in some day.)
Anyway, without that overriding, It is possible anyhow limitedly.
.region.top.center .container .module {
float: left;
max-width: 32%;
}
and I put 3 modules (2 clocks, 1 calendar) in top_center region.
@rdiharce
Maybe your armbian has no desktop environment (e.g. Gnome). Is it installed?
@sdetweil
Thanks. I’ll do it right now.
I am so sorry that all the ppl have that issue due to wrong instructions.
@Kaisies-0
Anyway,
For the firstDayOfWeek: 1 (Week starts from Monday), It could be achieved like below;
.CX3 .weekGrid {
grid-template-columns: repeat(5, [cell-start] 1fr [cell-end]) 0fr 0fr;
}
.CX3 .weekday.weekday_6,
.CX3 .weekday.weekday_0 {
display: none;
}
.CX3 .cell.weekday_6,
.CX3 .cell.weekday_0 {
display: none;
}
This will work.
But for the firstDayOfWeek:0 or another case, .weekGrid should be adjusted more heavily. And not sure side-effects.
@jimmy_382837
@MMRIZE said in Adjust individual table column widths?:
I haven’t examined the rendered HTML yet, but hardcoded style attributes in HTML code are prior than CSS.
In case; You should modify source code of the module to change the result. (Or consider to use monkey-patch)
The rendered result is not hard-coded, so you can adjust it with only CSS.
This is an example. (Anyway, your config was not exactly matched with your previous screenshot…)
.MMM-OpenWeatherMapForecast .module-content {
width: inherit;
/* I don't know why, but it was defined as 300px, might be an issue when you adjust the dimension. so have to reset */
}
.MMM-OpenWeatherMapForecast,
.MMM-OpenWeatherMapForecast .wrapper {
width: 500px;
/* give a custom width to a module */
}
.MMM-OpenWeatherMapForecast .forecast-item .time {
/* Some customizing for `time` cell for example.*/
width: 200px;
background-color: rgb(127 127 127/ 50%);
color: white;
font-weight: bold;
}
@nekreg9
There is a configurable option “waitFetch”.
But I doubt your real issue would be that. Because, CX3 starts rendering after one calendar which has at least one event have fetched successfully. (and in a “waitFetch”, no more calendar is fetched)
So if your CX3 starts late, It means your events source provider(usually default calendar module) might have timing issue to fetch calendars(e.g. too frequent fetch cycles or something else)
I haven’t examined the rendered HTML yet, but hardcoded style attributes in HTML code are prior than CSS.
In case; You should modify source code of the module to change the result. (Or consider to use monkey-patch)
@Manino
You need to stop “pm2” first before try dev mode. This error means just you are executing mm twice(one from pm2 and one from npm run start:dev). That error is not related with your original issue.
@Manino
Let’s test things.
calendar and MMM-CalendarExt3 then run again.npm run start:dev) => This will show front-end dev console and there might be some useful console log. (or you can populate dev-console on MM with Ctrl+Shift+i or equivalent shortcut keys by your system)@lornetw
(I removed the original post of mine and re-wrote it.)
You can see + CREATE CONFIDENTIALS in upper side.
You can ignore CONFIGURE CONSENT SCREEN. (Or at least later you can configure it.)
After click +CREATE CONFIDENTIALS, you will meet the options, you can select OAuth client ID.
Then you will meet this.
https://developers.google.com/assistant/sdk/reference/rpc/languages?hl=en
As far as I know, Turkish is not supported in Assistant SDK even though Google Assistant itself is supporting Turkish.
@jimmy_382837
What is your config now for your result? I cannot guess your configs.
@Manino
I tested URL you sent me. (Green is that one. I hope this will not be too privacy things.)
{
module: "MMM-CalendarExt3",
position: "bottom_bar",
config: {
mode: 'month',
locale: 'sv-SE',
}
},
{
module: "calendar",
position: "top_left",
config: {
broadcastPastEvents: true,
calendars: [
{
symbol: "calendar-check",
url: "https://ics.calendarlabs.com/709/45a0bb64/Fun_Holidays.ics",
color: "red",
},
{
url: "https://calendar.google.com/calendar/ical/7a9...4/basic.ics", // <- Your real iCAL URL
color: "green",
},
]
}
},
@Manino
But your picture above post shows you have Google Calendar. Could you send me the real URLs of icals? eouia0819@gmail.com
To represent your symptom, I need real data.
but you could walk from end of list back to before today, and now know forward looking and past looking… keep going back to the start date of the calendar view … this is what I do with a port of your code to another platform…
AFAIK, without proper maximumNumberOfDays and maximumEntries values, the bunch of broadcasting will be filled with prior events first up to maximumEntries. So the casted payload will not contain recent newer ones.
Is something changed in default calendar?
@sdetweil @Manino
Maybe your 3 calendars might have tons of events(at least 10) since long long ago time(at least 1 year).
Past events might be too many, so all of the quota for broadcasting was already consumed by the older events.
To test it, remove 3 calendars, try ‘us-holiday’ calendar of the default config example.
If so, check maximumNumberOfDays and maximumEntries of the default calendar module.
I think it is not the bug of that module but unexpected behaviour. Generally, for past events, People will regard newer events than older events as more important. But broadcasting of this calendar module contains older events prior to newer ones.
{
module: "MMM-CalendarExt3",
position: "bottom_bar",
config: {
mode: 'month',
manipulateDateCell: (dom, events) => {
let date = new Date(+dom.dataset.date)
if (date.getMonth() == 8 && date.getDate() == 2) { // specific cell by absolute date
dom.classList.add('specialHoliday')
dom.style.backgroundColor = 'red'
// do whatever you want.
}
if (events.some(e => e.title.search("Gelber") > -1)){ // specific cell by event
dom.classList.add('specialEvent')
dom.style.backgroundColor = 'yellow'
// do whatever you want.
}
}
}
},
