Subcategories

• Upcoming Features

  New upcoming features available in the beta branch will be announced here.

  12
  Topics
  115
  Posts

  

  @pana507 @sdetweil So, yay I got it working! Guess I’ll need to write some kind of tutorial, not too easy but here a few first steps: Install “simple-keyboard” in your module via npm Bind it into the JS getStyles: function () { return [ this.file('node_modules/simple-keyboard/build/css/index.css') ]; }, getScripts: function () { return [ this.file('node_modules/simple-keyboard/build/index.js') ]; }, Create a div in your DOM building function. Something like that: const kb = document.createElement("div"); kb.className = "simple-keyboard"; container.appendChild(kb); The class is important! Then, AFTER the DOM element is created, you can create the keyboard class. I did this as soon as a text field was clicked on. With this method I can make sure that the DOM is created already: input.addEventListener("focus", event => { if (!this.keyboard) { var Keyboard = window.SimpleKeyboard.default; this.keyboard = new Keyboard({ onChange: input => this.onChange(input), onKeyPress: button => this.onKeyPress(button) }); } this.keyboard.keyboardDOM.classList.add("show-keyboard"); }); I guess this can be shortened but I keep the running system for now. You can see there are a lot of other functions (this.onChange, this.onKeyPress…) Basically they are designed to hide the keyboard if I klick anywhere else and show it if I click on the input field. I have the concept from here: https://franciscohodge.com/projects/simple-keyboard/demos/show-hide-demo/ Simple-keyboard is well documented for npm including lots of sample code, so with a bit of knowledge you’ll find your way around eventually. Still need to test it on the raspi itself and for all it’s function.
• Feature Requests

  You have a cool idea for the core? Post it here.

  100
  Topics
  499
  Posts

  S

  @Alex2020 run this to disable the screensaver esegui questo per disabilitare lo screensaver bash -c "$(curl -sL https://raw.githubusercontent.com/sdetweil/MagicMirror_scripts/master/screensaveroff.sh)"
• Bug Hunt

  Think you found a bug? Check with others to see if it’s just you. Real bug reports can be submitted via GitHub.

  Report Bug
  103
  Topics
  497
  Posts

  L

  My mirror’s time can get late for the system time. Everything within the MM environment works by that late time, e.g the default clock and scheduled commands (MMM-ScriptScheduler items). The only scenario I can recreate this manually is stopping the mirror by “pm2 stop mm” and then rebooting it. After reboot there is about a 12 second latency. Spot time displayed by the clock module and in the top line of htop. Performing a (shutdown)-(waiting)-(starting the system) procedure extends this interval. The more the RPi stays switched off the more the time difference will be. Refreshing the browser with Ctrl-R corrects the problem. I have 3 mirrors running at the moment. (Actually, only one of them is a physical mirror but let’s call them like that.) mirror1: RPi4 4GB, MM v2.10.1, node v10.19.0, LAN mirror2: Rpi3B+, MM v2.10.1, node v10.19.0, LAN mirror3: Rpi3B+, MM v2.9.0, node v10.17.0, WiFi Only mirror1 and mirror2 (the PRi’s with MM v2.10.1) can be forced to the above 12 sec delay. All of them run the same config on 16GB SD cards. Modules: MMM-ScriptScheduler MMM-GoogleMapsTraffic calendar clock MMM-LocalTemperature (with DHT22 sensor) currentweather weatherforecast plus the MagicMirror-Display-Controller python program (with RCWL-0516 sensor)
• Tutorials
  63
  Topics
  957
  Posts

  S

  @veejae addess: “localhost”, means listen ONLY inside (from myself)… change to address: “0.0.0.0” (listen from anywhere)