I have noticed a change in the mouse behavior between 6.x and 7.x that has me concerned enough to consider it a possible bug. I am running Viewer 220.127.116.11 and Installed Host 18.104.22.168 with Windows 10 on both ends.
The issue is when the RU viewer is NOT the active window and you return to it and click somewhere on the remote computer's screen, the CLICK is registered, but the new position of the mouse is NOT registered, causing the click to happen wherever the mouse was last used on the screen. This can be problematic as you may click on something that you did not intend to click on.
I believe intended behavior (and prior behavior in 6.x) would be to update the mouse position on the remote screen BEFORE sending the click command to ensure proper mouse cursor location for the click.
Steps to reproduce:
1. Connect to a remote session. 2. Confirm that mouse clicks are operating as intended within the viewer to the remote screen. 3. Move the mouse out of the RU viewer making sure that where your mouse leaves the screen, it is on an icon that you can identify. In my tests, I had the desktop showing and moved my mouse off the screen to the left so that the "Recycle Bin" was the last thing it was on. 4. Click a window other than the RU viewer to make it inactive. 5. Return to the RU viewer remote session and RIGHT click on an empty area of the desktop. You SHOULD get the right click menu options at the point where you clicked. Where the menu actually pops up will be where your mouse left the screen (recycle bin icon in my case).
I will forward the issue along with the video provided by Trent to our developers for a review and we will additionally try to reproduce it in our environment to see if we can fix it in the next update. I'll get back to you with a reply from our developers shortly.
I'll keep everyone updated on the issue in this thread.