hasantr wrote: ↑
13 Dec 2019, 12:41
Hello. I like the features of AHK-H. AHK-L I'm new. I want to develop with AHK-H, but I don't know where to start. Which editors can I use?
I especially use AHK Studio. But it doesn't work with Studio AHK-H.
If you are using AHK_H v1, you will find that AHK Studio is quite compatible. This is because AHK_H v1 is a superset of AHK_L v1, and built on top of it. The few problems that I've seen have been:
1) AHK_H help files are not compatible with AHK_L
Meaning you primarily would use/configure for the AHK_L v1 help file
, then use the AHK_H v2 file as a supplement (for extra features/keywords). This is because HotKeyIt focuses on updating AHK_H v2 documentation and not AHK_H v1, and only
referring to his additional features.
The AHK_H v2 documentation is for both AHK_H v1 and AHK v2, which can be confusing. For greater clarity, it would probably be better (wish list) if HotKeyIt would make this clear, that the present AHK_H help file is referring to additional feature present in both AHK_H v1 and v2. And if syntax is different between his added features/keywords between the versions, he can simply show the distinction in the examples. Thus, there would be a combined AHK_H v1 and v2 help document.
Since AHK Studio is written in AutoHotkey (AHK_L v1), it can be modified by AutoHotkey users to open the AHK_H help file too or you can build a supplemental script that monitors for AHK_H keywords and opens the AHK_H help document when pressing a key of your choice. Like, F1 for AHK_L v1 help and F8 for AHK_H help.
2) Make sure the AHK_H lib folder has all the correct files
If your AHK_H lib folder is missing files, then the user can experience odd errors which causes confusion, when using AHK Studio. In addition, the AHK_H user might have also compiled AHK_H incorrectly or oddly, so are getting unexpected results. However, such problems are not the fault of AHK Studio, but are based on actions taken by the user.