running Wing Pro 9.0.0.6 on Debian 10 amd64
IDE is displayed on monitor 2, when hovering over variable in IDE, help is displayed on monitor 1
moving IDE to monitor 1 (without resize), help is displayed on monitor 1
attaching screenshot of the first case where hover is displayed on wrong monitor
This should be fixed in Wing 9.0.1 when it becomes available. Thanks for reporting this problem!
This issue still somewhat exists in Wing Pro 9.1.1.0, although when it appears is a bit different.
Normally the pop-up info is shown on the same monitor that my mouse pointer is on, except for the following situation:
When my monitors/screens go to sleep while I have Wing running (due to inactivity), when I return and the screens come back, debugging in Wing shows the pop-up on the wrong screen.
Before my screens go to sleep, the debug pop-up shows on the correct monitor.
Workaround: I restart Wing and then it works again (until I leave the computer and the screens go to sleep while I have Wing open).
Ubuntu MATE 22.04.2 LTS 64-bit Kernel Linux 5.15.0-71-lowlatency x86_64
Does it work if you drag the window back and forth between monitors after they go to sleep? Is it the case that all popups are shown on the primary monitor?
It works when I drag the window back and forth between monitors. Afterwards, the pop-ups show up correctly. I hadn't tried that before, that's a good workaround. Initially after the monitors wake up, the pop-up will show on the secondary screen (when Wing is on the primary screen). I have 2 screens. If I leave Wing on the second screen and the monitors go to sleep, afterwards, the pop-up will show up properly on the second screen. So the variable pop-ups appear to 'prefer' the second monitor after the monitors wake up.
Interesting ... moving the windows back and forth may be the best workaround for now. We'll try to look at this in future releases.
ok, thanks!
Comments
What desktop environment are you using? Is it X11 or Wayland based?
X11 - I am using XFCE desktop environment if that matters. thanks.
I've reproduced this on Debian 11. We'll try to fix it soon.
thank you!