Hey @noisneil, I’m looking forward to using this. My first observation when testing with Keyboard Maestro itself: when I launched Keyboard Maestro, it positioned the Variable Inspector Window instead of the Editor window.
That surprised me as I didn’t realize that window could be targeted by the Resize Window action. Perhaps adding logic to use the front window’s name as well could prevent this?
The reason I haven't gone past "front window only" yet, is that it gets very complex very quickly when you start taking window names into account. It's fine for something like KM where the Editor's window name is constant, but browsers or text editors, not so much. So having one macro that can deal with both scenarios could be a bit tricky. Perhaps you could have a user selectable option to deal with this. Hmm....
To control the situation can we apply an alias’ of sorts as the ‘first hand’ control and link those to what is actually open somehow? I know what you’re saying, difficult to account for all the different scenarios but I thought it were coded such that we were in control of those 5-7 windows, we could have an app mimic what say, window 4 does (but you can’t see window four because its not real). Then if there is more fake windows than apps, well it doesn’t sort of matter. Could be a dumb idea I’m just starting to learn this stuff on the Mac