Dbug - another debugger for AutoIt 2018.05.24

Hi, 
i'v just uploaded my latest project: Simple Snippet Manager to the Downloads. area :

 

 The intended usage is to select a Snippet, and to copy it's contents into your favorite Editor.
    The Copy/Paste process happens over the (windows)Clipboard. 
    The previous clipboard content is not restored.
    There is a time limit of 60 seconds, in which the pasting of the text is allowed (starting when the App window gets inactive).  
    The Hotkey is reenabled, when the main Window is activated.
    
    This is a File/Folder based manager. 
    The App is configured to hold 4000 files and 400 folders with searching depth of 5 sub-folders.
    
    The root folder is freely selectable, but it  should be a Folder with writing permission.
    Please install the App in a folder with Writing permission, too. 
    This App only uses an .ini file to save it's configuration, which has to be in the same folder as the App.
    
First configuration:
1. Open the config Window.
2. Enter the Language name, create or seek a root folder, enter an extension.
3. Click on Set button.
4. Click on the Exit button.
The Language configuration is done, adding files or folders are needed:
 1. Select the language from the dropbox list, and click on Get Lang button.
2a. Right Click on the root folder, chose New folder to add categories.
2b. or chose New/Edit file to open the builtin text editor
 3. Paste or Write a snippet-code, enter a filename and save it.
 
 (Repeat the 3. as needed)
 
Usage:
Select a language, then click on Get Lang button.
Choose a file with the left mouse button.
Check if the code was loaded in the Textarea at the bottom.
Switch to your Sourcecode editor, and press the Hotkey (default= Ctrl/Strg b) to copy and paste the text.
There is a time limit of 60 seconds, after the main window gets inactive, in which the copy&pasting is allowed.
Changelog:
V1.02        (24.06.2020)
            Addition: Undocumented ini setting: StartLoadLastUsedLanguage
                      Setting this to 1 (default value) will now reload the Last used language at start.
                      Last used language counts for the Language, selected with [Get Lang] button. The [Config] button will delete the last used language.
                      LastUsedLanguageNr, LastUsedLanguageName ini settings are used internaly for the above function.
             Added version string to the main Window title.
V1.01        (23.06.2020)
            Bugfix    : Starting the App without the ini file now sets the correct starting Hotkey (Ctrl b)
            Addition: Clipboard is saved, before pasting, and restored after pasting. (May work with text data only. p.s. untested!)

Simple Snippet Manager (AutoIt v3.3.14.5)
 The intended usage is to select a Snippet, and to copy it's contents into your favorite Editor.
    The Copy/Paste process happens over the (windows)Clipboard. 
    The previous clipboard content is not restored.
    There is a time limit of 60 seconds, in which the pasting of the text is allowed (starting when the App window gets inactive).  
    The Hotkey is reenabled, when the main Window is activated.
    
    This is a File/Folder based manager. 
    The App is configured to hold 4000 files and 400 folders with searching depth of 5 sub-folders.
    
    The root folder is freely selectable, but it  should be a Folder with writing permission.
    Please install the App in a folder with Writing permission, too. 
    This App only uses an .ini file to save it's configuration, which has to be in the same folder as the App.
    
First configuration:
1. Open the config Window.
2. Enter the Language name, create or seek a root folder, enter an extension.
3. Click on Set button.
4. Click on the Exit button.
The Language configuration is done, adding files or folders are needed:
 1. Select the language from the dropbox list, and click on Get Lang button.
2a. Right Click on the root folder, chose New folder to add categories.
2b. or chose New/Edit file to open the builtin text editor
 3. Paste or Write a snippet-code, enter a filename and save it.
 
 (Repeat the 3. as needed)
 
Usage:
Select a language, then click on Get Lang button.
Choose a file with the left mouse button.
Check if the code was loaded in the Textarea at the bottom.
Switch to your sourcecode editor, and press the Hotkey (default= Ctrl/Strg b) to copy and paste the text.
There is a timelimit of 60 seconds, after the main window gets inactive, in which the copy&pasting is allowed.
 
The Download includes:
32 + 64bit exe, sourcecode, icon, read me text and 2 Instructional Helpfiles in Html and PDF format.

Hi everyone!

I'm using AutoIt for several years now and I really get the hang of it!
I'm quite the curious OCD perfectionist kind of guy, so I can't help wondering..
what would be the best way to program stuff for the compiler / interpreter / scripting engine?
We're talking about the inner workings of the AutoIt's core here, and how to give it as less friction as possible but also take care of the machine running the script.
For example,
Imagine a script where we would constantly have to assign a Boolean value to a variable:
; A: local $bool = false $bool = true $bool = true $bool = false ; B: local $bool = false check(true) check(true) check(false) func check($b) if $bool = $b then return $bool = $b endfunc In this case, would it be better to just overwrite (A) the variable or first check if we really need to (B)?
What would be best for the computers memory if it had to do this for a year non stop?
Another example, imagine you're writing a function with an if statement.
If you would look under the hood of AutoIt, what would be the best way to give your computer as less work / code nesting stack filling as possible:
; A: func decide($b_Input) if $b_Input then ;do something else ;do something else endif endfunc ; B: func decide($b_Input) if $b_Input then ;do something return endif ;do something else endfunc Last one for now:
; A: while 1 ; do stuff wend ; B: while true ; do stuff wend Isn't AutoIt taking an extra step in converting 1 to a Boolean in example (A)?
Or is it the other way around and does the (B) way make AutoIt first convert a keyword (true or false) to a numerical value (0 or 1).
I think this kinda detail stuff is quite interesting, makes me wonder how AutoIt converts and runs our code.
What are your opinions on this topic?
Any coders who know more about the inner workings of AutoIt?
Any people like me who ask themselves similar questions (with examples)?

Let me know! 😉

First I would just like to say HELLO! to anyone reading. It has been a while since I've posted to the Forums but I'm always crawling around.
Now to the matter at hand. I have been looking high and low for a simplistic answer my burned out brain can find but to no avail. I've only recently upped my AutoIt skill and only by a little bit such as ordering my script neatly with my own UDFs and using Global/Dim more often to make my GUI creation understandable and easy to keep things orderly. My current problem however is figuring out how to make my newest endeavor work which is my own "Debugger". I've made a GUI with an Edit Control to display what my Variables are holding and other information from a concurrently running Script. I have access to all of the scripts I'm attempting to connect but I'm dumbfounded on how I would separately read variable information from one running script into another. I'll provide my "Debugger" script that I want to read variables into and a "Meta Script" I'd want to pass info from.
#Region Include Files #include <AutoItConstants.au3> #include <GUIConstantsEx.au3> #include <WindowsConstants.au3> #include <ColorConstantS.au3> #EndRegion #Region AutoIt Options ;Opt("TrayAutoPause", 0) ;Opt("TrayMenuMode", 3) #EndRegion #Region Hotkeys HotKeySet("{ESC}", "ExitProgram") HotKeySet("{PGDN}", "PauseProgram") HotKeySet("!1", "Snippet_1") HotKeySet("!2", "Snippet_2") HotKeySet("!3", "Snippet_3") HotKeySet("!4", "Snippet_4") HotKeySet("!5", "Snippet_5") HotKeySet("!6", "Snippet_6") HotKeySet("!7", "Snippet_7") HotKeySet("!8", "Snippet_8") HotKeySet("!9", "Snippet_9") #EndRegion #Region Global Variables #Region Globals Global $gMain, $ctrlEdit ;, $gParent #EndRegion #Region $gMain Params Dim $gMainW = @DesktopWidth / 2 Dim $gMainH = @DesktopHeight / 2 Dim $gMainX = (@DesktopWidth / 2) - ($gMainW / 2) Dim $gMainY = (@DesktopHeight / 2) - ($gMainH / 2) Dim $gMainStyle = $WS_POPUP Dim $gMainStyleEx = -1 ;Dim $gMainParent = $gParent #EndRegion #Region $ctrlEdit Params Dim $ctrlEditW = Round($gMainW * 0.98) Dim $ctrlEditH = Round($gMainH * 0.98) Dim $ctrlEditX = ($gMainW - $ctrlEditW) / 2 Dim $ctrlEditY = ($gMainH - $ctrlEditH) / 2 Dim $ctrlEditStyle = -1 Dim $ctrlEditStyleEx = -1 #EndRegion #EndRegion #Region GUI Initialization ;$gParent = GUICreate("", -1, -1, -1, -1, -1, $WS_EX_TOOLWINDOW) $gMain = GUICreate("", $gMainW, $gMainH, $gMainX, $gMainY, $gMainStyle, $gMainStyleEx) GUISetBkColor($COLOR_BLACK, $gMain) $ctrlEdit = GUICtrlCreateEdit("MainW: " & $gMainW & @CRLF & "MainH: " & $gMainH & @CRLF & "EditW: " & $ctrlEditW & @CRLF & "EditH: " & $ctrlEditH, $ctrlEditX, $ctrlEditY, $ctrlEditW, $ctrlEditH, $ctrlEditStyle, $ctrlEditStyleEx) GUISetState(@SW_SHOW, $gMain) #EndRegion MainFunction() #Region Main Function (GUI) Func MainFunction() While 1 $msg = GUIGetMsg() If $msg = $GUI_EVENT_CLOSE Then Exit EndIf WEnd EndFunc #EndRegion #Region Functions Func Functions() EndFunc #EndRegion #Region Program 1 Func Snippet_1() EndFunc #EndRegion #Region Program 2 Func Snippet_2() EndFunc #EndRegion #Region Program 3 Func Snippet_3() EndFunc #EndRegion #Region Program 4 Func Snippet_4() EndFunc #EndRegion #Region Program 5 Func Snippet_5() EndFunc #EndRegion #Region Program 6 Func Snippet_6() EndFunc #EndRegion #Region Program 7 Func Snippet_7() EndFunc #EndRegion #Region Program 8 Func Snippet_8() EndFunc #EndRegion #Region Program 9 Func Snippet_9() EndFunc #EndRegion #Region Pause/Exit Functions Func PauseProgram() While 1 Sleep(1000) WEnd EndFunc Func ExitProgram() Exit EndFunc #EndRegion Pause/Exit Functions #Region Snippets #CS #CE #EndRegion #Region Other Information #CS #CE #EndRegion That's the Debugger script. Please forgive anything ignorant but point it out if you will, I'll take any pointers to get better! (I usually use a Select to get $GUI_EVENT_CLOSE but this is early on)
Now if I made another script with a basic GUI similar to this and wanted to read say the GUI Width ($gMainW) into the Debugger Edit Control could I do it? If so, could I do it for every variable I have in a script? I read something about the Run function and adding the variables as an option parameter I believe which I think I could do with an array to keep it from being super long and ugly but would that be the only way to do this? Any information is going to be appreciated and thank you in advance for your time!
 
Edit: Sadly it just dawned on me that I could make a UDF that will create a child window that will do this instead of having a separate script trying to invade another... I'll still be keeping an eye on this for any comments but I apologize if I wasted your time!

Here's a new version of my Dump.au3 file (dirty). I've recently added support to dissect (dump) as a treeview-like view any string in the variable conforming to a strict JSON grammar, whereever said string is: as a standalone string variable or in an array or a map. AFAICT the only relaxed constraint not implemented here is that numbers in parsed JSON may have leading zeroes, although leading zeroes are forbidden in pure JSON specifications. If required it wouldn't be hard to add this constraint.
@c.haslam (among others) may find it useful. Use freely.
Dump.au3