_NET_NUMBER_OF_DESKTOPSto match the client
This should allow application which are virtual desktop aware to work properly.
With this in place, I can see:
$ xprop -root | egrep "_NET_DESKTOP_NAMES\(UTF8_STRING\)|_NET_NUMBER_OF_DESKTOPS\(CARDINAL\)" _NET_DESKTOP_NAMES(UTF8_STRING) = "desktop 1", "desktop 2" _NET_NUMBER_OF_DESKTOPS(CARDINAL) = 2
Or with xpra info:
$ xpra info | egrep "desktops|desktop_names" client.desktop_names=('desktop 1', 'desktop 2') client.desktops=2
And changing the preferences on the client side is immediately reflected on the server side.
Ready for testing:
How to test:
xpra control :DISPLAY WINDOWID WORKSPACE(ie:
xpra control :10 1 2moves window 1 to workspace 2)
No matter which method is used, the value shown in xpra info should be consistent with reality.
Support for win32 and OSX has been moved to #776, as this will take longer.
xpra info(did an xpra info :13 | grep workspace )
xpra control :13 3 2returns
server returned error code 6 invalid command
OSX client.. Win8.1 client..
Workspace info not found in xpra info
The workspace is only shown if it has been set to something meaningful. (the default is unset)
$ xpra info | grep workspace= window.workspace=0 window.workspace=1
xpra control :13 3 2 returns
Oops, sorry about that - I forgot the verb. The control command to use is:
xpra control :DISPLAY workspace WINDOWID WORKSPACE
xpra control :DISPLAY workspace 1 2
The test app does not show any workspace information and does not appear to work.
It does not show workspace information, it is used to set it. (but you have to use a supported OS, not OSX...)
xpra control :13 workspace 3 0 I can move firefox between workspaces. Interestingly if I use a number higher than the maximum number of workspaces(that is, moving to workspace 4 when I only have 2) it'll just move it to the highest workspace number(in my case 2). This works with both Fedora 21 and CentOS 6.4.
In addition, the python app(now that I know how to use it) works as expected. I can use it to move across workspaces in both Fedora 21 and CentOS 6.4.
xpra info | grep workspace is showing correct values, as well.
Re-assigning back to you
if I use a number higher than the maximum number of workspaces it'll just move it to the highest workspace number
Yes, it is capped.
Looks done, closing.
Windows 10 support moved to #1442
MacOS in #2488
this ticket has been moved to: https://github.com/Xpra-org/xpra/issues/774