Leaderboard

Thank you @pixelsearch and @argumentum for your recent help in getting me past my struggle with the ownerdrawn status bar. That was the last piece needed for my complete GUI rewrite and I was able to release version 6 this morning, compiled on GitHub Actions. If you have any desire to view the code or play with the compiled binaries (mainly AppControlPolicy.exe) to see how well the custom status bar functions in the running program, feel free. I am thankful and appreciative for your time and help. An interesting side effect: Everything got way faster, somehow. Rewriting the entire GUI somehow made everything a lot faster. Yay! The program does require Windows 11 though because App Control for Business (WDAC aka Windows Defender Application Control) requires Windows 11 and is on all SKUs. Link: Release App Control Tray and Policy Manager 6.0 · WildByDesign/WDACTrayTool By the way, the system tray tool component got a lot of improvements recently as well.

This is fantastic. Thank you. I remember writing those 633 lines out about a year ago when I first started with AutoIt. I was thinking "there must be a better way to do this". I didn't even know how to do any kind of For loops at the time. But the great thing is now I can easily expand with this to support more than 32 policies. I haven't tested it yet but I will try it later tonight and run it through so real policy setups. This is incredible. EDIT: After some solid testing, this seems perfect. I haven't ran into any issues with it. I'm assuming that I can increase the number 32 if I need to support more policies, is that correct?

@WildByDesign imho, in AppControlPolicy.au3, you could replace 633 lines with 13 lines Original 633 lines... If $policycount = 0 Then ; line 378 ... EndIf ; line 1010 ...could be replaced with these 13 lines : Select Case $policycount = 0 Global $aWords[1][11] Case IsInt($policycount) And $policycount >= 1 And $policycount <= 32 Global $aWords[$policycount][11] For $i = 0 To $policycount - 1 For $j = 1 To 10 $aWords[$i][$j] = $arpol[$i*10 + $j] Next Next Case Else Global $aWords[1][11] = [["", "Error:", "Error " & $policycorrect & " &" & " Error " & $policycount, "", "", "", "", "", "", "", ""]] EndSelect For what it's worth, these 4 tests display what they should (if not mistaken), fingers crossed Edit: the 3rd test should probably be done like the following, still showing correctly an error, as $policycount is not an integer (in the script, its value = $policycorrect / 10)

quick and dirty fix: Global $topstatus9 = StringStripWS($topstatus8, $STR_STRIPLEADING + $STR_STRIPTRAILING + $STR_STRIPSPACES) & @CR & @CR & @CR & @CR & @CR & @CR & @CR & @CR & @CR & @CR & @CR & @CR

oops do happen from time to time. Do use OnDebugMsgBox ( or a version of it ) to handle said

I know that I don't have the proper setup but AppControlPolicy.au3 : "C:\Users\Administrator\Downloads\WDACTrayTool-6.0\WDACTrayTool-6.0\AppControlPolicy.au3" (1087) : ==> Array variable has incorrect number of subscripts or subscript dimension range exceeded.: Global $CurrentPolicyStatus = $sVDriverStatus & " | " & $sSACStatus & " | " & $aPolicyStatus[1] & " | " & $aPolicyStatus[2] Global $CurrentPolicyStatus = $sVDriverStatus & " | " & $sSACStatus & " | " & $aPolicyStatus[1] & " | " & ^ ERROR and AppControlTray.au3 did not show while insisting with : Get-CimInstance : Provider load failure At line:1 char:1 + Get-CimInstance -ClassName Win32_DeviceGuard -Namespace root\Microsof ... + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : NotSpecified: (root\Microsoft\...n32_DeviceGuard:String) [Get-CimInstance], CimException + FullyQualifiedErrorId : HRESULT 0x80041013,Microsoft.Management.Infrastructure.CimCmdlets.GetCimInstanceCommand Much of coding is "how would all this work if the user ... " better known as beta testing So yes, the first thing to do is to announce your program is running and that it can be closed or, some quick review to make sure it can run before any announcement, or something that will not produce either a crash and/or hanging of the program. Will it run with Win11 home, or Win Seven, or god knows. Is the service that makes all this work loaded and should I quit or offer to enable it ?, should I make a watchdog in the tray to make sure that is reenabled ?, should I ... it's a head scratcher, I know. But you are writing this to help users and those can be clueless, very clueless Ok, I'll see if I find the prerequisites and install it in the test PC.

Please disregard my last comment about DPI scaling issues with your status bar. I made one minor measurement mistake and it was causing my ListView to partly cover the status bar under different DPI scaling settings. Your status bar is 100% perfect as it is under different DPI scaling settings. Further, my suggestion to add changing of the font was also a bad suggestion. The font in your status bar already scales the text size properly with DPI scaling. Changing the font, as I found out the hard way, actually caused the text of the status bar to no longer scale properly under different DPI settings. TL;DR: Everything is perfect. No changes required. Have a great weekend with the family!

When working cross platform I have found this method of opening (especially Excel) files saves a lot of debugging... #include<Excel.au3> #include<File.au3> $message = "Select Workbook" $var = FileOpenDialog($message, @DesktopDir & "\", "Excel (*.xls;*.xlsx)", 1) If @error Then MsgBox(4096, "", "No File Selected - Exiting") Return 0 Else $var = StringReplace($var, "|", @CRLF) EndIf $oExcel = _ExcelBookOpen($var) switch @error case 1 MsgBox(0,"Unable to Create Object","") case 2 MsgBox(0,"File Does Not Exist","") case 0 MsgBox(0,"Works!","") EndSwitch Good Luck