Love this XServer - fast and well behaved. However....
When using the Windows 10 Virtual Desktop feature, if an X window is opened on one desktop, then one switches to another desktop and opens a second X window in the same general region of the screen, then switch back to the first desktop, the window contents from the second window are visible and continue to be rendered in the first X window, instead of the contents of the first X window being displayed. The 'bleed through' is clipped to the intersection of the first X window and the second X window (if it were displayed). Simply clicking in the corrupted window cleans it up, and there are no more issues until one switches desktops again, and the problem repeats. It seems like a redraw event is required but not occuring.
If I start two instances of VcXsrv (:0 and :1) and open the first window on the first desktop using :0 and open the second window on the second desktop using :1 then I can switch between desktops without any data or display elements crossing the boundry.
FWIW, neither Exceed nor XWin-32 do not have this problem, but Xming suffers from the problem as well.
I've been seeing this for quite some time. It appears that only unfocused windows are affected. The window that gets focus after the switch does get refreshed with the correct contents.
Agree - it does seem to matter which windows have focus.
Could you try with 1.19.6.2
Could not reproduce during Initial testing. Will broaden my use and test further. Thanks!
Have not been able to reproduce the bleed through problem, but I'm noticing an odd behavior that was not apparent in 1.19.6.0:
When clicking on an XWindow to give it focus, I contantly find myself in selection mode - as if I had held the mouse down in a window that had focus and had started dragging - altough the mouse is not held down and there is no selection yet. Keystrokes are ignored but moving the mouse expands the selection. A second click ends the selection process.
Could you give some more details on how to reproduce, since I do not see this behavior? (Both test in windows 10 (WSL) and windows 7)
Sure - in my case, I have six non-overlapping XTerms open, each having been used (so there's lots of text in the window.) Click around between them, and in each case click to give the window focus, then type a few characters. At some point you'll notice the characters aren't accepted. If you move the mouse, you'll find that you are in the middle of selecting text.
BTW, with is Windows 10 Pro, at the current level.
Last edit: Michael barton 2018-04-20
Still no luck. Wich version of vcxsrv are you using? Which linux distribution are you using?
I just went back to vcxsrv 1.19.6.0, and was able to reproduce the problem. So it's not a result of the latest changes. The Linux system in CentOS 6.9, and vcxsrv is running on Win10 Pro.
I carefully studied the scenario, and I found that I subconsiously drag the mouse outside the window just after I click on the window to give focus. I'm using a trackpad, so there is a possibility of a suprious mouse click in the milliseconds after the window gains focus, as I touch the trackpad to move the mouse.
FWIW, I have never experienced this with XWin-32 or Exceed, so maybe there's a difference in how quickly mouse events are processed after the window gains focus. Is there a setting for this?