First of all, thank you for building such a great tool. I'm really enjoying it.
My setup has 3 monitor (the MacBook's built-in and two external Dell ones). When AeroSpace is enabled and I try to start a recording on a specific screen with Screen Studio, the overlays that Screen Studio should be showing individually on each screen become all cluttered in a single one which makes it impossible to start the recording.

Disabling AeroSpace solves the issue but it is not ideal since I want to record the screen with it on.
Additionally, I've tried the following on my config but it doesn't work.
[[on-window-detected]]
if.app-id = 'com.timpler.screenstudio'
check-further-callbacks = true
run = 'layout floating'
Based on that, I believe this could be related to (1) How AeroSpace manages screens and workspaces or (2) Aerospace interfering in the way the overlays are being rendered.
AeroSpace version
❯ aerospace --version
aerospace CLI client version: 0.14.2-Beta 0cb8dbdfc5ee73b8cbc200f175f467ebead55201
AeroSpace.app server version: 0.14.2-Beta 0cb8dbdfc5ee73b8cbc200f175f467ebead55201
Let me know if I van provide any additional information.
Edit 1:
Further investigating it, it looks like what is happening is that AeroSpace is moving all the overlays to the focused screen which is making them cover each other.
Originally posted by @emiliosheinz in #993
First of all, thank you for building such a great tool. I'm really enjoying it.
My setup has 3 monitor (the MacBook's built-in and two external Dell ones). When AeroSpace is enabled and I try to start a recording on a specific screen with Screen Studio, the overlays that Screen Studio should be showing individually on each screen become all cluttered in a single one which makes it impossible to start the recording.
Disabling AeroSpace solves the issue but it is not ideal since I want to record the screen with it on.
Additionally, I've tried the following on my config but it doesn't work.
Based on that, I believe this could be related to (1) How AeroSpace manages screens and workspaces or (2) Aerospace interfering in the way the overlays are being rendered.
AeroSpace version
Let me know if I van provide any additional information.
Edit 1:
Further investigating it, it looks like what is happening is that AeroSpace is moving all the overlays to the focused screen which is making them cover each other.
Originally posted by @emiliosheinz in #993