WMI ScriptOMatic tool for AutoIt

[argumentum]

update for 2016.05.16
fixed the combobox not working everywhere.
added setting to, in addition to Dynamic Classes, to include Abstract Classes.
added a filter ( easier to look for what you need ).

updated file in the files section.

ScriptOMatic.Add_To_ScITE_Tools_Menu.au3

Edited May 17, 2015 by argumentum
fix the "Add_To_ScITE_Tools" script, now attached here

[argumentum]

update for 2015.05.25
fixed "Send to ScITE" ( wasn't working well )
added the ability to remove fields/properties from the generated arrays

updated file in the files section.

[argumentum]

update for 2015.06.08
changed the CIMv2 button to switch between CIMv2 and WMI. ( is a more practical use of the button )
added some support for remote connections. ( executes remotely based in the classes discovered in local PC )
added Save to Disk for the filter by right-click the button. ( is anoying having to set it every time )
fix CPU usage was higher than needed in the main loop. ( ..less abuse on the PC )
added the position in the array to the "select properties". ( when an error pops up, the position is there,
 making it easier to find it in the listview )

updated file in the files section.

[argumentum]

update for 2015.06.11
added a "nice" COM error handler ( in Autoit v3.2 if there is a COM error it'll tell you and no more run,
  in v3.3 it will let it slide but you don't realize there was one. So I put together a COM error handler
  that will gather all the errors and show'em to you in an array displayed by _ArrayDisplay. It includes
  the line number and the line of code it self. nice. )
added the Scite lexer. ( There are code generated that is over 6000 lines long and that is a bit too much for
  the edit control, so, I decided that since is gonna run in a PC that most likely is to have ScITE, using
  the DLL just makes sense. Everything that is needed is taken from your installation, colors, fonts, etc.
  In case that ScITE is not there, then, the edit control would be used. )

updated file in the files section.

[UEZ]

I like the progress on this project - well done!

Thanks for sharing!

[mLipok]

some CleanUp

 

[argumentum]

some CleanUp

​for some reason the version you posted is giving me errors in Array.au3. It should not happen as Array.au3 is unrelated, ...no clue. But I've been up for close to 24 hrs. I'll look at it later

[mLipok]

show me console output 

 

[argumentum]

show me console output 

>Running:(3.3.12.0):C:\Program Files (x86)\AutoIt3\autoit3.exe "G:\au3forum\Scriptomatic(2015.05.04)\scriptomaticOld2005.au3"    
--> Press Ctrl+Alt+Break to Restart or Ctrl+Break to Stop
"C:\Program Files (x86)\AutoIt3\Include\Array.au3" (346) : ==> Variable used without being declared.:
Local $iDim_1 = UBound($avArray, $UBOUND_ROWS) - 1
Local $iDim_1 = UBound($avArray, ^ ERROR
->10:47:18 AutoIt3.exe ended.rc:1
+>10:47:18 AutoIt3Wrapper Finished.
>Exit code: 1    Time: 1.107

 

[mLipok]

Just when you start script or after some user actions ?

[mLipok]

new link.

[argumentum]

new link.

​no clue, for some reason it gives me the error using _ArrayDelete but in my messed up code it don't. I don't see a reason for the failure =/

edit: at line # 2707

Edited June 11, 2015 by argumentum

[mLipok]

uncoment this:

#Autoit3Wrapper_Testing=y

EDIT:
replace this below code with the follwing

#AutoIt3Wrapper_run_debug_mode=Y

 

Edited June 11, 2015 by mLipok

[argumentum]

uncoment this:

EDIT:
replace this below code with the follwing

#AutoIt3Wrapper_run_debug_mode=Y

​cool, good to know :)

expandcollapse popup

!> Starting in DebugMode..
Line: @error-@extended: Line syntax
0016: 0-0: #Region ScriptOMatic - Options
0017: 0-0: #NoTrayIcon
0018: 0-0: Opt("GUICloseOnESC", 0)
0019: 0-0: Opt("MustDeclareVars", 1)
0021: 0-0: #AutoIt3Wrapper_Res_Description=Tool to generate WMI code for AutoIt3.
0022: 0-0: #AutoIt3Wrapper_Res_Fileversion=0.2015.6.11
0023: 0-0: #AutoIt3Wrapper_Run_Au3Stripper=y ; for v3.3
0024: 0-0: #AutoIt3Wrapper_Run_Tidy=y
0025: 0-0: #AutoIt3Wrapper_Au3Check_Parameters=-d -w 1 -w 2 -w 3 -w- 4 -w 5 -w 6 -w 7
0026: 0-0: #AutoIt3Wrapper_Run_Au3Check=N
0028: 0-0: #AutoIt3Wrapper_run_debug_mode=Y
0029: 0-0: #Tidy_Parameters=/reel
0030: 0-0: #pragma compile(AutoItExecuteAllowed, true) ; for v3.3
0032: 0-0: #EndRegion ScriptOMatic - Options
0034: 0-0: Local $isAnsiStr = "", $isAdminStr = "[User]"
0036: 0-0: If IsAdmin() Then $isAdminStr = "[Admin]"
0037: 0-0: Local $sTitle = "AutoIt ScriptOMatic Tool  [2015.05.11]" & $isAnsiStr & $isAdminStr
0039: 0-0: If $CmdLine[0] > 0 Then
0050: 0-0: #Region ScriptOMatic - GUI - pre set up
0054: 0-0: Global $ini = @AppDataDir & "\ScriptOMaticForAutoIt3\ScriptOMatic.ini"
0055: 0-0: Global $sCacheFileBaseName = StringTrimRight($ini, 3) & "cache."
0056: 0-0: If FileExists(@ScriptDir & "\ScriptOMatic.ini") Then ; it"s a portable install
0061: 0-0: If Not FileExists($ini) Then $sCacheFileBaseName = @TempDir & "\ScriptOMatic.cache." ; this way, when in portable mode( and no personal .ini, just the .exe ) is a clean exit ( if so you choose to )
0062: 0-0: Global $iTab = Int(IniRead($ini, "Settings", "g_idAST_ScriptCode_Tab", "4"))
0063: 0-0: Global $sTab = tabInt2Str($iTab)
2256: 0-0:  Local $sTab = ""
2257: 0-0:  For $n = 1 To $iTab
2258: 0-0:      $sTab &= " "
2259: 0-0:  Next
2258: 0-0:      $sTab &= " "
2259: 0-0:  Next
2258: 0-0:      $sTab &= " "
2259: 0-0:  Next
2258: 0-0:      $sTab &= " "
2259: 0-0:  Next
2260: 0-0:  Return $sTab
0064: 0-0: Global $a2h_td1 = IniRead($ini, "Settings", "array2html_bg1", "bgcolor="#EAEAEA"")
0065: 0-0: Global $a2h_td2 = IniRead($ini, "Settings", "array2html_bg2", "bgcolor="#E2E2E2"") ; #0080C0  #E2E2E2
0066: 0-0: Global $sett_RemoveTempFiles = Int(IniRead($ini, "Settings", "sett_RemoveTempFiles", 0))
0067: 0-0: Global $_ArrayDisplay_Override_Topmost = Int(IniRead($ini, "Settings", "ArrayDisplay_Override_Topmost", 0))
0068: 0-0: Global $_ArrayDisplay_Override_PreferredMonitor = Int(IniRead($ini, "Settings", "ArrayDisplay_Override_PreferredMonitor", 0))
0069: 0-0: Global $sSaveFile_InitDir = IniRead($ini, "Settings", "SaveFile_InitDir", @ScriptDir)
0070: 0-0: Global $sGoogleIt = IniRead($ini, "Settings", "sGoogleIt", "https://www.google.com/search?q=wmi+%22@SelectedClass%22+example+vbs")
0071: 0-0: Global $ShowOnlyDynamicClasses = Int(IniRead($ini, "Settings", "ShowOnlyDynamicClasses", 1))
0072: 0-0: Global $iArrayDefaultLimit = Int(IniRead($ini, "Settings", "iArrayDefaultLimit", 1000))
0073: 0-0: Global $iSep = Chr(1) ; for $aRemotePCs, it will be saved to INI in a StringToBinary ( to avoid plain text snooping )
0074: 0-0: Global $aRemotePCs, $gd_ComputerName, $gd_UserName, $gd_UserPassword
0075: 0-0: loadRemotePCs()
2692: 0-0:  $aRemotePCs = IniReadSection($ini, "RemotePCs")
2693: 0-0:  If UBound($aRemotePCs) == 0 Then
2706: 0-0:      Local $n, $a, $f = 1
2707: 0-0:      $aRemotePCs[0][1] = $aRemotePCs[1][1]
2708: 0-0:      ConsoleWrite(UBound($aRemotePCs) & " , " & UBound($aRemotePCs, 2) & @CRLF)
4 , 2
2714: 0-0:      _ArrayDelete($aRemotePCs, 1)
"C:\Program Files (x86)\AutoIt3\Include\Array.au3" (346) : ==> Variable used without being declared.:
Local $iDim_1 = UBound($avArray, $UBOUND_ROWS) - 1
Local $iDim_1 = UBound($avArray, ^ ERROR
->11:23:17 AutoIt3.exe ended.rc:1
+>11:23:17 AutoIt3Wrapper Finished.
>Exit code: 1    Time: 1.335

 

[argumentum]

some CleanUp

​the #include were in the wrong place. I moved them higher up and it runs ok

[argumentum]

@mLipok , actually, you're gonna see a bunch of "; for v3.3" or "; for v3.3 start" , etc.
Those are markers for another script that weeds out one version from the other, older code.
The file that I distribute in the zip file, is the one for compatibility with the current version,
the one that I work out of, is the one for win95. In my humbly stubborn approach, the reasoning is:
  if it does not need something from a newer version, for a tool, the last version that supports the widest range
of OS's, is v3.2.12.1 and it shows to be very stable and versatile BUT, I found that is strongly preferred to focus on
the current version. So, I build the one I like for the foremention reasons and the one that will run from source on the current version.
Therefore, I will take the code you reformated and apply the concept to the code for a next version that will include the fold at the edge
of the editor, like in ScITE, and also apply that criteria to the generated code, where the fold will have good use,
.... because, honestly, the code is a mess. When I started, I just wanted arrays as an output, but obsessive as am, I did not stop there.
Now I find myself in a pickle. I'd have to rewrite the whole thing to make it do what I'd like, how I'd like, in a presentable manner.
A long speech but I wanted to tell you.
Anyways, thanks for showing me a thing or two, I appreciate it, I have no peers and all expertise that's given to me lets me grow into
a better coder. ( maybe ) =P 

[mLipok]

Ok.
If you want then I will back to this project in my free time and do some more CleanUp .

Best regards,
mLipok

[argumentum]

Ok.
If you want then I will back to this project in my free time and do some more CleanUp .

Best regards,
mLipok

​Thanks for the offer but I'll get around to do it. In so far the code is functional unless someone finds a bug.
I am going to rewrite it in a UDF like format. UDF for the Scite part and for the WMI.
The main loop should be as short and simple as possible,
Should be done maybe in a month or two.

[argumentum]

update for 2015.11.28
added a StatusBar. ( was not easy for me to resize in win10 )
fixed COM handler in generated code

updated file in the files section.

[cal]

I had no idea this had been updated.  I just stumbled on this looking for something else.  I used the original for years.  Then patched it myself when I needed to when I went to use it and discovered it was broken in the then current version of autoit.  According to the datestamp that was 2008.  I also had no idea that it now came with autoit.  Yes,  I do see it on my machine and that version I'm guessing is newer then one I've been using since I don't have a www lookup button on mine.

I'll have to bookmark this page and come back in a couple days when I have the time.  Outputs as arrays...  that sounds good.  I look forward to that and I'm very curious as what you mean redoing it as a UDF.   Do you mean I'd be able to pull data using your proposed UDF with just a couple lines to reference what I want instead of copying and modifying a couple sections of code from the tool.  If thats what you meant.... Then I eagerly await the future updates.

Thanks for the hard work.  I find it tough to go back and update my old code sometimes.  I've found myself wondering how I could have wrote such sloppy code or thinking why did I do it that way when this other way is so much better.    Doing so on someone else's code is just that much harder.