You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have installed Xpra in a Windows 10.
Started with command: Xpra.exe shadow --bind-tcp=[0.0.0.0:2222](http://0.0.0.0:2222/) --min-quality=70 --sharing=true --html=on --video-encoders=h264 command. Screen resolution is 1920X1080
Then, in another computer in same network, open a Chrome browser with url: ":2222". Resolution also 1920x1080.
Because chrome windows has border with menus, etc. The server screen can not be seen completely in browser page.
It seems that the browser view is centered in server screen and borders can not be seen/controlled.
And the mouse are not in sync.
In a bigger client screen with broser big enough to see complete server display the mouse are ok.
Also checked that with browser bigger that server display the mouse are also not in sync.
Tow questions:
The mouse shift can be fixed with some server and/or client parameters?
The display can be zoomed/scaled so it fit into the browser windows?
Thanks.
The text was updated successfully, but these errors were encountered:
I have installed Xpra in a Windows 10.
Started with command:
Xpra.exe shadow --bind-tcp=[0.0.0.0:2222](http://0.0.0.0:2222/) --min-quality=70 --sharing=true --html=on --video-encoders=h264
command. Screen resolution is 1920X1080Then, in another computer in same network, open a Chrome browser with url: ":2222". Resolution also 1920x1080.
Because chrome windows has border with menus, etc. The server screen can not be seen completely in browser page.
It seems that the browser view is centered in server screen and borders can not be seen/controlled.
And the mouse are not in sync.
In a bigger client screen with broser big enough to see complete server display the mouse are ok.
Also checked that with browser bigger that server display the mouse are also not in sync.
Tow questions:
Thanks.
The text was updated successfully, but these errors were encountered: