Skip to content

Commit 822e284

Browse files
committed
modified: docs/guide.md
1 parent e799cb3 commit 822e284

File tree

2 files changed

+22
-3
lines changed

2 files changed

+22
-3
lines changed

.gitignore

+1
Original file line numberDiff line numberDiff line change
@@ -2,6 +2,7 @@
22
/.build
33
# IDK, AppCode randomly creates this EMPTY file. I have no idea what this is
44
/default.profraw
5+
/.DS_Store
56

67
# XCode User settings
78
xcuserdata/

docs/guide.md

+21-3
Original file line numberDiff line numberDiff line change
@@ -150,10 +150,28 @@ AeroSpace is controlled by commands. For more info see [the list of all availabl
150150

151151
## Emulation of virtual workspaces
152152

153-
The supposed workflow is to only have one macOS Space (or as many as monitors you have) and don't interact with macOS spaces in
154-
any way
153+
Native macOS Spaces have a lot of problems.
155154

156-
When user quits AeroSpace or before crashing, AeroSpace puts windows back to the center of the screen
155+
- You can't disable animation for Spaces switching
156+
- You have a limit of Spaces (up to 16 Spaces with one monitor)
157+
- You can't create, delete, reorder Spaces with hotkeys
158+
- Apple doesn't provide public API to create, delete, reorder and switch Spaces
159+
160+
Since Spaces are so hard to deal with, AeroSpace introduces it's own concept - workspaces. Basically, workspaces are an emulation
161+
of Spaces. If the workspace isn't active then all of the windows of that workspace are placed outside of the visible screen area.
162+
Once you switch back to a workspace (by the binding, or by choosing the workspace in the tray icon list) windows are placed back
163+
to the visible area of the screen.
164+
165+
> [!NOTE]
166+
> For better or worse, macOS doesn't allow to place windows outside of the visible area entirely. You will still be able to see a
167+
> few pixels of "hidden" windows in bottom right corner of your screen. That means, that if you have some problems with AeroSpace
168+
> you will still be able to manually "unhide" the windows by dragging these few pixels to the center of the screen.
169+
170+
When you exit the AeroSpace or when the AeroSpace is about to crash, AeroSpace will place all windows back to the visible area of
171+
the screen.
172+
173+
The supposed workflow is to only have one macOS Space (or as many as monitors you have, if 'Displays have separate Spaces' is
174+
enabled) and don't interact with macOS spaces anymore.
157175

158176
### A note on mission control
159177
TODO DOCUMENTATION

0 commit comments

Comments
 (0)