Leaderboard

The first post has been updated with version 0.9.6. This was a monster of an update. I had to rewrite the majority of how everything worked, new functions, etc. to allow for individual per-app and per-class custom rules. I spent a few days testing it and had to iron out a few bugs, particularly with special handling of apps likes Terminal, VSCode, etc. Now we can have different colored borders for different apps, different titlebar colors, blur behind on some apps and mica extended to client area on other apps. It's kind of like of buffet now. Needless to say, I am sure a few more bugs will pop up because almost everything changed. Please start with the new config file as well because a lot was changed and/or removed. There is also another example config file included which shows some examples and ideas.

I don't know which words to use because the translator changes them. I'm using the wm_command command to type two edits at the same time, but when I click on $Edit1, it automatically sends the text to $Edit2. And I would like it to send the text only after I edit something. I think the EN_CHANGE command does this, but I didn't know how to use it in AutoIT. The way iao747 sent it worked partially. If there is already some text in $Edit1, it automatically sends it to $Edit2. I hope I understood. Edit: with a little research I ended up getting it. If _WinAPI_HiWord($wParam) = $EN_CHANGE Then GUICtrlSetData($Edit2, GUICtrlRead($Edit1)) EndIf

Hi @seadoggie01! Thanks for the heads up! This is due to the incomplete parser. Currently With...EndWith blocks are not supported. Anything inside the block will fail, since i haven't added any rules to it yet. The reason is that EVERY rule needs to be copied with the small change, that ".property" is a valid syntax within that or child code blocks. It is low priority, since With...EndWith is rarely seen used, but will be supported in the future at some point (depending on how urgent it is). That's an interesting bug! From quick testing, the issue seems to be caused by the empty line in the remarks: ; Remarks .......: Use like: _Acro_DocBookmarkProperties($oBookmark) to get an array of values ; ; Default means values won't be changed. My guess is some of my code is stuck in an infinite loop... I will look into it and fix it soon, since it can deadlock the extension. "Legacy" documentation blocks was implemented quick, since I'm trying to move towards the more cross language familiar docBlock syntax, but that still does not mean the code should fail this spectacularly😅 >Developer: Reload Window Should be your solution. It's not great, but faster than restarting the entire application 😉 Thank you for the kind words and the bug reporting! 😄 Edit: found the line causing problems with the function documentation: https://github.com/genius257/vscode-autoit/blob/0f1bb89f8af77ee7a005d1d5a9da429e5f344700/server/src/autoit/docBlock/DocBlockFactory.ts#L84 It's my regular expression to test if the content matches the UDF documentation format. It causes catastrophic backtracking, never getting past that regex check. Prevention in JS seems to time a new worker, child-process or a regex library, from a quick google search... I don't want to do any of that currently, so I've updated the regex, so it no longer has issues with your example, and if my test parses, I will push the change, and hope this issue does not come back 😜