Leaderboard

I have thought again and this is simpler and the better solution. #NoTrayIcon ;#RequireAdmin #include <WinAPISys.au3> #include <GDIPlus.au3> #include <WinAPIShellEx.au3> #include <GUIConstantsEx.au3> #include <WindowsConstants.au3> #include <ButtonConstants.au3> #include <StaticConstants.au3> Example() Func Example() Local $hGUI, $hGraphic, $hIcon, $hBitmap, $iX = 768, $iY = 525 $hGUI = GUICreate("GDI+", $iX, $iY) _GDIPlus_Startup() ; Create GUI Global $idPic = GUICtrlCreatePic("", 0, 0, $iX, $iY) Global $sFileName = @ScriptDir& "\MAIN.png" $hImage = _GDIPlus_ImageLoadFromFile($sFileName) $iX = _GDIPlus_ImageGetWidth($hImage) $iY = _GDIPlus_ImageGetHeight($hImage) $hBGImage = _GDIPlus_BitmapCreateFromScan0($iX, $iY) $hGraphic = _GDIPlus_ImageGetGraphicsContext($hBGImage) _GDIPlus_GraphicsDrawImage($hGraphic, $hImage, 0, 0) $btnx = 250 $btny = 150 ;_GDIPlus_GraphicsClear($hGraphic, 0xFFFFFFFF) $hIcon = _WinAPI_ShellExtractIcon(@SystemDir & '\shell32.dll', 221, 48, 48) $hBitmap = _GDIPlus_BitmapCreateFromHICON32($hIcon) _GDIPlus_GraphicsDrawImage($hGraphic, $hBitmap, $btnx, $btny) $shBitmap = _GDIPlus_BitmapCreateHBITMAPFromBitmap($hBGImage) _WinAPI_DeleteObject(GUICtrlSendMsg($idPic, 0x0172, 0, $shBitmap)) ; STM_SETIMAGE = 0x0172, $IMAGE_BITMAP = 0 GUICtrlSetState($idPic, $gui_disable) GUICtrlSetState(-1, $GUI_ONTOP) GUICtrlSetCursor(-1, 0) $hIcon = GUICtrlCreateIcon(@SystemDir & '\shell32.dll', -1, $btnx, $btny, 48, 48, BitOR($SS_NOTIFY, $SS_BLACKRECT)) GUISetState() ; Loop until user exits Do Switch GUIGetMsg() Case $GUI_EVENT_CLOSE ExitLoop Case $hIcon ConsoleWrite("Icon clicked" & @CRLF) EndSwitch Until False ; Clean up resources _WinAPI_DestroyIcon($hIcon) _WinAPI_DeleteObject($shBitmap) _GDIPlus_BitmapDispose($hImage) _GDIPlus_BitmapDispose($hBGImage) _GDIPlus_BitmapDispose($hBitmap) _GDIPlus_GraphicsDispose($hGraphic) _GDIPlus_Shutdown() EndFunc ;==>Example

I've updated the first post with version 1.0.1. It might be the smallest update with the least amount of changes. However, it is by far the most significant to me. I was finally able to get the compiled x64 binary to avoid the False Positive from Windows Defender. I actually tried about a dozen different changes and none of them got rid of the false positive. The one single change that did get rid of the false positive: #AutoIt3Wrapper_Compression=0 That's it. That is all. I was so disappointed with the false positive on every single prior version, but now I am ecstatic. Now I have to get rid of the false positives on my 5 or 6 other AutoIt programs. I'm wondering if they should change the default compression level because of this.

You have to exclude the area of the icon off the bitmap (graphic). One example:

Awesome thank you!

Version 1.0.0 has been updated on the first post. After failing to figure out color tinted blur for weeks now, I have finally figured it out. Now you can have blur tinted with any color. There are global options for this and per-app / per-class options. So you can have as many apps as you want all with varying colors of tinted blur with varying intensities. And some with all of the other stuff too. I've been so busy building this thing that I haven't actually had much time to play with it. But I am imagining the crazy amount of possibilities right now.

Apologies for the late reply, I have been awol for a bit. Generally speaking, if the object name starts with windows.* then it'll be built into the OS. So we should have a decent chance of making these ones work. The Microsoft.* objects however are usually external. For these we'll probably need dependencies or a runtime in order to use them. So "Microsoft.UI.Content.DesktopChildSiteBridge" looks to be part of the Windows App SDK (And maybe WinUI3??). There will be associated *.winmd files in the SDK somewhere that contain object definitions. From these we should be able to wrap any object that we'll need in order to change colours etc.. But the tricky bit is how to implement the external objects/controls in the first place. Hope that makes sense. I will eventually get around to attacking this WinUI stuff - It'll just be whenever I have the time and energy to throw at it