corentin-soriano commented on PR #1061: URL: https://github.com/apache/guacamole-client/pull/1061#issuecomment-3043771155
> I have done a little testing using docker images built from your two branches. Great work so far! > > By default the `resize method` configuration option is set to a blank entry. If you specify a maximum number of secondary monitors and leave the resize method blank you will only get a white screen when trying to open a secondary monitor. This is presumably why you added `needs display-update` to the label, but I just overlooked it the first time, because i didn't know what was meant. Maybe you could create an `Enable secondary monitors` checkbox, which I think would greatly improve the UX for administrating this feature. Checking the checkbox would: > > * fix the resize method to `display-update` (set the value and disable the dropdown if that is possible, maybe show a warning about the required RDP version) > * enable the text field for the maximum secondary monitors (and set a default value?) > * cause the button for opening another monitor to be displayed during the connection > > Another thing I noticed testing a connection from Chrome on Windows 10 to a Windows 11 PC is that dragging a window to the secondary monitor will create visual artifacts as in the screenshot below. It uses a Chrome window as an example but the same happens for other windows, e.g. the file explorer or CMD. > >  > > 1. If I drag the window from primary to secondary without releasing the mouse button, I **get** the artifacts on the window in the secondary monitor. > 2. If I drag the window from secondary to primary without releasing the mouse button, I **do not get** the artifacts on the window in the primary monitor. > 3. If I drag the window from primary to the edge of the screen, release the mouse button and move the mouse to the secondary monitor, then grab the window on the secondary monitor and drag it in, I **get** the artifacts on the window in the secondary monitor. > 4. If I drag the window from secondary to the edge of the screen, release the mouse button and move the mouse to the primary monitor, then grab the window on the primary monitor and drag it in, I **get** the artifacts on the window in the primary monitor. > > Note how only dragging without releasing to the primary does not generate artifacts. Moving windows around in the monitor they were created in does not create artifacts for either monitor. I have only tested with two monitors (primary + secondary). > > Otherwise it has been working great so far. I will continue testing it over the next days. I haven't had time to research a fix yet, but I've already identified this issue. These are copies of a piece of image from one screen to another screen that do not work (and leave the old image). The bug occurs because each window ignores the instructions sent to other screens, so the part to be copied is not known. Regarding the other comments, I will try to improve them. Thanks for taking the time to test and provide feedback! -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@guacamole.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
