You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My use case: I always open a lot of windows on different workspaces, and it's difficult to remember which specific window in which workspace. Previously I use AltTab to see which window in which workspace with vanilla macOS space, but that does not apply to Aerospace.
Potential workarounds that do not work: Use CLI command to extract information. However, because of the overhead of CLI, this solution is imperfect now. In specific, one CLI call costs 60ms on my machine (where Swift runtime initialization could costs 10ms, tested by aerospace list-windows returning help message), and 400ms for querying all my 10 workspaces, which is an unacceptable lag (related to #104). Another approach is to query many workspaces in one call. However, current response does not separate windows in different workspaces, therefore cannot be used for this purpose.
Potential Solution:
In the toolbar dropdown, add the count of windows in workspace to each workspace.
Add more information when querying multiple workspaces, e.g. adding workspace names to the window information.
Optimize CLI call performance.
The text was updated successfully, but these errors were encountered:
This issue is mostly resolved with the new introduced "aerospace list-windows --format", which can get windows and their space ids in one 60ms command.
My use case: I always open a lot of windows on different workspaces, and it's difficult to remember which specific window in which workspace. Previously I use AltTab to see which window in which workspace with vanilla macOS space, but that does not apply to Aerospace.
Potential workarounds that do not work: Use CLI command to extract information. However, because of the overhead of CLI, this solution is imperfect now. In specific, one CLI call costs 60ms on my machine (where Swift runtime initialization could costs 10ms, tested by
aerospace list-windows
returning help message), and 400ms for querying all my 10 workspaces, which is an unacceptable lag (related to #104). Another approach is to query many workspaces in one call. However, current response does not separate windows in different workspaces, therefore cannot be used for this purpose.Potential Solution:
The text was updated successfully, but these errors were encountered: