Jeezy

@Lethaquell Can you confirm if you are running `komorebic start` or `komorebic start --ffm`? The latter is a custom implementation which (should) handle cases like this in a less frustrating...

I guess "more CPU usage" is relative to the actual CPU you're running; what is a little on my Ryzen might not be the case for everyone. 😅 Unfortunately the...

I've finally got some bandwidth to start exploring process elevation related issues now. Is there any chance you could provide a video of what is happening here? I'm struggling to...

@Vernetzt it took a long time, but I think this is now fixed with the latest commit. (which was also tested by @ozokuz 🙏)

I've been trying to replicate this behaviour locally (W10) with the same applications (VSCode and Edge as the only applications on separate workspaces) but I have not been able to....

Great idea! This isn't possible right now, but I will work on this very soon.

Hey @snide! I'm very excited to see your video! Feel free to join the Discord to ask questions or open issues for anything that I can help with while you're...

I am able to reproduce this behaviour locally. `komorebi` uses [`SetFocus`](https://docs.microsoft.com/en-us/windows/win32/api/winuser/nf-winuser-setfocus) whenenver a window is [focused using CLI commands](https://github.com/LGUG2Z/komorebi/blob/master/komorebi/src/window.rs#L233) > Sets the keyboard focus to the specified window. The window...

[This](https://github.com/workspacer/workspacer/commit/1c02613cea485f1ae97f70d6399f7124aeb31297) seems to be the only difference in focus handling. I just tried implementing this in `komorebi` but unfortunately I am seeing the same behaviour with Tablacus Explorer. 😞

Can you describe the behaviours your are seeing in a little more detail and share the commit that you are currently running from? This is the only commit that I...