@ankonaskiff17 yes just delete the node modules folder in the module folder and redo the npm install no guarantee it will change the results best just to ignore the messages

@strawberry-3-141 but thats not true on intel I get one version on arm (32bit) I get a diffferent version on arm (64bit) I get a different version on aarch64 i get a different version especially if there is a binary… and who knows what is buried under there

@ankonaskiff17 note there are two different date format strings dates and times full dates ( all day)

@sdetweil Sent you an email

@ankonaskiff17 same here, oops… just snap the cover on…

I have a feeling that they just stop working or fire their support because I cannot find any activity on the Dakboard during this period. But yes, this is too funny a situation.

@KiaSohc loading is the default message while waiting for data so we need to look at the output of npm start if you use pm2 to launch MagicMirror then you need to do pm2 logs --lines=50

@sdetweil Anything to be done for it? When I have just MM running all is well . Just seems to be a problem when editing. So that is coming from the origin point of link? It is national radar from NWS and I don’t update it locally in config.js I’ll swag this and guess it generates that Vuex stuff locally when the NWS updates the radar image remotely?

Hi @ankonaskiff17 , there are very simple answers to both of your questions ;-) Imagine the horizontal ticker like one long strip of text, which just moves/flies over your screen from the outer right to the outer left position: |<<- Stock1 - Stock2 - Stock3 - Stock4 | Now, if Stock4 reaches the left corner of your screen, there would be a gap on the screen to its right. That’s why there is a second “clone” of the ticker that fills that gap and moves right after the first one. Once the first one completely left the screen, it lines up again after the first one. With that, you get an infinite loop. Jast is built with TypeScript. What you see, is a minified and uglyfied, transpiler generated version of the module. If you are interested in the source code, just check the files in the /src folder. Please feel free to submit a Pull Request, if you found a way to avoid that the module runs out of the screen. I think a minor css change should fix that.

@mumblebaj Thanks

@jalibu Pi 4

@ankonaskiff17 preferred is the way that works

@sdetweil Have it read MM/DD/YY, even on the day of event. Either 6 or 7 days out from calendar event, the date swaps from MM/DD/YY to Monday at 12:00 AM. (For US Labor Day holiday, in this case) hideTimegets me to it just showing Monday. I thought getRelative: 0, was used to do what I want it to do, You have option of from between 0 - 48 hours with default being 6 hours it goes to relative time. It is swapping at about 6 - 7 DAYS in reality. Maybe just a coincidence but it seems like the default getRelative: 6;is 6 days, not hours, and setting it to zero has no effect.

@hango said in Generic CSS question when target is several layers down: if he put something between clock and calendar or change position the ID is changing good point… I hadn’t thought of classes for that kind of purpose…

I have two of the default calendar modules, one above the other both visually and in config.js. module_1_calendarand module_2_calendar. I have both modules with dateFormat set to MM/DD/YY. I also have getRelative: 0, which in the configure options description says will force the calendar event to stay absolute vs at a configured time (0 - 48) with default being 6. My understanding could be way off the mark but I translate that as saying right up to and including the day of the event it will stay in 'MM/DD/YY' rather than what is shown in attached picture of my config.js file. The default 6 hours isn’t really the issue either as the circled Wednesday at 12:AM is way out beyond 6 hours. In the end I do not want either calendar to show anything but 'MM/DD/YY' and I thought the combination of the date format and forcing the getRelative would accomplish that. [image: 1630176840682-getrelative.jpg] [image: 1630176754141-relative-vs-absolute.jpg]

@sdetweil I have a ton of pictures from rocket launches to elk in Rockies. I somehow or another had found Dak Board and piddled with it but it was a subscription based system that MagicMirror puts to shame.

@ankonaskiff17 i think so

@ankonaskiff17 ah, yes. that’s likely fullscreen below, or inserted at the same place, Prime example of fullscreen below being used is MMM-BackgroundSlideshow. Fullscreen above, I don’t know of anything using it, other than the built in alert module.

@cowboysdude I understand the purpose of custom.css and in the end main.css which I copy to custom.css will be different than main.css. When you run MM on a big 45+ inch TV , each module is really small so if you park module X at top_left and park module Y at bottom_right you have two small modules that are same small size and would seem better to do them both with one block of css. The other thing that I want to understand is if the top, bottom, left and right sections scale up on big monitor? If I put a module in top_left is the right edge of the module hitting the right side of the left section. My first pass at this was module by module in custom.css and it was a chore. I’m first to admit i’m a noob in extreme at this but after upscaling each module one by one I was wondering if there was an easier way. I subsequently blew up whole thing so opted to start over. I don’t mind that I killed module via that very css but on second pass I’d as soon avoid the module by module tweaking. As @sdetweil says, just piling in more modules not way to go. Standard PC monitor it is not an issue. All the modules seem written with PC monitor in mind. In my use case I want MM to occupy one of HDMI ports on TV, with other HDMI port being cable TV. I can just toggle inputs on TV remote to flip between the two. [image: 1627182779095-module-question.jpg]

@ankonaskiff17 n custom.css entry #module_2_calendar { background-color:lightblue; } sorry, I had used my cal identifier changed to yours