terrypin Posted January 25, 2009 Report Share Posted January 25, 2009 We discussed this in the thread http://pgmacros.invisionzone.com/index.php?showtopic=3518 and I sent a bug report. It was assigned the tracking number [iSS6421] I haven't yet checked this specifically with a pop-up menu, which was what prompted my original query. But I can confirm that in the latest 4.0.1.1 release I am still getting invalid messages when I save any 'normal' macro that has a shortkey activation. I add a shortkey activation that is unused by any other enabled macro and then click Save and Close, but get "The ShortKey activation may conflict with one or more macros. You may have multiple macros launched when using this activation." -- Terry, East Grinstead, UK Quote Link to comment Share on other sites More sharing options...
joe Posted January 26, 2009 Report Share Posted January 26, 2009 I add a shortkey activation that is unused by any other enabled macro and then click Save and Close, but get "The ShortKey activation may conflict with one or more macros. You may have multiple macros launched when using this activation." According to the WhatsNew.txt it was fixed. Or something like it was fixed. If you are still experiencing it I would place another bug notification. Macro Express Pro v 4.0.1.1 6. Fixed a problem in the menu builder which would generate duplicate shortkey warnings when saving a menu. 46. Made a change to allow punctuation characters to be entered as a part of a shortkey activation. Quote Link to comment Share on other sites More sharing options...
terrypin Posted January 26, 2009 Author Report Share Posted January 26, 2009 According to the WhatsNew.txt it was fixed. Or something like it was fixed. If you are still experiencing it I would place another bug notification. Macro Express Pro v 4.0.1.1 6. Fixed a problem in the menu builder which would generate duplicate shortkey warnings when saving a menu. 46. Made a change to allow punctuation characters to be entered as a part of a shortkey activation. Thanks Joe, duly done. After further testing I think this happens when a shortcut has been assigned previously, but to a macro that is now disabled. And even if the shortcut for that disabled earlier macro is then changed to some third string, unused anywhere, that too then generates the error. IOW, the bug sort of spreads. I also experienced some other very odd behaviour when I was playing around with this. It may or may not be related. While trying to change the troublesome shortcut I used the backspace key to delete the two existing characters. An unprintable 'empty square' symbol appeared. And more of them with subsequent keystrokes. Had to terminate ME Pro. -- Terry, East Grinstead, UK Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.