01-24-2010, 09:16 PM
I've noticed at times that if threads are terminated from QM some of the functions of QM will start throwing some odd ball errors on functions that are normally extremely reliable.
If something starts to throw errors where there were no errors before it is always a good starting point to re-start Quick Macros.
If that doesn't solve the problem, restart your computer...
If that doesn't solve the problem...then it is probably your code. Usually I never have to restart my computer and restarting QM does the trick. If you ever have to end a thread, you'll see that Gintaras has included a recommendation to restart QM. Don't ignore what Gintaras has to say about things...he's usually right!
Thanks,
Jimmy Vig
If something starts to throw errors where there were no errors before it is always a good starting point to re-start Quick Macros.
If that doesn't solve the problem, restart your computer...
If that doesn't solve the problem...then it is probably your code. Usually I never have to restart my computer and restarting QM does the trick. If you ever have to end a thread, you'll see that Gintaras has included a recommendation to restart QM. Don't ignore what Gintaras has to say about things...he's usually right!
Thanks,
Jimmy Vig