04-02-2016, 04:57 PM
I am not an expert and I do not know if I am right, but below my "explanation"
(If someone else reads my below explanation and if missed or explained something wrong please correct me)
Compiled Macro's / function's to exe and their original form do not have the same functionality when it comes to triggers.
To elaborate:
Within QM In the left you see all the items you have in QM (your Macro's , functions, classes, etc...).
If you attach a trigger to an item (Macro/Function) in QM it is only available within QM, this means QM must be running at all times if you want to take full advantage of the triggers.
Once an item is compiled to exe, the attached triggers are not available anymore.
My guess is, it is to keep the .exe as small as possible. Also most triggers (I think) need .dll components /hooks to be available within your operating system thus QM needs to run in the background if you want to take full advantage of triggers.
This is not a limitation that applies to QM only, other Macro tools with .exe compiling functionality have to take into consideration what they need to include in the .exe to keep it all contained into one executable that is of reasonable size.
This does not mean the final compiled exe can not contain triggers, it can actually but they must be programmed into your macro.
But the way program "triggers" into your maro is totally different then the way it is implemented in QM.
Most things are not directly possible but some things are with some kind of "circumvention", for example you could use in a function "ifk(S)" to check of [SHIFT] was clicked.
How to implement a window trigger in an exe...that's really difficult (for me) but maybe someone else could give you a hand with that.
(If someone else reads my below explanation and if missed or explained something wrong please correct me)
Compiled Macro's / function's to exe and their original form do not have the same functionality when it comes to triggers.
To elaborate:
Within QM In the left you see all the items you have in QM (your Macro's , functions, classes, etc...).
If you attach a trigger to an item (Macro/Function) in QM it is only available within QM, this means QM must be running at all times if you want to take full advantage of the triggers.
Once an item is compiled to exe, the attached triggers are not available anymore.
My guess is, it is to keep the .exe as small as possible. Also most triggers (I think) need .dll components /hooks to be available within your operating system thus QM needs to run in the background if you want to take full advantage of triggers.
This is not a limitation that applies to QM only, other Macro tools with .exe compiling functionality have to take into consideration what they need to include in the .exe to keep it all contained into one executable that is of reasonable size.
This does not mean the final compiled exe can not contain triggers, it can actually but they must be programmed into your macro.
But the way program "triggers" into your maro is totally different then the way it is implemented in QM.
Most things are not directly possible but some things are with some kind of "circumvention", for example you could use in a function "ifk(S)" to check of [SHIFT] was clicked.
How to implement a window trigger in an exe...that's really difficult (for me) but maybe someone else could give you a hand with that.