AutoHotkey Community

TAC109

neogna2 I can’t see that it matters which order the items are presented to the callback function. In any case the offset parameter can be used to determine this. I prefer not to use a callback function as it has a noticeable detrimental effect on the efficiency of the sort except for a trivially sh...

TAC109

Try adding extra single quotes around the parameter.
Run('"D:\phone stuff\scrcpy\example.vbs"')

Edit: As Boiler said!

Cheers

TAC109

This is because cmd.exe (the batch file interpreter) doesn’t understand UTF8. (It partially understands an early version of UTF16.) However it can’t be updated by Microsoft without potentially breaking the millions of batch scripts out there.

Cheers

TAC109

I'm happy to leave it that way as a 'safety net' for any future v1 scripts I may create, but as it's superfluous to include BOM for v2 scripts, shouldn't there be a settings option in Dash for the preference to include it or not - can it be assumed that a v2 BOM won't incur a performance hit? The p...

TAC109

Looking at the error message, the word ‘AutoHotkey' may have been left out of the '#Requires' directive in the failing script.

Cheers

TAC109

Update - 1.1.37.01b, 21 August 2023

Fix: compile of new .exe failed in 1.1.37.01a.

See this post for download details.

TAC109

Update - 1.1.37.01a, 20 August 2023

Avoid copying compiled .exe permissions from temp.
Fix 'Save script as' when Base compiler directive selected.
Local help now shows v2 if Base compiler directive selected.

See this post for download details.

TAC109

red12sin Can you check that you have copied and pasted the compiler directives correctly into your script. If you past them here from your script I can double-check them as well. Edit: It looks like the two ;@Ahk2Exe-Obey compiler directives further up weren’t executed properly. Could you check the...

TAC109

lexikos wrote: ↑
13 Aug 2023, 21:46
The launcher supports versions that predate #Requires.

I’m sure it does, although I can’t see what that has to do with behaving differently depending on whether ; or /*..*/ characters are used to comment out directives.

Cheers

TAC109

UX Launcher ignores multi-line comment characters around #Requires when both v1 + v2 are installed. /* ;#Requires AutoHotkey v2.0 */ v1 := "v2" MsgBox v1 When this code is run, the launcher asks for the version of AutoHotkey to run, as expected. If the ; is removed from the start of line 2, the laun...

TAC109

I hope I’m not stating the obvious, but you could adjust the path by checking A_IsCompiled and substituting A_ScriptFullPath in place of A_LineFile. Or perhaps I’m not understanding the question properly…

Cheers

TAC109

Using FileInstall is certainly simpler and more straightforward, especially if the embedded files are to be accessed by a runwait executable.

Cheers

TAC109

I would suggest that you should uninstall your existing V2 and v1 AutoHotkey, then reinstall v1 followed by v2. This will ensure that the installation is correct.

Edit: Install into the offered directory.
Cheers

TAC109

It would help if you could post a screen shot of Ahk2Exe with the failing message.

Edit: In addition you should select a v2 base file (which should be present in the dropdown). Anyway, the screenshots should help me diagnose the problem.

Cheers

TAC109

When DOS commands are separated with '&&' it means 'only do the second command if the first command is successful'. To do the second command regardless, just use a single '&' to separate them. To complete the picture, if commands are separated by '||' this means 'only do the second command if the fi...

TAC109

If there are files/directories in the 'IndexLinked' directory, use ‘rmdir /s ' to delete these files/directories as well as the top level directory itself.

Cheers

TAC109

That's what I figured…

TAC109

In the situation when AutoHotkey v1 is installed (including the compiler), then v2 is installed, the Start menu item for Ahk2Exe is removed and not created again even though Ahk2Exe is still present, having been installed with v1.

TAC109

Update - 1.1.37.00a, 05 July 2023

Ahk2Exe: Add sub-version check for base file *.exe allowed. (Compile v2.1 scripts correctly.)

See this post for download details.

Edit: Fixed link In first post.

TAC109

Update - 1.1.37.00a, 05 July 2023

Ahk2Exe: Add sub-version check for base file *.exe allowed. (Compile v2.1 scripts correctly.)

See this post for download details.

Search found 1129 matches

Re: (default) alphabetical Sort oversight ?

Re: Run() doesn't run my SCRCPY .vbs

Re: To BOM or not to BOM?

Re: To BOM or not to BOM?

Re: about V1->V2 and a script with strange behavior

Re: Upcoming Ahk2Exe Changes (2023)

Re: Upcoming Ahk2Exe Changes (2023)

Re: ScriptGuard: Helps Protect Compiled Scripts from Decompilation

Re: UX Launcher ignores multi-line comments around #Requires

UX Launcher ignores multi-line comments around #Requires

Re: How to properly create a library that loads a dll file to account for compiling.

Re: Embedding files in a compiled script and using them without extracting them

Re: Error when trying to compile a v2 script

Re: Error when trying to compile a v2 script

Re: RUN WAIT A_comspec stops execution

Re: RUN WAIT A_comspec stops execution

Re: Ahk2Exe Start Menu Shortcut Missing, v1 + v2 Topic is solved

Ahk2Exe Start Menu Shortcut Missing, v1 + v2 Topic is solved

Re: Upcoming Ahk2Exe Changes (2023)

Re: Upcoming Ahk2Exe Changes (2023)