03-30-2006, 06:02 PM
I don't think scheduled tasks and keyboard triggers are related.
The problem with scheduled tasks probably is the following. You have QM 2.1.8 for several months. That version was unfinished. Now QM command line syntax used with scheduled tasks is different.
Sometimes keyboard and mouse triggers stop working when some modifier key is pressed but not released for some reason. For example, if a function executes key+ S, but does not execute key- S, then Shift is leaved in pressed state. If you then press Ctrl+J to run a macro, actually is recognized Ctrl+Shift+J, and Ctrl+J trigger does not work. Usually this also causes applications to behave strangely. You wrote that triggers were restored when you pressed Ctrl+Shift+Alt+D. Next time, try to press only Ctrl, Alt and Shift, without D. Please notify me about the results. Also, when triggers stop working, are the keystrokes filtered (if "Eat" is checked)? Also, do you have accessible object triggers? Also, what trigger and what macro and what window it was?
The problem with scheduled tasks probably is the following. You have QM 2.1.8 for several months. That version was unfinished. Now QM command line syntax used with scheduled tasks is different.
Sometimes keyboard and mouse triggers stop working when some modifier key is pressed but not released for some reason. For example, if a function executes key+ S, but does not execute key- S, then Shift is leaved in pressed state. If you then press Ctrl+J to run a macro, actually is recognized Ctrl+Shift+J, and Ctrl+J trigger does not work. Usually this also causes applications to behave strangely. You wrote that triggers were restored when you pressed Ctrl+Shift+Alt+D. Next time, try to press only Ctrl, Alt and Shift, without D. Please notify me about the results. Also, when triggers stop working, are the keystrokes filtered (if "Eat" is checked)? Also, do you have accessible object triggers? Also, what trigger and what macro and what window it was?