DarkMode UDF for AutoIt's Win32GUIs

[WildByDesign]

I need some opinions on something. If you run the ModernDark examples (or set $bPreferNewTheme to True) on a system that is not 24H2/25H2 with latest updates, I have already designed it to fallback to the regular DarkMode_Explorer gracefully. This way the GUI is not left broken.

However, whoever is using it may think that ModernDark is not working properly which is not good.

Should I have some sort of messaging if someone tries to apply DarkMode_DarkTheme (ModernDark) on a system that is not compatible?

Would ConsoleWrite message suffice?

[WildByDesign]

GUIDarkTheme 1.0.0:

• Restructured and reorganized UDF files to match standard UDF requirements
• Renamed functions, global variables and constants
• Ran UDF files through Tidy
• Code cleanup

Making things proper and well organized was a lot more work than I had anticipated. But it does looks much nicer now and I am glad that I took the time to do it.

Please keep in mind that I may have missed a few requirements and there may be a few more things to do for becoming fully UDF compliant. Let me know what else needs to be done.

 

GUIDarkTheme-1.0.0.7z

[pixelsearch]

5 hours ago, WildByDesign said:

Let me know what else needs to be done.

For a future release, "GUIDarkTheme.au3" got 2 arrays that could be updated :

1) Global Const $_g__Style_Button[20][2]
A new updated array can be found here, with 28 rows instead of 20

2) Global Const $_g__Style_Static[18][2]
A new updated array can be found here, with 29 rows instead of 18

[WildByDesign]

1 hour ago, pixelsearch said:

1) Global Const $_g__Style_Button[20][2]
A new updated array can be found here, with 28 rows instead of 20

2) Global Const $_g__Style_Static[18][2]
A new updated array can be found here, with 29 rows instead of 18

Thanks for these. Especially the button styles because I do differentiate between some of the button styles. It is always good to have more possibilities.

I've updated it locally and will have these in the next release.