Leaderboard

Current Beta should add Include files required by the Master script, ignoring when they are included through an Include file. This is cleaner and less dependent on possible changes in the Includes.

No issue, so we would want Tidy to respect that when not ran from SciTE. I have uploaded a Beta version that checks how the program is shelled and will Indent linecomments when not ran from SciTE.

All, I see that there are multiple efforts to create/maintain an AutoIt3 Visual Studio Code extension, and I would like to open a discussion to see how that can be streamlined/merged/done more effectively so we can come up with the one that's preferred. I have been toying with the idea to stop the development of all the LUA extra's used by SciTE and start using VSCode for the more advanced way of developing AutoIt3 scripts, as many things a way after when the extension supports it, like running au3check on save so you just click the problems tab to see the warnings/errors of the currently opened scripts. So I have been working on making the utilities packaged with SciTE4AutoIt3 suitable to run stand-alone without the need for wrapping them with AutoIt3Wrapper, with the plan to be able to make them all more generic usable for any editor. They need to support UTF8 & ANSI encoded files, even when through includes the encoding is mixed. I have modified AutoIt3Wrapper to stop renaming and changing encoding of script/include files, and updated Tidy/Au3check/Au3stripper to support special characters in filenames and mixed ANSI/UTF8 file encoding and the generated console output is UTF8. I have been toying a bit with the VSCODE extension maintained by Damian (just picked one without looking at any others) and made some modifications locally for testing. Run au3check (Ctrl+F5), Tidy (Ctrl+t), Au3Stripper (Ctrl+Shift+o) without using AutoIt3Wrapper. Other already standardly available option (Run/Compile) still run via AutoIt3Wrapper as there is an added value doing it that way. I really like what I see and think this is a good way forward. So... I like to hear how you all think about this and possibly your preferred VSCode autoIt3 extension with reasons why. Also feels as a waste of effort when so many are making their own version of an extension instead of bundling the effort making one really nice one with all required features. Thoughts/Opinions?

I update SciTE w/newer beta files with this script so otherwise it brakes my automation 😅

Thanks... fixed in Beta downloads, but is really not needed to download as the installer only updates au3check.exe to support the mixed encoding, but will use the available au3check.dat.

The new Au3Check.dat is missing data ( Maps, SetExitCode, etc. ) Fixed

So another vscode extension for the AutoIt language emerges! I've tried the existing ones, and found small problems that i felt i could improve on, but it would require an entire new approach to the inner working of the existing extensions. Also working on a complete AutoIt3 parser a vscode extension just made sense Any feedback is appreciated, and i hope this project will benefit more than just me 🤡 Visual Studio Code Marketplace GitHub repo Some of the current features: Basic AutoIt2 syntax highlighting, for fun 🤡 AutoIt3 syntax highlighting Variable/Function hover gives declaration information if available. Goto declaration #include links Syntax checking, as you type Function signature help Function and variable list in a file via the outline tab. Works on desktop (any OS) and web version ⚠️ The parser used is not yet 100% complete (see issues for know problems), and the last thing to be implemented is the With code block. Hope you like 😃

I'm a dummy, I thought I was using your extension! I am now though .. I'll let you know how it goes!

I agree 100%. And that is probably the way that I have learned the most at every aspect of life. Taking things apart, breaking things and figuring it out later. I will definitely read that Best coding practices tonight. Cheers!

... today I was telling a neighbor about a project her husband was doing and told her about material aging and fatigue but that I don't correct people that much anymore because with time they end up learning and doing, one failure at the time The WiKi as this "Best coding practices" and is a good read. The way that I lean a lot is reading and messing with the UDFs that come with AutoIt. Still I read old code of mine and ask myself "why ?, why this way !" because with time I learned to better structure code. The kind of thing that people like @Nine say. Your current version is functional and that is good. If you code it as if it was to be a UDF that you later add a GUI to, better

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.

Uploaded a new beta version with several changes to how special ANSI characters are detected and any master or include file containing ANSI characters will be converted to UTF8.