Leaderboard

ACL Viewer (WildByDesign/ACLViewer: ACL Viewer for Windows) This would not have been possible without the amazing support from this forum. I received so much great help and I am thankful. I wanted to give back to the community by sharing what I have come up with. I overcame a lot of challenges. So I am hoping that this (or parts of this) may benefit others. I have other AutoIt-created programs on my GitHub also which I will likely share here in the forum when I have more time to get all the information together. Screenshot: Features: automatic dark mode / light mode depending on system theme settings treeview for selecting files/folders for viewing ACLs listview for displaying parsed ACEs custom ACCESS_MASK parser listviews for displaying permissions with checkboxes Includes: TreeListExplorer by @Kanashius DarkMode UDF originally by @NoNameCode, updated by @argumentum GUIFrame UDF by @Melba23 ACL Permissions UDF originally by @FredAI, updated by @AdamUL There are other functions within the code that I received incredible help on from the forum and I added credits and links within the code.

Personally I dislike declaring variables between includes. It should be declared inside the included file. All UDF should be auto-sufficient. No offense. edit : if you need to share a global variable between UDF, the source UDF should provide a function to retrieve that variable instead of relying on the knowledge of a variable name...

Thank you for mentioning this. I will have it fixed in the next build. This is really neat. I am still very new to AutoIt, so I had never thought of adding some Global variables before specific includes. It works great, thank you. It changed my way of thinking as well since being a script, it goes in order line by line. That way it is declared before the other include is loaded. This seems so simple, yet I did not know. So I appreciate it. Also thank you for the simplification of the dark mode function, that is incredible. This makes me excited to learn more about AutoIt and improve my abilities.

Generally respecting the indentation when commenting or un-commentating a line seems like the best approach in my opinion. Doing it like in SciTE, gives issues, when you want to indent a section containing an out-commented line of code, where with vscode the identation is no issue and un-commentating the line later, does not produce the same possible problems.

... #include <Misc.au3> Global $isDarkMode = False Global $sRet, $aRet, $newItem, $oldItem, $isFolder, $aUniques, $TV_Icons #include "include\GUIFrame.au3" ... would solve that. But also: ;~ isDarkMode() ;~ Func isDarkMode() ;~ Global $isDarkMode = _WinAPI_ShouldAppsUseDarkMode() ;~ EndFunc ;==>isDarkModeisDarkMode() ;------------------------------------------------------------- ;~ Global $isDarkMode = isDarkMode() ;~ Func isDarkMode() ;~ Return _WinAPI_ShouldAppsUseDarkMode() ;~ EndFunc ;==>isDarkMode ;------------------------------------------------------------- Global $isDarkMode = _WinAPI_ShouldAppsUseDarkMode() ;------------------------------------------------------------- this could be simplified. Using #AutoIt3Wrapper_Au3Check_Parameters=-q -d -w 1 -w 2 -w 3 -w 4 -w 5 -w 6 -w 7 would force you to confront these things. At one year old ( you joined less than a year ago ), your script is better than I ever did at 1 year old. Thanks for sharing @WildByDesign

Got this error in GUIFrame :

This is an UDF to print the content and type of any variable. This includes basic datatypes, as well as all data in multidimensional arrays, DllStructs, Maps, some Objects like Dictionaries,... Basically any datatype I could think of. By Default, the datatype is given, this can be turned of. Additionally the spacing can be tuned to ones liking. I hope you like it and feel free to provide some feedback for improvement. Example: Output: ToString.au3 ToString Example.au3

Just for the heck of it: I've modified my forked repo extension code to include these standard shortcuts/tasks : Tidy (Ctrl+t) Au3Stripper (Ctrl+Shift+x) AddIncludes (Ctrl+Shift+m) .. and think this works nicer than defining the tasks.json. Also added a fix to be able to cope with the -1 returncode from Tidy.

THE TITLE SAY'S ALL. Image SearchAllVersion.zip

THANK YOU

Unfortunately the OSVersion info doesn't provide enough information especially when dealing with multiple build versions of Windows 10 in our environment, as some of our software doesn't work across all builds (usually because some features are only available on specific builds): OS Versions: 7, 10, 2008 R2, 2012 R2, 2016, 2019 OS Editions: Home, Professional or Enterprise OS Builds: 1709, 1803, 1809, 1903, 1909 HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion can usually be used to determine most of this info, however WMI is generally more consistent when running across multiple OS versions. Global $g_sOSCaption, $g_sOSVersion _GetOSInfo() ConsoleWrite("OS Caption : " & $g_sOSCaption & @CRLF & "OS Version : " & $g_sOSVersion & @CRLF) Func _GetOSInfo() Local $oSystemSet = ObjGet("winmgmts:").InstancesOf ("Win32_OperatingSystem") If IsObj($oSystemSet) Then For $oSystem In $oSystemSet $g_sOSCaption = $oSystem.Caption $g_sOSVersion = $oSystem.Version Next EndIf EndFunc