• Recent
  • Tags
  • Unsolved
  • Solved
  • MagicMirror² Repository
  • Documentation
  • 3rd-Party-Modules
  • Donate
  • Discord
  • Register
  • Login
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.

Is there a way . . .

Scheduled Pinned Locked Moved Troubleshooting
23 Posts 8 Posters 8.0k Views 8 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.
  • ? Offline
    A Former User @BKeyport
    last edited by Dec 18, 2018, 10:51 AM

    @bkeyport
    In modern CSS, you can use variables. If you are using values referenced frequently or dependently, you can set that value as variables.
    In prior example, --body-margin is defined. Now you can use it instead static fixed value 20px. So when you have to change that value, just modify --body-margin once.

    1 Reply Last reply Reply Quote 0
    • B Offline
      BKeyport Module Developer
      last edited by Dec 18, 2018, 12:03 PM

      This is the part that’s getting me…

      width: calc(100vh - var(–body-margin) * 2);
      height: calc(100vw - var(–body-margin) * 2);

      If I’m reading this correctly - it’s taking the calculation of 100% of the viewpoint(direction) - the margin defined in the varible multiplied by 2?

      100% of the viewport height minus 40 pixels in your example?

      The "E" in "Javascript" stands for "Easy"

      ? S 2 Replies Last reply Dec 18, 2018, 12:07 PM Reply Quote 0
      • ? Offline
        A Former User @BKeyport
        last edited by Dec 18, 2018, 12:07 PM

        @bkeyport
        Yes. you are right.
        Just one point, user-defined property should be start with -- not -

        1 Reply Last reply Reply Quote 0
        • S Away
          sdetweil @BKeyport
          last edited by Dec 18, 2018, 2:46 PM

          @bkeyport margin is both sides, or top and bottom. All the way around.

          If u look at the original the width is hard coded at 100%- 2 times the margin value

          Sam

          How to add modules

          learning how to use browser developers window for css changes

          1 Reply Last reply Reply Quote 0
          • B Offline
            BKeyport Module Developer
            last edited by Dec 19, 2018, 10:32 AM

            @sdetweil so, then because I have to use the following:

            body {
            margin: 0px;
            height: calc(100vh - 10px);
            width: calc(100vw - 5px);
            }
            

            am I correct in assuming that magicmirror sees the screen a few pixels bigger than it really is - and that’s being expressed by running off the right and bottom of the screen when I don’t have the 10px subtract from height, and the 5px subtract from width?

            The "E" in "Javascript" stands for "Easy"

            S M 2 Replies Last reply Dec 19, 2018, 1:21 PM Reply Quote 0
            • S Away
              sdetweil @BKeyport
              last edited by Dec 19, 2018, 1:21 PM

              @bkeyport I also had a heck of a time modifying body to get a fullscreen image.
              I finally changed to use the .fullscreen.above css setting. I was also worried that if I required body to be changed and some else’s module also required body changed, then the conflict would mess up my display.

              Sam

              How to add modules

              learning how to use browser developers window for css changes

              1 Reply Last reply Reply Quote 0
              • M Offline
                michael5r Module Developer @BKeyport
                last edited by Dec 29, 2018, 5:49 PM

                @bkeyport said in Is there a way . . .:

                @sdetweil so, then because I have to use the following:

                body {
                margin: 0px;
                height: calc(100vh - 10px);
                width: calc(100vw - 5px);
                }
                

                am I correct in assuming that magicmirror sees the screen a few pixels bigger than it really is - and that’s being expressed by running off the right and bottom of the screen when I don’t have the 10px subtract from height, and the 5px subtract from width?

                No - the screen is the size it is.

                Your CSS above doesn’t make sense (you’re setting a body height that’s 10px smaller than the window height). If you set the body height to be 100vh and you get a vertical scrollbar, it’s because of another margin that’s pushing the body element.

                In general, it’s good practice to also do:

                html {
                    margin: 0;
                    padding: 0;
                }
                

                to avoid situations like this.

                B 1 Reply Last reply Dec 30, 2018, 11:44 AM Reply Quote 0
                • B Offline
                  BKeyport Module Developer @michael5r
                  last edited by Dec 30, 2018, 11:44 AM

                  @michael5r - Actually, I don’t get scrollbars at all. If I don’t subtract back from the 100vh/100vw or 100% - It’ll just run off the edge of the screen as if the system is seeing the screen (In this case, the RasPi’s 7" touchscreen) bigger than it is. With it set the way I have it, everything is dead on edge, giving the maximum use of the screen.

                  The "E" in "Javascript" stands for "Easy"

                  M 1 Reply Last reply Dec 30, 2018, 2:58 PM Reply Quote 0
                  • M Offline
                    michael5r Module Developer @BKeyport
                    last edited by Dec 30, 2018, 2:58 PM

                    @bkeyport said in Is there a way . . .:

                    @michael5r - Actually, I don’t get scrollbars at all. If I don’t subtract back from the 100vh/100vw or 100% - It’ll just run off the edge of the screen as if the system is seeing the screen (In this case, the RasPi’s 7" touchscreen) bigger than it is. With it set the way I have it, everything is dead on edge, giving the maximum use of the screen.

                    I’m glad it works for you, but it still doesn’t make any sense :)

                    J 1 Reply Last reply Dec 30, 2018, 5:09 PM Reply Quote 0
                    • J Offline
                      j.e.f.f Project Sponsor Module Developer @michael5r
                      last edited by Dec 30, 2018, 5:09 PM

                      @michael5r the CSS is also set to hide overflow on the body so even if the CSS defines a screen size larger than 100% you won’t get scroll bars. You’ll just get the contents pushing off screen or at least not centred.

                      M 1 Reply Last reply Dec 30, 2018, 6:23 PM Reply Quote 0
                      • 1
                      • 2
                      • 3
                      • 2 / 3
                      • 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