@sjanssens I just tried that diagnostics approach on my own Surface Pro (9). First I set scaling to 225%, resulting in an effective screen width of 1280 pixels, but that didn’t seem to be narrow enough in the project that I tried. At 250% however (corresponding to 1152 pixels effective width) I could finally reproduce the issue described by @Barry_Chabala . This is consistent with another report posted today - in the latter example, a 1440p (a common resolution for 27") screen in portrait mode with 125% desktop scaling would also result in an effective width of 1152 pixels (I don’t know about the referenced original poster’s OS and desktop scaling ratio though).
For myself I have come to the conclusion to agree that this needs to be looked into - especially because as of now, a mere selection in the score invoking connected information to be displayed in the status bar has the potential to suddenly push the right edge of the UI off the screen even in fullscreen mode. @dspreadbury , please excuse me for tagging you once again, but I suppose that this side effect isn’t what you and the team had in mind, right?
P.S. @Barry_Chabala As long as this isn’t resolved, could you make do with a desktop scaling ratio of 175% for the time being?