AHK Portable Installer v1.29

[TheArkive]

@hoppfrosch
Ok, are you up for trying the script version so we can pinpoint the problem?

If so, download the master.zip from the repository, unzip, and copy AHK v2 U64 EXE into the script folder and rename to AHK Portable Installer.exe.

If it runs, then we can insert msgbox entries to try and find the error...

EDIT: I'm trying to recreate the problem... no luck yet

[hoppfrosch]

What I just noticed:

Within "AHK Portable Installer U64.exe", above the list where the available AHK versions should be listed there is a message "Registry mismatch" - don't know what this means or whats the impact ...

[hoppfrosch]

Which AHK v2 U64 exe-version? a108?

Edit: Ok, did as you said (downloaded master.zip .... renamed exe ... started) using V2a108

Same behaviour with error

[TheArkive]

@hoppfrosch
The "Registry Mismatch!" is only a way to show that AHK is not installed.

Yes AHK v2 a108.

And what version of windows do you use?

[hoppfrosch]

Using MS Windows 10 Enterprise, Build 16299

----

Edit: we finally figured it out - the problem is caused by different language/localization of OS

[TheArkive]

Changes:

• FIXED: can't set base folder when running on system with locale NOT set to English due to error

[hoppfrosch]

Works now independent of locale

[TheArkive]

@hoppfrosch
awesome! thanks for your help

[TheArkive]

Update 2020/04/19

• Added my own version of the WTFPL license. I just want to prevent some troll from attempting to being a turd of a human.

• changed storage to JSON, added library file for JSON

• removed XML library file, XML code is commented out

NOTE: This release offers no functional updates or improvements. This is just a framework adjustment for going forward. If you do upgrade, you must redefine your settings in the program. There shouldn't be any need to uninstall / reinstall AHK if you choose to implement this upgrade. Just copy over, overwrite, and redefine your settings. There's no need to keep the `Settings.xml` file.

[TheArkive]

Update 2020/05/01

Big changes! Please re-read the README on github if you have issues, or post an issue ... here we go:

• AutoHotkey_H and compiler fully supported now

• no more need to rename .bin files, or AHK_H EXE files

• AHK Launcher updated to allow unlimited parallel version of AutoHotkey in Extras tab

• user specifies AHK version, first-line match string, and associated EXE to run on match in Extras tab

• appending AHK version to the end of the script file no longer supported

• included .ahk templates changed to include AHK v1 and v2 lines, all commented out

• user can still define different custom templates for v1 and v2 if desired

• fixed several small bugs on startup and when an invalid EXE is specified to run a script

• improved code to uninstall AHK registry entries, external .reg file no longer needed

• main EXE now only compiled as 32-bit, writes to 64-bit registry on 64-bit systems

Please post bugs!

[TheArkive]

Instructions to add AHK v2 a109

Implementing the latest version of AHK v2 a109 is really easy with AHK Portable Installer. Just download and unzip to the folder specified in the Basics tab. Make sure AHK v2 a109 is contained in its own folder. Also copy WindowSpy.ahk in there as well.

a) On the Extras tab, simply double-click the version of AHK you want to "upgrade" (red arrows)

b) Change the EXE in the popup window (yellow arrow)

c) OPTIONAL: If you want the latest version of AHK v2 a109 to be the default for your system, just double click your preferred version in the main EXE list (blue arrow)

Annotation 2020-05-27 144005.png (52.29 KiB) Viewed 5220 times

Please pardon the crazy windows theme I use. It looks different, but functions the same.

If you end up having questions please please ask in this thread.

[vvhitevvizard]

@TheArkive

; AHKv# as line 1 in the script

just a suggestion: I find myself using slightly different first line commentary. And other ppl scripts might differ from each other, too.
Make the search more fuzzy, try to find any: ";" any symbols "AHK" whitespace separator(s) whitespace "v" "1|2" within 1st line:

Code: Select all

if (s ~= "^;.*AHK[ \t:_,.!>=-]+[vV][12]")

or

Code: Select all

regexmatch(s, "^;.*AHK[ \t:_,.!>=-]?[vV]([12])", m)
if (m[1]=="2")
 ...
if (m[1]=="1")
 ...

[TheArkive]

@vvhitevvizard
The user defines the regex match in every case. So they can make it as fuzzy as they want. Or they can set the settings (per EXE) to to be an exact match.

[vvhitevvizard]

@TheArkive

Also there might be new preprocessor command https://github.com/Lexikos/AutoHotkey_L-Docs/commit/3495cace587e3be99516c656f624be2676bdd6e5
So the regex would be something like:
#requires\sAutohotkey\s[vV]?(\d+)(?:\.\d+)?
and u gotta search some reasonable # of lines (first 4096 bytes or something), not only the first line.

PS: I, for one, don't use ur script tho - I prefer Total Commander's stuff.

[TheArkive]

u gotta search some reasonable # of lines (first 4096 bytes or something), not only the first line.

Why? I needs to be standardized for simplicity. It's not like you can change AHK code version part way through the script file...

[vvhitevvizard]

@TheArkive
Well, its kinda impossible to edit all the scripts... especially written by other ppl... So u have to find ways of using fuzzy logic.
AHK preprocessor's commands don't have to follow some order, #requires doesn't have to be in the 1st line of the script...
ofc I'm talking of ur script being future-proof. A user might rewrite all his/her scripts to strictly follow some rules helping to identify its desired AHK version(s).

[TheArkive]

Well, its kinda impossible to edit all the scripts....

I don't follow... If you have AHK v2 installed on your system, and you want to run AHK v1, then you simply add any variation of ; AHK v1 to line 1 (check regex settings for specifics - modify them any way you like). If the script ever worked at all in any context, it should work in the context of using this program, assuming the settings are properly configured to point to the proper EXE.

[vvhitevvizard]

What if u get some scripts to assess (to run them and test) written by other ppl? Consider ppl start using #requires preprocessor directive soon.

In other words, ur tool requires a user to re-edit scripts. I'm talking of ur script to analyze a script to be run a bit deeper: u might even start parsing some commands to get an idea whether it requires AHK v2 or v1.

[TheArkive]

ofc I'm talking of ur script being future-proof. A user might rewrite all his/her scripts to strictly follow some rules helping to identify its desired AHK version(s).

By requiring the first line to be this type of comment, I'm attempting to ensure that the user adds such a comment intentionally. Rather than adding ; AHK v# in some other part of the script, simply meaning to only identify a single part of the script meant for a particular version of AHK. If the AHK language suddenly requires a specific command to be on line 1 of the script document, the I'll figure that out when it happens. Until then, it won't matter, because previously configured AHK EXEs, running scripts of those versions will still function just fine.

[TheArkive]

@vvhitevvizard
I think you may be confused about how this script functions. I checked the docs you linked to. If people start using #requires, that won't affect how this program functions. It's up to the user to understand what version of AHK to configure for each script they run.