When opening Test or progress window they are displayed with padding outside to the right and bottom. (This also happens to the configuration window but is less of a problem)
The smaller the window, the larger the area doesn't show anything useful.
The behaviour is the same regardless of if the window is docked or popped out.
Ncrunch version 5.20.0.2, Rider 2025.3
I've had the same issue for a long time -- it helps to change the window to force a redraw (either change size or toggle output to be shown right/bottom). The problem does however reappear shortly after.
My suspicion right now is that the problem is being caused by the DPI scaling not being handled consistently through the wormhole.
Has the problem returned at all now that your DPI scaling is consistent between monitors?
If not, does turning on the scaling difference cause it to reappear? Perhaps if the application is started on one monitor then dragged over to the other?
Ok, tried this:
1. Laptop and externals screen, both on 100% DPI
Started Rider, Tests and processing queue windowed on laptop, the rest on external screen. Both windows filled and no padding, it takes a while for the dark theme to set in which is kind of ugly.
Moved the windows around, docked and undocked them etc. Everything worked fine. No padding.
2. Docked the windows on external screen. Changed DPI to 125%. Rescaling test window docked works as expected. Popped out to laptop, looks good. Rescaling, looks good.
Docked back to rider and the padding reappeared. Popped out, padding still there.
3. Closed and reopened Rider, test window popped out on laptop, padding is there.Changed scaling back to 100%, padding prevails, docking, undocking does nothing.
4. Restarts rider(now with no DPI), padding gone, everybody’s happy.
From what you've provided, I've had a go at reproducing this problem. I can occasionally produce intermittent problems where the tool window has padding, but resizing it always immediately corrects the issue. This contrasts with the issue you've described where resizing the tool window never fixes the padding.
If resizing isn't fixing the padding, this is more serious as it means that the tool window 'thinks' that the scaling or dimensions for its monitor are different to what they actually are. Where resizing solves the issue, this means that the problem is just an event that hasn't triggered when the scaling situation has changed.
I'm wondering if you're having any luck finding a consistent way to reproduce a problem where resizing the window does not correct the padding. Working between two monitors with different scaling, I'm having trouble achieving this myself.
Ok, some more data:
Laptop 2560x1600(recommended), 125% scaling
Screen (main display) 5120x1400 (recommended), 100% scaling
Opened Rider in windowed mode on main screen and test window docked and pinned. Resizing the window does not help, maximized, does not help. Padding stays the same pixel width and height
Closed and restarted, Rider now in maximized mode, testwindow docked. Padding still there. Resizing the testwindow docked, padding stays the same pixel width and height.
Popped out the testwindow by pressing the 3 dots and choosing float. The window pops out without padding but as soon as I touch it the padding reappears.
Thanks!
I changed to 125% scaling for the laptop and restarted. Now the padding is almost gone, there is like 5-10 pixels left
Changed to 150% scaling, same result.
Behaviour is the same regardless if the window is docked or popped out. (Rider maximized or windowed)
Thanks. This may be able the best I'm able to do here. This is a Winforms UI being piped through 3 processes and into a JVM environment, inside a dockable pane that it can't control, and subject to a lot of DPI hacks to prevent it from warping.