Set a minimum number of workspaces, while still allowing for dynamic workspaces beyond the minimum.
Note: Binary files aren't shown on the web site. To see all files, please download the extension zipfile.
| Version | Status |
|---|---|
| 10 | Active |
| 9 | Active |
| 8 | Inactive |
| 7 | Inactive |
| 6 | Rejected |
| 5 | Inactive |
| 4 | Inactive |
| 3 | Inactive |
| 2 | Inactive |
| 1 | Rejected |
Fixed issue: https://github.com/philbot9/gnome-shell-minimum-workspaces/issues/1 Added Localization: https://github.com/philbot9/gnome-shell-minimum-workspaces/pull/2
Instead of disabling the extension (Which extension shouldn't do) just don't do anything when dynamic workspaces are enabled.
Thanks for reviewing the extension. I get what you mean. An extension disabling itself is kinda weird. However, I think in this case it makes sense. The reason is that the extension will automatically switch from static to dynamic workspaces whenever it is enabled. To explain what I mean let's assume the extension did not disable itself once the user switches to static workspaces: Step 1: User has been using static workspaces and now enables the extension. Extension switches Gnome Shell to dynamic workspaces and does its thing (keeping a number of them alive). Step 2: User decides he wants to use static workspaces again and switches Gnome Shell back to static workspaces using the Gnome-Tweak-Tool. Step 3: User reboots (or restarts shell). Extension will notice that Gnome Shell is set to static workspaces and switch it back to dynamic workspaces automatically and do it's thing again. This will be very confusing to the user, because he just enabled static workspaces before the reboot, and now all of a sudden they are dynamic again. I hope that explains what I mean. I can't really think of another way to avoid this issue, other than automatically disabling the extension. Maybe you have a suggestion? Thanks.
Minimum Workspaces