Thus it is not possible (or at least difficult) to have a batch file that runs at startup which both creates the desired desktops, and then runs programs on the desired. See the scenarios below which explain problems in the current situation, as I understand it, which this feature request aims to resolve.
Request
Allow vdesk on:n to create desktop n if it doesn't already exist.
And, if the current number of desktops m, and n>m+1 then vdesk creates the 'missing' desktops between desktop m and desktop n, as well as creating desktop n.
Allow vdesk on: to additionally use desktop names to identify the desired desktop - see feature request 74
Scenario 1
The batch file would work OK on first boot, when only the default "Desktop 1" exists, using vdesk create[:n]
But on the second run the batch file would create another [n] desktops, and again on every subsequent boot.
Scenario 2
Similarly, if the batch file used only vdesk [args] to create a new desktop for the command, on every boot additional desktops would be created.
Further, if you then wanted the batch file to open a second program on the new desktop using vdesk on:n [args] one the second boot, the second program would open on a different desktop to the first.
i.e. first boot: Desktop1, Desktop2 command1program command2program
second boot: Desktop 1, Desktop2 command2program Desktop3 command1program
Desktops are persistent between boots of windows.
Thus it is not possible (or at least difficult) to have a batch file that runs at startup which both creates the desired desktops, and then runs programs on the desired. See the scenarios below which explain problems in the current situation, as I understand it, which this feature request aims to resolve.
Request Allow vdesk on:n to create desktop n if it doesn't already exist.
And, if the current number of desktops m, and n>m+1 then vdesk creates the 'missing' desktops between desktop m and desktop n, as well as creating desktop n.
Allow vdesk on: to additionally use desktop names to identify the desired desktop - see feature request 74
Scenario 1 The batch file would work OK on first boot, when only the default "Desktop 1" exists, using vdesk create[:n]
But on the second run the batch file would create another [n] desktops, and again on every subsequent boot.
Scenario 2 Similarly, if the batch file used only vdesk [args] to create a new desktop for the command, on every boot additional desktops would be created.
Further, if you then wanted the batch file to open a second program on the new desktop using vdesk on:n [args] one the second boot, the second program would open on a different desktop to the first.
i.e. first boot: Desktop1, Desktop2 command1program command2program second boot: Desktop 1, Desktop2 command2program Desktop3 command1program