Now issue the following command to start MagicMirror in development mode.
npm start dev
This will start MagicMirror in a split screen layout. One side will be the Magic Mirror that you know and love, the other side will be the developer tools console.
Is this correct? I spent quite a bit of time trying to figure this out. Maybe it’s changed.
The developer tools console is surely just the browser console which is achieved by pressing F12.
When I tried the command:
npm start dev
What this did is direct debug messages into the shell where I typed the command, but didn’t change the display in the web browser. I just thought this might help other people following this guide, which is excellent!
@techlady Here is my project in progress. My intent is to mount Pi to back of TV and treat MM as another HDMI input.
As others have said, module writers that stick with the convention of using main.css to format their module make it real easy to format multiple modules by using the appropriate block of main.css and dropping it in custom.css.
Gets sticky when a module author does their own formatting top to bottom.
@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.
@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.
@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.