Page 32 of 32

Re: Upcoming Ahk2Exe Changes (2023)

Posted: 19 Aug 2023, 20:23
by 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.

Re: Upcoming Ahk2Exe Changes (2023)

Posted: 20 Aug 2023, 23:59
by 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.

Re: Upcoming Ahk2Exe Changes (2023)

Posted: 29 Sep 2023, 21:53
by TAC109
Update - 1.1.37.01c, 30 September 2023
  • Fix Base compiler directive not fully expanding built-in variables.
  • Fix "Save script as' for v1 & v2.
  • Add diagnostics to 'Syntax check' error message.
See this post for download details.

Re: Upcoming Ahk2Exe Changes (2023)

Posted: 17 Nov 2023, 13:47
by mslonik
Hi,

I suppose something is still wrong with Directive

Code: Select all

;@Ahk2Exe-Base [Path\]Name [, [Exe_path\][Name], Codepage]
.
1.1.37.01c, 30 September 2023
Fix Base compiler directive not fully expanding built-in variables.
Confirmed, it works.

But if user defined variable is used within this directive, in particular in section

Code: Select all

[Exe_path\][Name]
then it is not interpreted. For example variable

Code: Select all

%U_Filename%
is literally added to executable filename (executable filename contains literally string %U_Filename%).

Kind regards, mslonik (🐘)

Re: Upcoming Ahk2Exe Changes (2023)

Posted: 17 Nov 2023, 22:31
by TAC109
Unfortunately, because the Base directive is handled at an earlier stage of the compilation process, there is a limit to the kind of replacements that can be used. This note for the previous parameter also applies to the parameter you are having problems with:
Any use of built-in variable replacements must only be from group 1 above.
You could maybe use the ExeName directive instead.

Cheers

Re: Upcoming Ahk2Exe Changes (2024)

Posted: 11 Feb 2024, 18:55
by TAC109
Update - 1.1.37.01c0, 12 February 2024
  • Rationalise detection of major AHK version.
  • Enhance for MS Store version.
See this post for download details.

Re: Upcoming Ahk2Exe Changes (2024)

Posted: 15 Mar 2024, 20:13
by TAC109
Update 1.1.37.01c1, 16 March 2024
  • Send parameter errors to stdout/stderr if in /Silent mode.
  • Prevent compression when compiling Ahk2Exe.
See this post for download details.

Re: Upcoming Ahk2Exe Changes (2024)

Posted: 16 May 2024, 19:41
by TAC109
Update - 1.1.37.02a0, 17 May 2024
  • Get Mpress more reliably in the Updater.
  • Fix addition of new base file in the GUI.
See this post for download details.

Re: Upcoming Ahk2Exe Changes (2024)

Posted: 16 May 2024, 22:30
by JoeWinograd
TAC109 wrote:Get Mpress more reliably in the Updater.
Hi TAC,
Just to confirm...it works! Before, it shows MPRESS as Offline:

update with 1.1.37.01c1.png
update with 1.1.37.01c1.png (11.55 KiB) Viewed 450 times

After, it shows MPRESS as Up-to-date:

fixed mpress update.png
fixed mpress update.png (11.33 KiB) Viewed 450 times

Thanks very much...nice fix! Regards, Joe

Re: Upcoming Ahk2Exe Changes (2024)

Posted: 16 May 2024, 23:30
by TAC109
Thanks @JoeWinograd.

I have set up an Mpress binary release on GitHub and now download it from there to avoid the recent problems with the AutoHotkey web site.

Cheers

Re: Upcoming Ahk2Exe Changes (2024)

Posted: 17 May 2024, 00:49
by JoeWinograd
TAC109 wrote:I have set up an Mpress binary release on GitHub and now download it from there to avoid the recent problems with the AutoHotkey web site.
Great idea! The AutoHotkey web site downloads (via UrlDownloadToFile in V1 and Download in V2) are still not working, as of a few minutes ago. For anyone not familiar with the problem, it is being discussed at this forum thread. Cheers, Joe