MagicMirror Forum
    • Recent
    • Tags
    • Unsolved
    • Solved
    • MagicMirror² Repository
    • Documentation
    • 3rd-Party-Modules
    • Donate
    • Discord
    • Register
    • Login
    1. Home
    2. mfruckus
    3. Topics
    A New Chapter for MagicMirror: The Community Takes the Lead
    Read the statement by Michael Teeuw here.
    M
    Offline
    • Profile
    • Following 0
    • Followers 0
    • Topics 2
    • Posts 11
    • Groups 0

    Topics

    • M

      Vertical Display Graphical Errors

      Watching Ignoring Scheduled Pinned Locked Moved Unsolved Troubleshooting
      2
      0 Votes
      2 Posts
      623 Views
      M
      I’ve also tried installing just a clean raspbian stretch. However, the problem persists when I rotate the display with only the desktop environment of stretch running. I’m now thinking that the 32" Samsung I’m using may be the issue and I’m going to try out another make/model.
    • M

      Vertical Image Diagonal Line Issue

      Watching Ignoring Scheduled Pinned Locked Moved Unsolved Troubleshooting image resolution
      13
      0 Votes
      13 Posts
      5k Views
      M
      Here’s an update with an even better fix! While beginning my journey into custom css, I quickly came across another fix to the poor graphics of a vertically rotated screen. In my opinion, this fix is even better than using xrandr because this fix saves a ton on performance, results in a look just as good as using the screen in its native horizontal look, and once you implement it, it will stay implemented. All you have to do is copy and paste the following to your MagicMirror’s custom css: body { margin: 0; position: absolute; transform: rotate(90deg); transform-origin: bottom left; width: 100vh; height: 100vw; object-fit: cover; top: -100vw; visibility: visible; } There you go, just like that you’re set. The custom css of modules may have to be edited as well to make it work but that’s a small price to pay for a much better finished product. Credit where credit is due, I found this fix right here on the forum!
    • 1 / 1