![]() Consider the code examples here: for instance. It was just the simplest language, yet fairly powerful in creating working UI-based programs. I was reminded by post of Gui4Cli, which worked up to Windows XP and I've mourned its loss ever since. I feel the urge to start another search for new languages. While I accept the response from that you can still use v1, it does now feel like that's a dead end at least in future, so I had hoped to switch rather than be forced to later. So I'm finding things to dislike, too, in the version change. Functions come less naturally to me than subroutines, and I've always preferred variables to be global by default. But I have always struggled with OOP, and tried to avoid as much of that complexity as possible. I was immediately pleased to see the simplified syntax in regards to getting rid of the legacy mode, and I was lucky in having already scripted mostly in expression mode. I am only just trying to work through my first conversion of a script and reading the help files, following the error messages and trying to figure out what's going on. I'd normally ask yet another question in the help section, but this feeling I have now is more general. I found this thread when I began looking for somewhere to chat about my struggles with the language. If you want to keep things as v1 similar as possible you can go from V2 supports using single quotes instead of doublequotes. ![]() The more traditional AHK way of concatenating strings and variables works in both v1 and v2 (see below). To stay with your emoticon association think of it as giving all incoming parameters a one way ticket to where the sun doesn't shineįormat() already exists in v1 and is optional in both v1 and v2. In other words the * here is like params* in a v1 variadic function but instead of putting the inputs into array params you just discard them. v1 gui events automatically sets A_Gui and A_GuiControl) that the snippet creator had no use for, I suppose, so they did (*) => instead of a redundant parameter name (GuiObj) => (*) are parameters for the fat-arrow function and * is a way to discard the parameters, used here because the Close event automatically passes a parameter (cf. Kind of like how ternary is optional in v1 and v2 and just shorthand for what can be done with if-else lines. => fat-arrow functions are optional, you can do everything with regular functions instead. ![]() But since it is hard to know what other things you dislike I'll comment on that specific snippet. But still an easy to code, well documented, powerful starter language! I guess you picked a code snippet just as illustration for a more general complaint. Easier in some ways, more difficult in other ways. I look forward to what is think v2 is all in all much better than v1. I thank all the contributors, you have eased my work life and continue to enhanced my computer usage every day. Include a database, include web browser integration, include a network stack, include a gui builder, include com, accessability, graphics, ocr, speech, and the sky is the limit. A smart compiler could include only the needed functions to keep size down.ĪutoHotkey is a wonderful project, and with a few changes it has the potential to replace every tool on the pc and web. What I want is more of the powerful functions from the forums to be included in the base installation. Sadly simplicity, readability and new user inclusion is hampered in the process.Ī smart interpreter could reduce the need for the V2 language changes. But now it's here, and progress usually means V1 is left in the dust. I gave up on AutoIt years ago due to the same changes. I was surprised to see V2 officially released, it's been years, and I've ignored the reality of it ever happening. And still AutoHotkey has been able to do anything I've thrown at it, with the assistance of the wonderful contributors in the community. Originally there were few paranthesis, no line ends, no conversion between data types, no case sensitivity, all the things that bug novice users in other languages. Write a line, test it, add another, rinse and repeat. No libraries, no definitions, just code and go. What set AutoHotkey apart from all other languages I've tried over the years, is simplicity combined with power. Take my ramblings as the lazy apprehension of an old man set in his ways, but I think there is something to be said for simplicity.
0 Comments
Leave a Reply. |