Fullscreen sort of works, as long as the server-side screen size matches the client's. When it doesn't, the window backing is painted with an offset:
This is made worse by the fact that the opengl client paints from the bottom of the screen (inverted Y coordinates), so the pointer location reported doesn't match what is on-screen...
r16209 added a
Shift+F11 client-side fullscreen switch so we can make any window fullscreen, even an xterm - useful for testing.
r16218 also makes it easier to test:
XPRA_FORCE_SCREEN_MISMATCH=1 will ensure that the server-side resolution used by desktop servers never matches the client's.
FORCE_SCREEN_MISMATCH=1 xpra start-desktop --start=xterm -d screen,geometry
xpra attach -d geometry
Shift+F11 and the xterm is shown in one place, but actually responds to mouse events at an offset..
Should be fixed in r16219.
Note on resolutions: if we cannot find a match for the client's screen size in the server's list of pre-defined resolutions, then the fullscreened window will be displayed with black borders around it.
The steps in the list of resolutions are 64 pixels below 4k, and 128 pixels for resolutions above 4k. So the worst case scenario (which should be rare) is that you will get about 30 black pixels around the window when showing fullscreen. (and double that for resolutions higher than 4k) The most common resolutions are already pre-defined and will work without borders (ie: 1080p, 1440p, 1600x1200, etc..)
Shift+F11 shortcut was being ignored on MS Windows upgrades because the default system wide config was not being overwritten on upgrade - this is changed in r16426.
This means that modifying the default system config should be done by adding new files in
xpra/conf.d and not by modifying existing ones as those will be overwritten on the next upgrade.
this ticket has been moved to: https://github.com/Xpra-org/xpra/issues/1567