AutoHotkey Community

Hi Tuncay,

Actually AHK Classic is installed with XP.

I installed the whole pack . . .

But, for now it seems that all is well . . .
Although is could take months before I notice anything . . .



Anyone know hich one should be installed for AHK Classic and for AHK_L ?

Thanks in advance.

@awannaknow, all included libraries are made for and tested with AutoHotkey Basic (we use Classic as a synonym for Basic in our AHK community). Installing all should work without problems for this. Btw, just as a notice: You can just copy the whole libs folder to your user library with the Windows Explorer in one copy-paste action.

But if you have the current AutoHotkey on your computer, then its not that easy. Some libs do not work with it. There are newer versions out of some libs, which are compatible with L. And some other you do simply not need anymore.

_________________
{1:"ahkstdlib", 2:"my libs", 3:"my apps", 4:"my license"}
--> Don't feed the troll! <--

Now that autohotkey_L is the main branch, we will have something like this for it?

Since AHK_L is under active development and therefore subject to changes, so are any compatible libraries. Building such collection would prove time consuming and eventually unfeasible, due to possible frequent changes.

It's improbable that someone would take over such task, although not impossible.

_________________
AHK tools by Drugwash (AHK 1.0.48.05 and Win98SE)

@Peixoto
I do not maintain the collection anymore. If someone want take this project over or begin with a new similiar one, I would greatly appreciate it.

_________________
{1:"ahkstdlib", 2:"my libs", 3:"my apps", 4:"my license"}
--> Don't feed the troll! <--

Well, missing the library hurts AHK a lot...

If that's the case we shouldn't even be going to AHK_L after all

Of course, with the new features you can do a lot more with AHK_L, but you do it the harder way.

AHK was suposed to be friendly for for newcomers, wasn't it?

Why do you think the new ahkl would be harder to use or learn? It is more or less the same with legacy Ahk Basic, additionally it have some features more, which are essiantial. Most scripts work as they are or with small changes with new ahkl v1.1.

I personally switched (very late, since some month) because some things are solved faster, easier and more elegant. And the support of Unicode was THE killer feature. You can use it like ahk basic if you want. Nobody is forced to use the new features.

I'm not saying that AHK_L is more difficult, and i 'm hopping i will finally learn about classes and OOP with it

What i said is: if you wanna do something you could do before with the stdlib, you can probably find another way to do it with AHK_L, but it would be more work than simply using the lib.

I've managed to use some libs written for AHK basic just using the ANSI version of AHK dll, calling them from a script running in ahk_L, but it's not always possible...

You can find a compilation of miscelaneous AHK libs, wrappers, classes, etc for AHK basic, _L, and v2, at https://github.com/george2/ahk-libs. These scripts use many different licenses, and may or may not be StdLib-compliant. The 'ahkstdlib' collection is included, along with many other scripts, with explicit permission from the original authors wherever possible. See the README for more information of specific libs that are included.