Troubleshooting

Window positioning needs the macOS Accessibility permission. Go to System Settings → Privacy & Security → Accessibility and turn FluidZones ON. Tip: if FluidZones already shows as enabled there but windows still don't move (typical after updating the app), the entry is stale — toggle it OFF and ON again, or remove it with “−” and re-add the app.

Each icon tells you exactly what happened with that app. A filled ✓ in your theme's accent color means the app launched and its window landed exactly where you set it — everything worked perfectly. A filled ✓ in yellow means the app launched and FluidZones tried to position it, but macOS enforced a minimum window size larger than the assigned zone — the window was anchored as close as possible to the target position. A hollow ✓ in dim gray means the app launched, but its window ended up on a different macOS Space — FluidZones can't move windows across Spaces (a macOS limitation). A filled ✗ in red means the app failed to open entirely.

Some apps enforce a minimum window size and macOS silently overrides any positioning request smaller than that — no window manager can work around this OS constraint. FluidZones detects it, anchors the window to its zone's corner as close as possible, and marks it with a yellow ✓ in the launch HUD so you know the placement was adjusted. Measured minimums for common apps: Arc ~940px wide, Fork ~640px wide. If an app lands wider than its zone, assign it a larger preset (e.g. 'First Two Thirds' instead of 'First Third') or draw a wider custom zone.

When an app is already open on another macOS Space, FluidZones repositions its window there — macOS doesn't provide a public API to move windows across Spaces, so no window manager can do this without using private system calls. The launch HUD marks the app with a dim ✓ and a notification tells you which app landed on another Space. To get all apps on the same desktop, close the app before launching your scene and FluidZones will open it fresh on your current Space.