I have multiple monitors. The main one is a 40" 4K monitor. I do use the split fuction of DisplayFusion to devide it in four quadrants. I then often open a lot of windows / programs into those quadrants (same location every time) and use ALT-Tab to tab through the programs opened in those quadrants. A killer-feature. I can't live without it. Thank you for that.
I also use AHK a lot. I do use it mainly to auto expand phrases for mails etc. Since a couple of versions (I do use beta versions also - but it happened in at least the last stable version of DisplayFusion also). I have the problem that whenever I use the ALT-Tab handler my AHK scripts stops responding and I have to manually reload them. This is 100% reproducable.
So because I mainly use AHK for phrase expanding - I also tried another program - breevy. But it also happens to that one. It seems that DisplayFusion by using Alt-Tab will cut the keyboard handler for programs like AHK. I know there has been a lot of work latly in making the Alt-Tab handler more robust as I have seen in the changelog. But somehow it seems that it now also breaks the use of AHK. At least with multiple monitors and by using the split function. Is there a workaround other than not using Alt-Tab? Because both features AHK and DisplayFusions Alt-Tab are my favurite time savers on my desktop machine.

Thanks

Felix

Just tested. Unfortunatly it doesn't matter which one I launch first. It immediately stops working after the first Alt-Tab

Great, thanks for the update.

Confirming that I see this behaviour as well. Confirmed it was due to Alt-Tab and not other behavior. Confirmed the problem goes away if I close DF. Confirmed that the problem goes away if I disable Alt-Tab in DF settings and just use native Alt-Tab. Looking forward to fix but disabling Alt-Tab works for fine for now. Thanks.

I have a similar (the same?) issue where whenever I use DF's Alt-Tab handler, no mouse clicks are registered until I mash the modifier buttons (Ctrl and Alt). This only happens with both DisplayFusion and AutoHotKey are open. I can confirm it still happens with the latest beta (DF Pro 9.7 Beta 5) on Windows 10 (Windows 10 Enterprise 10.0.17134.0).

There definitely seems to be a bug with the interaction between DF & AHK; whether the bug is on the DF or AHK side, I don't know, and I'm not sure how to troubleshoot it further. It could be that it only happens when certain AHK listeners are registered. To note: since AHK is open source software, its support is community-based.

I have the same issue since I installed AutoHotkey.
A fix would be nice.

Christian