Triggers

[jsampson45]

Hello -

I am trying Quick Macros for the first time.
I have a macro script with the name "testSky":

key "Hello World"
act "SKY Index Professional" ;; a Windows program
wait 0.5
str s.getclip
act "Boxer" ;; a Windows text editor
wait 0.5
key (s)

The trigger is Ctrl+Shift+ m. wheel down.
Both the abovementioned programs Sky and Boxer are open and running.

I clicked "Save now". If I run the macro by selecting "Run", "Hello World" appears in the script. Nothing else happens.
If I activate the trigger, nothing happens.
What am I doing wrong?

[Gintaras]

This macro works on my computer. When I Ctrl+Shift+mouse wheel backward, it types "Hello World" in the active window, then activates Paint, Notepad, and pastes clipboard text.
Macro Macro2555
Trigger #CSD     

Code:

Copy      Help

key "Hello World"
act "Paint" ;; a Windows program
wait 0.5
str s.getclip
act "Notepad" ;; a Windows text editor
wait 0.5
key (s)

To copy Quick Macros code to this forum, use menu Edit -> Other Formats -> Forum. Then simply paste in the post.

If a trigger does not work, possible reasons could be:
Quick Macros is disabled. When disabled, QM tray icon is gray. It must be blue.
The macro is disabled.
The macro is in a disabled folder. Icons of disabled macros and folders have a red symbol added.
The trigger is used by another macro.
Another macro is running (depends on macro properties).
Triggers of that type are disabled in Options -> Triggers.
An error in the macro. Then you can see error text in QM output.
The trigger is set to work not in all programs.
Quick Macros is running with lower UAC integrity level than the active program. Look in Options, should be Administrator or uiAccess, not User.

But in this case maybe the trigger works. To test, add this line at the beginning:

Code:

Copy      Help

mes "trigger works"

If the macro starts but does nothing or just types "Hello World":
1. Look in QM output, maybe there is an error, for example "window not found". Window names in Quick Macros scripts are case sensitive.
2. Run the macro in debug mode. Start it not with the Run button, but with F5 key, then press F5 F5..., to run the script in steps. Then you will know which step (statement, line) does not do what it should do.

[jsampson45]

Many thanks - the macro was in a 'disabled' folder.