DwmColorBlurMica

[argumentum]

55 minutes ago, WildByDesign said:

I don’t enjoy making the GUI too much. Autoit lacks ability to

..about a web site ?. You can serve ... look at this example and if you can make a decent web gui, then that would work too I guess.

Then you have GUIs like in PE Network Manager that are quite creative:

 

Edited June 15 by argumentum

[WildByDesign]

2 hours ago, argumentum said:

..about a web site ?. You can serve ... look at this example and if you can make a decent web gui, then that would work too I guess.

Wow, that really expands the possibilities for sure. I had no idea that was even possible.

[WildByDesign]

Good news! I've got the custom per-app / per-class functions working. So we can do custom rules with the full spectrum of options.

The was the hard part. The last part that I have to do still is the easy part and that involves falling back to global coloring options (if set) for anything else that does not have custom rules or is not on the exclusion lists.

[WildByDesign]

The first post has been updated with version 0.9.6.

This was a monster of an update. I had to rewrite the majority of how everything worked, new functions, etc. to allow for individual per-app and per-class custom rules. I spent a few days testing it and had to iron out a few bugs, particularly with special handling of apps likes Terminal, VSCode, etc.

Now we can have different colored borders for different apps, different titlebar colors, blur behind on some apps and mica extended to client area on other apps. It's kind of like of buffet now.

Needless to say, I am sure a few more bugs will pop up because almost everything changed. Please start with the new config file as well because a lot was changed and/or removed. There is also another example config file included which shows some examples and ideas.

[WildByDesign]

I just updated the first post with version 0.9.7.

I added support for Task Manager (Blur Behind and ExtendFrameIntoClient) which looks nice and works well. Also some important bug fixes with border colors and some special handling fixes for Windows Terminal.

I added options for GlobalExtendFrameIntoClient and GlobalEnableBlurBehind for people who like too much adventure. It's not the greatest since most apps do not behave well with those. However, for those people, I made it so that the CustomRules can negate this on  per-app or per-class basis with ExtendFrameIntoClient=False or EnableBlurBehind=False

Task Manager screenshot:

Spoiler

 

[WildByDesign]

First post has been updated with version 0.9.9.

I didn't end up releasing 0.9.8 because I noticed a few more issues with global fallback with the custom rules. The idea is that if you leave any of the fields blank in any of the CustomRules sections, it will fallback to global rules. So you only have to specify changed options. If you put False in one of the CustomRules, it will negate whatever the global rule was for that process/class. Some of the global fallback options were failing with 0.9.7 and all of that has been fixed now.

I also added a safety check to make sure that each of the CustomRules sections has the correct number of lines to prevent issues with the CustomRules array. If there is a mismatch, it will let the user know and exit the process.

Also in the unreleased version 0.9.8, I rewrote the entire main coloring function. I rewrote it to ensure that each customrules option will fallback to global if not set. And if there is no match at all, it will follow up with global options. This ensures that the customrules take priority over the global rules. But here's the bonus: The entire function became more efficient and faster. So we accidentally got some performance improvements out of the changes as well.

My initial assumption was that the addition of customrules would have degraded performance if anything. But after rewriting the main coloring function, performance actually improved.

[WildByDesign]

I had some users mention that my compiled binary (last bunch of releases) gets labelled as a virus. Out of all of the AVs out there, only 1 is doing this and of course it happens to be Microsoft. They call it "Trojan:Win32/Sabsik.FL.A!ml" in client version of Defender and "Trojan:Win32/Wacatac.B!ml" with their cloud AV on VirusTotal.

I have submitted it to Microsoft as a false positive in hopes that it gets analyzed and removed sometime in the future but I am not holding my breath.

From my security industry work, I know that the main reason why they do this is to encourage developers to purchase expensive code signing certificates.

I don't know if this detection is AutoIt-related or not. Some of my other projects are getting flagged as well.

Does anybody have any experience with this?

EDIT: I am reading through the 15 page (

) thread now but I don't know how much of that is current information or outdated.

Edited 6 hours ago by WildByDesign

[argumentum]

1 hour ago, WildByDesign said:

Does anybody have any experience with this?
EDIT: I am reading through the 15 page ( ... ) thread now but I don't know how much of that is current information or outdated.

Can not be outdated. These are timeless, as life itself.
I would recommend putting everything in a zip file and add a simple password. That has shown to me to be better A/V wise for downloads.

Edited 6 hours ago by argumentum