> opens nearby dictionary, flips to ‘politics’, grabs red pen and writes /* ... */ around definition <

YEP! Still works! :)

I wasn’t referring to the actual module files. I’m talking simply editing the config.js file and comment the specific module’s config section out.

Yeah, the acrylic, at the monitor size (22x15), would be about $103 … But I’m putting it on a wall, a much larger piece … that’s gonna be 'spensive!

Yep, when I’m done cleaning it up. I have this thing against repeating blocks of code, which I had to do here, once for an all day event and again for a timed one. So let me rewrite it first and clean it up.

Yeah, I saw that too when using Edge. I need to spent some time looking into that, but I’m also working on other code … one thing at a time. :)

Basically the pulled a MacGyver then … :)

I have a 27" monitor (rotated vertical) on my desk that has MM running on it. It’s my development rig. No mirror, really, I don’t need to be staring at my face the whole time. So that aspect is obviously doable.

As for having the other information, Bitcoin, weather, others, those are all things that can be integrated, so long as you have the software written for it to interface with MM’s module mechanism. Anything’s possible.

As for the touch screen part, that’s between the monitor and the Raspberry Pi. MM (or any other software you run) doesn’t have anything to do with that part. So your first point to research is how to make the touchscreen work on the rpi. Are there drivers for it? How does it interface, etc., etc. But more importantly, have you tried just plugging it in, see if it doesn’t “just work” already?

My knee jerk answer is to find the model of the screen, and search eBay for a driver for it. The driver board will have the ribbon cable you need to connect to that, and the board will have the standard HDMI input on it. Simply typing in ‘lcd driver board’ on eBay’s search bar will get you a long list of them. By also entering the model of the screen, you can narrow that down.

Sorry, it was funny. I’ll go back to my dark cave now. :)

Got a reply on there at least. I don’t want the user to think we’re ignoring it.

You can easily have another module (module_scheduler?) keep track of time and when require, it can call another module’s .hide() or .show() routine. And you’d want to check on the other module every so often, in case the mirror restarted and re-displayed it.