Visual Studio Code Extension currently available and future plans for SciTE?

[WildByDesign]

On 2/13/2025 at 5:40 AM, Jos said:

Uploaded an updated beta installer v25.205.1420.2 which contains an updated AutoIt3Wrapper v25.205.1420.1, where /addincludes parameter works again correctly.
I stripped out a little too much when removing the previously required "filename with special characters" support.

I'm using that exact version of the installer and confirmed that mentioned version of the wrapper and I just wanted to mention that it is still adding duplicates, at least under some circumstances. Most includes end up with two. But with #include <WinAPIInternals.au3> I end up with 3.

For all the doubles, I already had those includes in my file. So it added a second one. Same with #include <WinAPIInternals.au3> I had as well, but in that case it added 2 more so I ended up with 3.

Thank you for your efforts regarding this. I feel like it is quite valuable now with this transition to VSCode.

Edited February 14 by WildByDesign
spelling

[Jos]

1 hour ago, WildByDesign said:

On 2/13/2025 at 11:40 AM, Jos said:

Uploaded an updated beta installer v25.205.1420.2 which contains an updated AutoIt3Wrapper v25.205.1420.1, where /addincludes parameter works again correctly.
I stripped out a little too much when removing the previously required "filename with special characters" support.

I'm using that exact version of the installer and confirmed that mentioned version of the wrapper and I just wanted to mention that it is still adding duplicates, at least under some circumstances. Most includes end up with two. But with #include <WinAPIInternals.au3> I end up with 3.

I'll have a look as I can replicate it.

Edited February 14 by Jos

[Jos]

I guess I'm mixing too many different program languages these days, so goofed up pretty much with that last version.
Anyway, it should be fixed with the latest Beta installer containing an update for AutoIt3Wrapper v25.205.1420.2 ... and did test properly this time.  

[WildByDesign]

12 minutes ago, Jos said:

Anyway, it should be fixed with the latest Beta installer containing an update for AutoIt3Wrapper v25.205.1420.2 ... and did test properly this time.

Confirmed here as well. Working brilliantly in the same manner as it does with SciTE4AutoIt3. Cheers!

[Jos]

 

[donnyh13]

I was curious, when using VSCode, what processes the Macros, specifically, @ScriptDir ? While working on a LibreOffice Script I ran into a problem, which only happened when the code was ran using VSCode, not Scite. I tracked it down to the @ScriptDir Macro. In VSCode, the Drive letter is lower case, but in Scite it is uppercase. This caused something in LibreOffice to not work right when using VSCode, but to work fine in Scite, and could cause problems with other applications too? I tried both extensions, with the same result, so I'm assuming it's not the extension's fault? 

[genius257]

5 hours ago, donnyh13 said:

I tracked it down to the @ScriptDir Macro. In VSCode, the Drive letter is lower case, but in Scite it is uppercase. This caused something in LibreOffice to not work right when using VSCode, but to work fine in Scite, and could cause problems with other applications too?

Interesting. Windows path/file handling should not care, but maybe something with the underlying file/path implementation in LibreOffice?
I have not experienced issues before, but I would assume other applications that are made as cross OS compatible may have the same issue, especially if they end up using same part of a library that contains this bug/issue.

[donnyh13]

On 2/21/2025 at 3:59 PM, genius257 said:

maybe something with the underlying file/path implementation in LibreOffice?

Its possible. I haven't had time to test anything further, besides a simple FileExists (Which worked fine). So that would seem to prove your theory correct? I ran into the issue in L.O. while trying to insert an image into a Button control.

I always assumed it was AutoIt itself that filled in the macro, so this kind of surprised me, so I thought I would share.

Edit: Sorry for hijacking the thread Jos.

Edited February 23 by donnyh13

[Jos]

On 2/15/2025 at 8:53 PM, Jos said:

 

Did anybody check this out and have any comment whether this is a correct approach for VSCode to run the extra stuff not supported by the extension internally or are we all done making the changes needed for SciTE4AutoIt3 extra installer also supporting VSCode "better"?

 

 

[WildByDesign]

21 hours ago, Jos said:

Did anybody check this out and have any comment whether this is a correct approach for VSCode to run the extra stuff not supported by the extension internally or are we all done making the changes needed for SciTE4AutoIt3 extra installer also supporting VSCode "better"?

First of all, I really appreciate these extra integrations you've done between VSCode and AutoIt3Wrapper.

So for me, the autoit.aiPath variable has always automatically came up as C:\Program Files (x86)\AutoIt3\AutoIt3.exe. I have never manually configured it. The problem is that for the powershell command, it fails by trying to run C:\Program Files (x86)\AutoIt3\AutoIt3.exe/SciTE/AutoIt3Wrapper/run_autoit3wrapper.ps1.

This is default automatic settings for the Damien extension.

The terminal output error is as follows:

The argument 'C:\Program Files (x86)\AutoIt3\AutoIt3.exe/SciTE/AutoIt3Wrapper/run_autoit3wrapper.ps1' to the -File parameter does not exist. Provide the path to an existing '.ps1' file as an argument to the -File parameter.

EDIT: I was able to test it successfully by modifying both sections from:

"args": ["-File",
        "${config:autoit.aiPath}/SciTE/AutoIt3Wrapper/run_autoit3wrapper.ps1",
            "-AutoitPath", "${config:autoit.aiPath}",
            "-Options", "/addincludes",
            "-ScriptFile",  "${file}"],

To:

"args": ["-File",
                  "C:\\Program Files (x86)\\AutoIt3\\SciTE\\AutoIt3Wrapper\\run_autoit3wrapper.ps1",
                        "-AutoitPath", "C:\\Program Files (x86)\\AutoIt3\\",
                        "-Options", "/addincludes",
                        "-ScriptFile",  "${file}"],

Everything is good like this now. But we have to find a better way by default.

Is it possible to use environment variables in the task code?

Edited February 27 by WildByDesign
added more info

[WildByDesign]

Another suggestion, @Jos, would be adding the keybindings.json file as you suggested to me recently. That way the user can use the same Ctrl+Shift+Z for adding missing Includes. I am not as familiar with Au3Stripper though or whether or not the extension already has a key combo for it.

[donnyh13]

Sorry Jos. Still working on getting the basics of VSCode down, before I can do much for testing.

[SOLVE-SMART]

23 hours ago, Jos said:

Did anybody check this out and have any comment whether this is a correct approach for VSCode to run ...

Similar to @donnyh13, I had not enough time. But I try to give you @Jos feedback soon.

Best regards
Sven

[Jos]

3 hours ago, WildByDesign said:

So for me, the autoit.aiPath variable has always automatically came up as C:\Program Files (x86)\AutoIt3\AutoIt3.exe. I have never manually configured it. The problem is that for the powershell command, it fails by trying to run C:\Program Files (x86)\AutoIt3\AutoIt3.exe/SciTE/AutoIt3Wrapper/run_autoit3wrapper.ps1.

 

Not sure if there is an easy fix for that other than hard-coding the proper Path instead of using the default value, which seems to be including the autoit3.exe.
Or do you have other thoughts?

[Jos]

2 hours ago, WildByDesign said:

Another suggestion, @Jos, would be adding the keybindings.json file as you suggested to me recently.

We can also work on a proposal for the key bindings. I still haven't figured out how we can define these keybindings just for when an *.au3 file is selected, which to me sounds like that is important.

[SOLVE-SMART]

14 minutes ago, Jos said:

out how we can define these keybindings just for when an *.au3 file is selected

Hi @Jos,

you can set editorLangId as the "when" value in the keybindings.json file. For example to comment-in / comment-out a line only for javascript, it would look like this:

{
    "key": "ctrl+numpad1",
    "command": "editor.action.commentLine",
    "when": "editorTextFocus && !editorReadonly && editorLangId == 'javascript'"
}

CTRL+Numpad1 will comment-in/out for JS, but not for all other languages. So you can use another shortcut for other languages too ... etc.

I hope this is what you're looking for 🤝 ?

Best regards
Sven

[Jos]

33 minutes ago, SOLVE-SMART said:

I hope this is what you're looking for 🤝 ?

Yes & No 🙂

Thanks, but I was a little confused as I had that already in my earlier post on keybindings.json and just got confused with tasks.json am was looking at to see it there is a simple fix for the aiPath.
I also would like that the AutoIt3 specific tasks are only shown when editing an AutoIt3 file.

[WildByDesign]

1 hour ago, Jos said:

Or do you have other thoughts?

It might be good to add your own variables with the installer and those variables could be independent of either extension.

From my understanding, in order for tasks.json to use any variables, they must first be written to the settings.json file. So you could create separate variables for AutoIt directory, the wrapper, etc.

Edited February 27 by WildByDesign
Typo

[donnyh13]

4 hours ago, WildByDesign said:

Is it possible to use environment variables in the task code

It seems so.

https://code.visualstudio.com/docs/reference/variables-reference#_environment-variables

 

[Jos]

I prefer not to go down that road as some use autoit & scite+utilities portable, in which case there are no existing  env variables for the location of the scite directory.

Edited February 27 by Jos