Hi,

I've been "getting by" with the various issues the NCrunch UI has with scaling when using multiple monitors with different DPI

Most of the time when the UI looks odd I can just wiggle something to trigger a re-render, like resizing the toolbox or adjusting the split. However, This doesn't work with the Hot Spots toolbox.

Here's what it looked like when I opened the Hot Spots tool window:

https://ibb.co/vD39pzk

As you can see the header area is taking up a lot of virtical space and the table is only showing 1 column. After stretching the window across both monitors I can see another column. But even after resizing as many columns as I can this way, I still don't see any timing information.

https://ibb.co/bzMjjqg

NCrunch version: 5.7.0.1

Monitor details:

1) Main screen: 3840x2400 at 250% scale
2) Landscape screen: 2560x1440 at 125% scale
3) Portrait screen: 1440x2560 at 100% scale

https://ibb.co/n37RWdv

As a bonus, here's how the context menu appears when you right click on the NCrunch icon :D

https://ibb.co/2ybCJGb

That's great to hear !

Looking forward to it.

Thanks for the update. I’ll test this version tomorrow and get back to you

I'm sorry to hear it's not working. Can I ask what version of windows and visual studio you are using? I haven't been able to reproduce what you are seeing. Do you have any window managers running like power toys?

Thanks for sharing these extra details.

We've put a lot of time into trying to reproduce further problems with the DPI scaling in the way that you've described, but we can't seem to make them happen.

I believe the issues you're seeing may be somehow specific to your system configuration or hardware set. DPI scaling is a really tough area for us to work in, because we are using two entirely different UI systems concurrently (winforms+WPF) while integrated inside another application. We've noticed that handling for having different DPI scale settings across multiple screens is somewhat hit-and-miss through many Windows applications, and the story seems to change across versions of the O/S and platform.

Handling for different DPI scaling set in parallel has always been a stretch goal for us. I am, actually, somewhat surprised we've managed to handle it as well as we have (Michael deserves much credit for this), but at some stage we need to draw a line here. We can only fix the problems we can find, and DPI scaling itself currently seems to be a can of worms full of other cans of worms scaled across edge cases.

Unfortunately, we can't provide further support in this area. As a workaround, I recommend bolting NCrunch tool windows directly into the main IDE window. This should give more stable behaviour as the lifespan of the tool windows should be bounded within the same DPI scaling.