Possible problem with new macro,quick launch, and hot key ??

bnc1 · Post by **bnc1** » Thu Jun 19, 2008 2:18 pm

I have a wierd problem with MS 10.1.15 that is reproducible on both Vista x64 Ultimate and Vista x32 Home Premium. Something odd is going on with MS quick launch and hotkeys.

Can anyone recreate this problem ? Before you start make sure you have at least 2 existing macros, one that runs from Quick Launch and another macro that runs via hotkeys.

1) Create a new macro
2) Either boot your system or manually exit MS and restart it
3) Right click the MS icon and use Quick Launch to run an existing macro
4) Run a different macro via a hotkey

On my system, the macro invoked via a hotkey is NOT the one that should run. It is some other random macro.

5) manually exit MS and restart MS
6) try the quick launch and hotkey macros again, this time the correct macro executes

As stated previously, I can recreate this problem. The combination of new macro, quick launch, and hotkey is the source of the problem on my system.

Post by **Marcus Tettmar** » Thu Jun 26, 2008 4:44 pm

I've just replicated this. We'll look into locating the cause and fixing it right away.

Post by **Marcus Tettmar** » Fri Jul 04, 2008 12:04 pm

Hmm .. well I thought I had replicated this. But now I can't. Are you still able to replicate this? If so could you perhaps zip up your Macro Scheduler macro folder including all .dat, .ini and .scp files so that we can test with your setup?

Anyone else able to replicate?

bnc1 · Post by **bnc1** » Fri Jul 04, 2008 1:42 pm

This is slightly different from the original post but I can recreate this on a clean system. I stopped MS, backed up and deleted everything in the MS folder. I started up MS ..no macros present. I created 2 new macros, both very simple with just one unique MDL> statement. macro #1 was quick launchable, and macro #2 had a hotkey (NP0). Then I stopped and restarted MS. Next create a 3rd new macro. Then quicklaunch macro #1 and all is fine. Hit the hotkey (NP0) associted with macro #2 and the error occurs as the hotkey starts the new macro #3 (or sometimes even macro #1) when in fact it should start the hotkey macro #2.

Post by **Marcus Tettmar** » Fri Jul 04, 2008 2:47 pm

bcn1: Just followed your instructions to the letter and still didn't replicate. Are you using the latest version?

bnc1 · Post by **bnc1** » Fri Jul 04, 2008 3:06 pm

as per the orignial post ...

"I have a wierd problem with MS 10.1.15 "

Post by **Marcus Tettmar** » Fri Jul 04, 2008 3:10 pm

Apologies, was looking at your last post and didn't check the first.

bnc1 · Post by **bnc1** » Fri Jul 04, 2008 3:21 pm

I can send you the newly created MS macro lib if it would help. Where/how shouid I send it ?? I am reluctant to send you my "normal" MS macro lib as it contains personal info

Post by **Marcus Tettmar** » Fri Jul 04, 2008 3:22 pm

please zip up all files and send to [email protected]

Post by **Marcus Tettmar** » Mon Jul 07, 2008 8:00 pm

This issue is now fixed in 10.1.17.