Skip to main content
BrendanPrice
Contributor II
Oct 10, 2018 11:45 PM UTC

Windows Controller 9.2 doesn't remember window position

The new Sonos Controller app for Windows doesn't remember the window location anymore, meaning that every single time I open the app I have to drag it back to where I want it. Can this please be added back in? Thanks.
      This topic has been closed for further comments. You can use the search bar to find a similar topic, or create a new one by clicking Create Topic at the top of the page.

      19 replies

      johnseay
      Enthusiast I
      Oct 11, 2018 3:09 PM UTC
      Absolutely fix this! The desktop controller has been able to remember its size and position for years. This is a bug that was missed in testing that needs to be fixed.
      Translate
        HiFiAtLast
        Trending Lyricist I
        Oct 11, 2018 5:13 PM UTC
        Yes, I agree 100%
        I have a long-established Desktop layout and - until now - the Sonos Controller opened reliably in the exact area to which I'd 'assigned' it. It's now a PIA to to have to RE-move its window each time I open it.
        I'm using 64-bit Windows 7.
        (In case it's relevant to the Sonos Controller developers, I have no intentions ever of upgrading to Windows 10.)
        Colin P.
        Translate
          Ryan S
          Ryan S
          Retired Sonos Staff
          Oct 11, 2018 5:16 PM UTC
          Hi guys, the team is looking into this one. Thanks for the report!
          Translate
          Mark good posts by pressing the like button, and select the best answer on questions you've asked to help others find solutions.
            bitwranglers
            Contributor I
            Oct 12, 2018 12:03 AM UTC
            On my 4K monitor the 9.2 application takes over a huge portion of the screen, right in the middle. Sono's Mark W. advises there hasn't been any changes made to the default window size with the Sonos controller for desktop.
            This is more than likely something specific to your system and Windows applications generally do not start with specific window sizes based on the application you're using.
            Sorry Mark - large change in behavior - and it doesn't recall and reset the size and location settings of the previous instance. Here's how you do it using the registry in C#:

            this.Left = (int)(Registry.GetValue(keyName, "PositionX", 0));
            this.Top = (int)(Registry.GetValue(keyName, "PositionY", 0));
            this.Height= (int)(Registry.GetValue(keyName, "Height", 250));
            this.Width = (int)(Registry.GetValue(keyName, "Width", 200));

            Set the key values on closing, restore on activation. Everything is exactly as you left it.
            Not hard. Very user friendly. Highly recommended.
            Translate
              Dave_O
              Avid Contributor I
              Oct 12, 2018 1:56 PM UTC
              This is clearly a bug in the new version. Developers can fix this easily.
              Translate
              billfalls
              Trending Lyricist I
              Oct 31, 2018 7:20 PM UTC
              Another longtime user with the same problem, started a few days ago after an update on a Windows 10 PC.
              Translate
              Airgetlam
              Airgetlam
              Oct 31, 2018 7:46 PM UTC
              Please see Ryan S' response above.
              Translate
              Bruce
              xdbmw
              Lyricist I
              Nov 28, 2018 7:12 PM UTC
              ...unfortunately ***NOT*** fixed in v9.3...
              Translate
                Beuki
                Lyricist I
                Nov 29, 2018 8:54 AM UTC
                Same here on my 4k Screen, everytime I open the app I have to resize it back to normal screen size instead of a Huge window over all my other windows.
                Translate
                Snapgate
                Lyricist I
                Dec 6, 2018 3:48 PM UTC
                Ryan, I understand the team are looking into this, but that was a month ago. Since then you have released another version and still not fixed this issue. As a developer I know how simple this is to fix (and also how this should have been caught by your testing before release). Why has this issue still not been addressed?
                Translate
                  Show more replies
                  Terms & ConditionsAccessibility statement