processing limitations or reasons not to use ahk for larger programs?
Posted: 17 May 2018, 08:46
I'm just wondering if there are any practical limitations using AutoHotKey to write larger programs?
It's just that I've been writing a program for a ... ahh.. well I just looked into it and i've got related files over 5 years old
So as you can imagine with continual development what started as a simple script is something that I would consider legitimate software. For the initial purposes of the 'script', AHK was ideally suited for it, taking hotkey imputs and launching programs. However, now I intend on feeding datasets through it. AHK had no problem creating the first test dataset, but my intent is to add weight to these stored variables based on the user's behaviour when using the software. ie the user ends tasks labelled 'red', send less and less tasks labelled 'red' the more the user kills them. the first test database it created has 8000 keys so far and it's nowhere near complete and I haven't even started assigning them weight.
Can I keep using AHK, or am I going to have to create a module in another language and feed my base program data, or rewrite the entire thing? I'm thinking if there is any time to do this it should really be now. I'm just concerned at the huge task to rewrite 5 years of writing endless lines of nonsense then repacking it into loops I can barely follow.
If I should rewrite it or write new modules, what should I use? In technical terms there's nothing in the software beyond launching, tracking and managing software windows and basic key input and output. everything it manages is well behaved, unlike a few games i've use AHK to script that need a range of specific conditions written into the script to interpret the i/o. everything else about how it calculates how it behaves and basic gui prompts are a simple enough.
I was just a bit concerned as Microsoft Excel often very repeatedly tell me to go f myself. It loves to crash at save time when I'm getting a bit extreme with my vb and referencing. Its just that ahk has never hit me with some weird bugs like a lot of vb based software if you don't have the correct reference files etc, it's never given me any headache beyond just getting the code right. I recently wrote something cool in bash to wrap some logic around some curl commands to fully automate downloading files upon availability, sanitizing raw names to reference/describe/upload elsewhere. But my god, the errors that made absolutely no sense even after resolving them and the nonsensical soup of commands each with their own unique syntax.
to all the developers of ahk, thankyou very much, with the exception of microsoft excel i've enjoyed using it more than any other software although this post has made me realise that maybe I use excel like someone trying to paint a wall with a hammer.
It's just that I've been writing a program for a ... ahh.. well I just looked into it and i've got related files over 5 years old
So as you can imagine with continual development what started as a simple script is something that I would consider legitimate software. For the initial purposes of the 'script', AHK was ideally suited for it, taking hotkey imputs and launching programs. However, now I intend on feeding datasets through it. AHK had no problem creating the first test dataset, but my intent is to add weight to these stored variables based on the user's behaviour when using the software. ie the user ends tasks labelled 'red', send less and less tasks labelled 'red' the more the user kills them. the first test database it created has 8000 keys so far and it's nowhere near complete and I haven't even started assigning them weight.
Can I keep using AHK, or am I going to have to create a module in another language and feed my base program data, or rewrite the entire thing? I'm thinking if there is any time to do this it should really be now. I'm just concerned at the huge task to rewrite 5 years of writing endless lines of nonsense then repacking it into loops I can barely follow.
If I should rewrite it or write new modules, what should I use? In technical terms there's nothing in the software beyond launching, tracking and managing software windows and basic key input and output. everything it manages is well behaved, unlike a few games i've use AHK to script that need a range of specific conditions written into the script to interpret the i/o. everything else about how it calculates how it behaves and basic gui prompts are a simple enough.
I was just a bit concerned as Microsoft Excel often very repeatedly tell me to go f myself. It loves to crash at save time when I'm getting a bit extreme with my vb and referencing. Its just that ahk has never hit me with some weird bugs like a lot of vb based software if you don't have the correct reference files etc, it's never given me any headache beyond just getting the code right. I recently wrote something cool in bash to wrap some logic around some curl commands to fully automate downloading files upon availability, sanitizing raw names to reference/describe/upload elsewhere. But my god, the errors that made absolutely no sense even after resolving them and the nonsensical soup of commands each with their own unique syntax.
to all the developers of ahk, thankyou very much, with the exception of microsoft excel i've enjoyed using it more than any other software although this post has made me realise that maybe I use excel like someone trying to paint a wall with a hammer.