Hi,
yeah AI is currently still very bad with autohotkey scripts, i also made that experience. There is a v1 and a v2 syntax, and there are a few similar programs (i.e. there is a version which runs on linux) which aim to be "syntax-compatible" but have partially different syntax, and i guess the AI can't tell the difference of all that.

Do you have performance problems? Because for me it runs just fine on a i5-9500M mobile cpu and uses maybe 2-3% cpu when inverting a few windows. I still don't fully understand the code in the Inverter class (i just took it from the mentioned link and changed it from v1 to v2 syntax), so it's difficult for me to improve anything here.

What i want to improve when i have time for it:

• Add a feature which looks at the color of the program's title bar to decide if the window should be inverted.
• Try to fix a bug when there is a dialog which opens another dialog which opens then another dialog (happens in Visual Studio in the Project Options and some other programs) then the 2nd dialog suddenly stops inverting it's color.
• Disable font font smoothing / anti-aliasing (or however it is called) on inverted windows, because a partial inversion (like with the Smart Inversion filter) doesn't invert the smoothed part of the fonts and that makes text very hard to read. I use a windows VM at home which seems to disable that smoothing so i only noticed that at work.

To your suggestions (which sound like they come from an AI..?):

• use Widget instead of WinExist: i will look it up.
• cache the results of calling DllCall("GetWindowInfo", ...): it's only called once and writes in the WINDOWINFO buffer, so i don't see how i could cache something there. Do you have a code example?
• more efficient algorithm to search for an inverter: Do you have a code example? Because i don't know a faster syntax. Also usually there are only a few inverted windows at max, so looping over those few should still be plenty fast. Or do you have a use-case to invert thousands of windows at once?
• use DllCall("magnification.dll\MagUninitialize") only if the inverters are actually used: Do you restart that script every few seconds? I mean i see your point, but the usual use-case would probably be to start the script through Windows autostart and it gets closed when you shutdown the PC, that single Dll call shouldn't matter at all. And if one doesn't remove the 'ahk_class #32770' from the script then to 99% there was a inverter used because very many programs (not only windows, also notepad++ or the modern visual studio code) still have dialogs with class #32770.

Beautiful script, thank you! I recently went on a Windows dark mode crusade and ended up installing SecureUXtheme and modifying my own .msstyles files to inject, just to get some Win32 apps to finally be dark - and there was an AHK script for it all along!

...I do see what that other commenter was saying about optimizing it, though. I have one program assigned to the auto invert group, and this script is eating up over 5% of my CPU (on a new gaming PC, no less), while the target program isn't even running! Is there a way to make this script idle more efficiently, or make a helper script call this script only when the target program is running? I thought it already had the latter feature implemented, but maybe not...

Try the fastest ways: other programs, such as Dark Any App, Easy Window Invert, negativescreen and etc

Well sure, but I'm on github because I like open source. Easy Invert is proprietary, negativescreen can't do individual apps as far as I can tell, and Dark Any App is proprietary and triggered my antivirus as soon as I tried to go to their website, which isn't encouraging

Anyway, I did create a helper script to call this one when the target window is created. I think it would be useful to have some logic in this script that detects when there are no longer any target windows existing, to kill the script. I can't figure out where or how to do that, though. I think it should go somewhere in one of the loops?

Hell yeah I figured it out (I'm a pretty novice programmer so I view this as an accomplishment)

At Line 328 insert:

invLen:= Inverters.Length
if(invLen = 0) {
	Uninitialize(ExitApp,0)
}

It doesn't work properly:
I invert a window. When the window is inactive, it's inverted. Once I activate it, it turns back to normal.
No issue with the original script.

When the taskbar is hidden the script doesnt convert the area where the taskbar used to be. I'm assuming this is an oversight since most people don't have their taskbar set to auto hide? Otherwise great script, makes fusion 360 less of a pain to use! I just wish it worked on the whole screen.

@BillySp33d: A hidden taskbar is now recognized. That feature was not in the original script and yeah i never hide my taskbar 😄 What still doesn't work is inverting below the taskbar when you have a 2nd monitor that goes below the taskbar (that hasn't worked before).
And i enabled per-monitor DPI awareness, so you could have monitors with different DPI settings or when you change the DPI scaling in windows you don't need to restart the script any more.

@charlie89 Thank you. This helps a lot :)

Looks like the inGroup() function is redundant and can be removed.

The text on my pc (acer EX215-31 win11 24h2) appears to be blurred in all apps I've tried (hh.exe, everything.exe, and AHK msgbox).
See example below with AHK help file showing comparison between this script with MatrixHigh dark mode (Feb 18 2025 version) and in-built dark mode.
Is there a way to correct this text blurring?