To get the windows names and classes you can use the "windows spy" tool from AutoHotkey. When you have any script running (from *.ahk file, not compiled to *.exe), you should have "H" icon in the tray. Open its menu with a right mouse button, choose 'windows spy" and turn on 'follow mouse" setting in the top right corner of Window Spy window. Now if you hover a mouse cursor over any window, Window Spy should show a windows class for that window. It's not 100% reliable, as sometimes it shows wrong names, but it usually works fine.Michael Dow wrote: ↑Tue Dec 06, 2022 10:21 amPierre Sosa wrote: ↑Mon Dec 05, 2022 3:25 pmAnother question: do you use "#IfWinActive ahk_class TFruityLoopsMainForm" directive in your scripts? If yes, then the hotkeys won't work for detached windows, as detached windows don't belong to class ahk_class TFruityLoopsMainForm. Try to use "#IfWinActive ahk_exe FL64.exe" directive instead (or "FL64 (scaled).exe" if you use that). Now it should work with detached windows.Michael Dow wrote: ↑Mon Dec 05, 2022 4:11 amThey don't stay on the screen if they aren't detached. Annoyingly they just go back to the other monitor, albeit in a random useless position.
I do use that, ill try that new one thank you so much!
How do you know to enter that? What does ahk_class TFruityLoopsMainForm mean? And why is it called FL Studio? It's not been called that for a decade now. Is FL still calling itself FL Studio in the background?
Also what does MainForm mean?
I'm not at my studio pc at the moment, but just getting ahead, i have a novation launch pad mini mk3 coming soon purely for many of these AHK scripts. Some currently only work when i have a certiain window clicked on. IS there a way to make them all work permanently? For example, i have AHK's setup to automatically load up certain instrument channels. And some to load up certain FX at just the press of a midi button. It's awesome. But works only when a certain window is focused i think.
Now i have 2 monitors again, (first time since using AHK) will i be able to use AHK's that ar linked to the mixer at the same time as the playlist, regardless of which one was last clicked on?
Also
I'm not a programmer, so I'm not sure about from where that T-Form stuff comes, but it probably comes from Visual Component Library framework where classes/windows/controls has that naming convention. But like I said I'm not sure about that.
For the last question I would probably need to have a look into your script to see why it works only for focused window. Also if you plan to use MIDI controller it may be a good idea to get into MIDI scripting.