Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature Request] Better approach to get the amount of windows in each workspace respectively #174

Closed
XOR-op opened this issue Mar 2, 2024 · 1 comment

Comments

@XOR-op
Copy link
Contributor

XOR-op commented Mar 2, 2024

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:

  1. In the toolbar dropdown, add the count of windows in workspace to each workspace.
  2. Add more information when querying multiple workspaces, e.g. adding workspace names to the window information.
  3. Optimize CLI call performance.
@XOR-op
Copy link
Contributor Author

XOR-op commented Sep 17, 2024

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.

@XOR-op XOR-op closed this as completed Sep 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant