Autohotkey module managing and developing framework.
The last Qt updates involved quite some work. A couple of widgets broke with this latest version. The whole widget connection system was stirred up and so the module editor with the hotkeys, the hotstrings and the menu-buttons ... Update 0.5.3 And seems the very latest Qt for Python breaks my multi inheritance stuff. I know this is bad practice anyway but I didn't know any better back in these days. So we're back on 6.4.2. Which is fine for our needs anyway. Fingers crossed!
I hope it's all covered now. But in any case: Thanks for reporting and keep reporting! Cheers: eRiC
❌❌❌BROKEN!❌❌❌Please do not use this release!❌❌❌
That update involved some work. A couple of widgets broke with this latest version. The whole widget connection system was stirred up and so the module editor with the hotkeys, the hotstrings and the menu-buttons ...
I hope it's all covered now. But in any case: Thanks for reporting and keep reporting! Cheers: eRiC
Finally the update-checker that was already working under the hood made it's way to the surface. We have a new "About dialog" as proposed by @sirtet #265, it displays the current and latest online version as well as the versions of all found module source packages. In dev mode it also lists all the components that might be outdated (such as Autohotkey, Python and PySide) Still a2 is not updating itself though! It currently only points to github if there is a new release. But the installer can already update properly and so there is a little less pressure? I hope :) Aaaand: Updates to module packages are shown in the About dialog but are not yet otherwise made apparent. Bear with me that's a next.
Also the Console/ log view received a little update! One can now see a timestamp of a block in the log that and some issues with the new error reporting in Python3.11 were resolved (apparently when exceptions underlined things with ^^^^^ these were pushed to the stdout one by one resulting in a page of single ^ in our log. That's why the block thing now.)
Weeell, I wasn't up with all my senses. I left the dev version on 0.4.6 and decided on release to make it 0.5.0 because of some more changes. Now all is good! :) 🤞
Finally the update-checker that was already working under the hood made it's way to the surface. We have a new "About dialog" as proposed by @sirtet #265, it displays the current and latest online version as well as the versions of all found module source packages. In dev mode it also lists all the components that might be outdated (such as Autohotkey, Python and PySide) Still a2 is not updating itself though! It currently only points to github if there is a new release. But the installer can already update properly and so there is a little less pressure? I hope :) Aaaand: Updates to module packages are shown in the About dialog but are not yet otherwise made apparent. Bear with me that's a next.
Also the Console/ log view received a little update! One can now see a timestamp of a block in the log that and some issues with the new error reporting in Python3.11 were resolved (apparently when exceptions underlined things with ^^^^^ these were pushed to the stdout one by one resulting in a page of single ^ in our log. That's why the block thing now.)
Hello. Another smaller bugfix one :)
sqlite3.dll. Well, it worked for Python! But not for Autohotkey!
Talking from the Autohotkey-Runtime to the a2 database is not so widely used but still this was a shitty issue. As of writing this Python 3.11 still ships with Sqlite3 3.38.4.0 where ther're on 3.40.0 already!
So I went to make our package builder to patch the sqlite3.dll if it appears to be outdated. Turns out the download-method I was using via Python built-in urllib breaks on the Let's Encrypt certificate of https://sqlite.org . As I wanted to create an easy to use method using Qt for Python via QNetworkAccessManager anyway I went forward doing that as well and use it to make this build-script fix right away.Hello again with a fix release! Sure there had to be something with the new Qt for Python version :) The UI was not opening up due to a missing shiboken file that I now fetch the longer version number from.
Please Pardon the silence. There is soon to be more :) This one some small updates:
Hello there again already! Not so much news here now but some important ones!
Meaning we no longer rely on PyInstaller (but a small download of an "embed" Python package)
The former packages look pretty similar. There is no more a2app.exe in our ui-directory but the complete set of python scripts and the original python/w executables. Since we have Autohotkey-compiled runtime- and ui-starters in our root anyway the ui starter now just runs the embed python with the a2app script. Voilà!
This not only reduces build times dramatically but makes the whole package less prone to being victim of antivirus heuristics. Our 0.3.0 portable tripped a whopping 16 of those on virustotal! Merely because we "freeze" with PyInstaller! Still the package was fine with Windows Defender.
Now there was a whole different issue in there with module downloads. I fixed that with a couple lines of Python code, build and pushed 0.3.2. It had almost the same 16 findings BUT now Windows Defender was complaining!
Well, finally we're down to 2 flaggings on virustotal probably because of the Autohotkey-compiled starter executables. I can try and upload false-positives for these (frankly, never-heard-of) vendors. But most important is that Windows Defender is fine. And I think .. I'm pretty much certain this is solved for good!
Trying our new build method #254 ... Please report on this issue if anything weird occurs. Thank you! 🙏
PATCH🩹 release fixing #253 with improved download/install code. 🤞
Hello there! Thanks for your interest in a2! Much appreciated 🙇♀️
Again we have almost 100 commits piled up. Most interesting:
6.2.3.0 seems mature enough now.*clipboard library hackery now bent to use the well cooked WinClip internally.path, explorer with some ports from modules to be available everywhere.ico images to be used in modules (we cannot make use of svgs in Autohotkey runtime)Loads of thanks to @Cyberklabauter for testings and suggesting things (#250)! More to come with the modules update!
(*) For PySide6 they go with native scaling which might cause some tiny rendering issues when you actually scaled your Windows UI but its OK. Might be we need to deal with it explicitly but its not too bad now.