Layouts should be per-Space as well as per-Screen

[ianyh]

No description provided.

[ianyh]

The APIs for identifying spaces are private, but it may be possible to heuristically fingerprint a space via its visible windows with -[NSWindow windowNumbersWithOptions] or something like that. Have to figure out the edge cases (e.g, what if we don't catch a window creation in an off space and thus lose our key?).

[dhgwilliam]

@ianyh this doesn't work consistently for me, although it might be because my desktops tend to be identical. e.g.:
S1: [ 'Google Chrome', 'KeepassX' ]
S2: [ 'Google Chrome', 'Google Chrome', 'KeepassX' ]
S3: [ 'Google Chrome', 'iTerm2', 'Google Chrome', 'KeepassX' ]
S4: (de facto float space) [ 'Hibari', 'Adium', 'KeepassX' ]
S5: [ 'Google Chrome' ]

Ideas?

[ianyh]

Hm. Does KeepassX persist across spaces? It's possible that would confuse the logic of determining which space we're in. I'll download it and give it a try.

[dhgwilliam]

Not naturally, no. I have manually set it to be on All Spaces. I mostly keep it hidden, but sometimes I forget to hide it. I do the same thing wth NValt.

[ianyh]

@dhgwilliam I think this should work. I tested it with keepassx across all spaces. Let me know if you run into trouble.

[dhgwilliam]

@ianyh it appears to improve space detection, but it introduces a significant performance issue. amethyst is unresponsive for several seconds after changing spaces.

[ianyh]

Hm. I haven't noticed any slowdown on my end. It's possible I just have significantly less windows than you do. I'll look into it.

[ianyh]

Opened #46 to track performance issue.