MagicMirror Forum
    • Recent
    • Tags
    • Unsolved
    • Solved
    • MagicMirror² Repository
    • Documentation
    • 3rd-Party-Modules
    • Donate
    • Discord
    • Register
    • Login
    A New Chapter for MagicMirror: The Community Takes the Lead
    Read the statement by Michael Teeuw here.

    ALT or ALT+Spacebar

    Scheduled Pinned Locked Moved Unsolved Troubleshooting
    8 Posts 2 Posters 230 Views 2 Watching
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • S Offline
      sdetweil @ankonaskiff17
      last edited by

      @ankonaskiff17 restart it in dev mode

      npm run start:dev

      Sam

      How to add modules

      learning how to use browser developers window for css changes

      ankonaskiff17A 1 Reply Last reply Reply Quote 0
      • ankonaskiff17A Offline
        ankonaskiff17 @sdetweil
        last edited by

        @sdetweil Am I right in that these problems are tied to this Wayland/labwc change?
        Just looking at how MM appears when it goes from fullscreen to “not fullscreen” is what prompts my question.

        S 1 Reply Last reply Reply Quote 0
        • S Offline
          sdetweil @ankonaskiff17
          last edited by

          @ankonaskiff17 yes, its wayland and labwc. all new UI interface… SO much fun… not

          Sam

          How to add modules

          learning how to use browser developers window for css changes

          ankonaskiff17A 1 Reply Last reply Reply Quote 0
          • ankonaskiff17A Offline
            ankonaskiff17 @sdetweil
            last edited by

            @sdetweil I pulled to a stop on finishing this particular MM to make sure it was not something that I did incorrectly or something that could be resolved by me just changing a setting or something along those lines but after picking at it on and off for a few days that does not appear to be the case.

            As of right now I feel like I can work around the problem, but is it something that is going to have to be resolved by yourself and the other maintainers?
            Just my nature to poke at problems like this to better understand. There is very little information out there and mostly what is out there seems to be of minimal technical value. Sort of “We rolled out Wayland, enjoy” or “Raspberry Pi rolled out Wayland, enjoy” repeated in a hundred different locations.

            Related to the above, how do I determine the MM version? I have a MM, the first one I built that I felt really good about, and it has been chugging along just fine for a few years now. I know it needs updating but I have been reticent about doing that update because of this issue ever since Wayland was initially rolled out by Raspberry Pi. Sort of “If it ain’t broke, don’t fix it.”

            S 1 Reply Last reply Reply Quote 0
            • S Offline
              sdetweil @ankonaskiff17
              last edited by

              @ankonaskiff17 mm version

              cd ~/MagicMirror
              grep version package.json

              Wayland was introduced three Raspi OS releases ago.
              its ‘better’ than X11 they say

              WE MagicMirror don’t have any choice.

              Sam

              How to add modules

              learning how to use browser developers window for css changes

              1 Reply Last reply Reply Quote 0
              • 1 / 1
              • First post
                Last post
              Enjoying MagicMirror? Please consider a donation!
              MagicMirror created by Michael Teeuw.
              Forum managed by Sam, technical setup by Karsten.
              This forum is using NodeBB as its core | Contributors
              Contact | Privacy Policy