AutoHotkey Community

Is there a process for uninstalling a specific v2 version? I had like 6 of them in the install directory and really just need the latest. Running the uninstaller from Control Panel removed all v2 versions. That was fine because I had yet to install beta.10 but was curious for in the future.

kczx3 wrote: ↑

28 Sep 2022, 08:49

Is there a process for uninstalling a specific v2 version? I had like 6 of them in the install directory and really just need the latest. Running the uninstaller from Control Panel removed all v2 versions. That was fine because I had yet to install beta.10 but was curious for in the future.

Same here.

If it wasn't you, I was probably going to ask this sooner or later because the dash is starting to look funny too.

It is adequate to delete the corresponding "v" folder(s) for now.

I am planning to do more work on the (un)installer soon.

Perfect, thanks!

Regarding the launcher and ambiguous scripts, an option (checkbox?) to have the launcher prepend #Requires to the top of the launched script file could be a nice comfort feature.

@Tensai I don't like the idea of the launcher modifying scripts, but if someone implements it in a way that is a clear improvement over the current simple Menu, and submits a pull request, I would consider merging it.

Is there random lag when bringing up the menu? It seems to happen most often when the first script is run and can even delay for up to 3 seconds.

I have noticed that myself, although at first I thought it was an issue with one particular script I run often via a hotkey (always running with v1, never showing the menu). I haven't confirmed the cause yet, but I suspect it is due to how the launcher scans for interpreters, reading each exe to identify its version. I suppose that once the directory index and interpreters are in the file system cache (managed by the OS), there is no delay. Antivirus software might contribute to the delay. I intend to optimize it by caching a list of installed interpreter paths and versions.

Removing obsolete versions would probably reduce the delay.

I confirmed that the cause of the delay on my system was Windows Defender. The additional delay is about 3 seconds (with 9 versions installed).

The disk/file system cache makes negligible difference on my system. In a VM without antivirus, stored on a mechanical hard drive, scanning for interpreters takes about 70ms the first time, then maybe 30ms. Outside of the VM, it's usually too fast to measure with A_TickCount.

@lexikos I have just checked out the uninstaller in the Beta.11 UX. One thing I noticed is that the GUI seems to show a summarised list of version numbers of all .exe's found. This includes the version numbers of non AutoHotkey files such as Mpress.exe, UPX.exe, and BinMod.exe. Perhaps these could be suppressed from the listing as I’m sure the presence of these numbers could be confusing for some users. (If any of these files need to be uninstalled, this is provided for in Ahk2Exe's 'Check for Updates' window.)

Cheers

The install and uninstall scripts currently don't properly account for unexpected modifications to installed-files.csv. They expect this file to only list files that are actually part of an AutoHotkey installation.

lexikos wrote: ↑

04 Oct 2022, 22:42

This was discussed up thread, and I implemented the suggestion starting at your second sentence.

Cheers

I have another seemingly silly question. Is the only way to update to the latest v2 by manually downloading from the site or by trying to run a script that has a very specific #Requires directive such as #Requires AutoHotkey v2.0-beta.12 so that the launcher prompts to download and install it?

@kczx3 You can, of course, automate it using whatever means you wish. And since the launcher is a script, you can just copy how the launcher does it.

From memory, the launcher invokes install-version.ahk 2.0-beta.12 or whatever. The version number must be exact. You can retrieve the latest version number from https://www.autohotkey.com/download/2.0/version.txt

kczx3 wrote: ↑

12 Oct 2022, 10:48

I have another seemingly silly question. Is the only way to update to the latest v2 by manually downloading from the site or by trying to run a script that has a very specific #Requires directive such as #Requires AutoHotkey v2.0-beta.12 so that the launcher prompts to download and install it?

could also submit ahk v2 to chocolatey package manager for distribution

@lexikos of course I could do it on my own and likely will. But for the thousands of users of AHK I think it makes most sense to build in a notification of available update and the ability to install it within the Dash.

guest3456 wrote: ↑

13 Oct 2022, 04:41

could also submit ahk v2 to chocolatey package manager for distribution

winget. since it is buildin with newer windows versions.

@kczx3 I'm open to considering pull requests for this and other improvements.

Package managers are outside the scope of this topic.