Windows: issue on HiDPI monitor and multiple monitors

Windows
1

Here is an issue and a potential fix. Maybe a better fix could be found. Here are steps to reproduce, reproduced on both master and develop branches:

  1. Setup: get a Windows machine with a High DPI main monitor (i.e. scale factor 200%) and a 100% scale factor secondary display, with secondary display “arranged” to be to the left of the primary display. Note, the first issue (A below) can likely be reproduced without the secondary display. But, I believe the second issue (B below) is caused by the same thing (and is what lead me down this road).
  2. Build and launch HelloWorldDemo.

A. Start with the window positioned towards the top of the primary (HiDPI) display. Click on the titlebar of the window. Very slowly, drag the window towards the bottom of the screen. You will see the mouse cursor “detach” from the titlebar of the window. If you drag slow enough the mouse cursor will be in the middle of the window before the window gets to the bottom of the screen. Note, I was using an Intel Macbook Pro with Bootcamp, so perhaps the trackpad contributes to the issue.

B. Second issue. When you drag the window from the primary (HiDPI) display to the secondary (100% scale factor) display the window size should adjust. If it does not then when the window is on the secondary display it will be too big. This is the main problem I’m investigating. To reproduce it drag the window slowly from the primary to the secondary display. Here’s the key: go very slowly and start dragging the titlebar just to the left of the minimize button.

Potential solution:
I believe this is all related to the position constraining code (handlePositionChanging) in the HWNDComponentPeer. It always constrains the position to even coordinates. I suppose it is scaling pixel values to points and then back and this is losing some precision. What seems to work for me is this:

-    auto getNewPositionIfNotRoundingError = [] (int posIn, float newPos)
+    auto getNewPositionIfNotRoundingError = [this] (int posIn, float newPos)
    {
-        return (std::abs ((float) posIn - newPos) >= 1.0f) ? roundToInt (newPos) : posIn;
+        return (std::abs ((float) posIn - newPos) >= scaleFactor) ? roundToInt (newPos) : posIn;
    };

Thanks for listening! Hopefully this helps reproduce and maybe figure out a better fix.

Best,
Rob

2

I was unable to repro this on my machine (with 200% and 100% monitor setup).

Window resizing across scaling boundaries worked correctly and I saw no weirdness with the mouse cursor.

What branch did you see this issue on?

3

Hi Oli, thanks for taking a look! Starting with just “problem A” from above, I just reproduced it again on the tip of master (7.0.12) using a Dell XPS notebook with a HiDPI display (no external monitor connected). I attached a zip of a screen recording of this so you can see what I mean. If you watch the video look at how I click the mouse on the D of “DemoRunner” in the titlebar. Then I slowly drag the window to the right. By the time the window is closer to the right edge of the screen you can see the mouse cursor has moved to the right side of “DemoRunner”.

While this is a slight annoyance this was also contributing to issue B above when I was originally looking into this.

Anyway, I hope the video helps and thanks again!

juce_cursor_lag.zip (7.2 MB)

4

Thanks for the video.

Are you using a mouse or a touchpad? I assume it’s reproducable on either, if so?

5

I was using the integrated touchpad on the Dell XPS but I just tried again with a Logitech mouse and reproduced with that as well. The key is to drag very very slowly.