coffent

Thanks for the information & suggestions!

The online Help* says that to remap the keyboard: 1. From the Macro Explorer, select Tools > Remap Keyboard. 2. The Remap Keyboard window will activate. However when I do this the Remap Keyboard window does *not* appear. It also says: Note: Click on Options > Preferences > General and select the Miscellaneous tab to disable the Keyboard Remapping feature. It shows a screenshot Close open .... Disable keyboard remapping Delete temporary... However when I follow these instructions there is no "Disable keyboard remapping" option. How can I remap the keyboard? Thanks for any suggestions. Version: Macro Express Pro 6.3.3.1 * https://www.macros.com/helppro/Index.htm?context=3240

Thank you.

In the following code: 1 If Condition_1 2 OR 3 Some non-If statement 4 Condition_2 5 More code 6 End If If Condition_1 is satisfied, does the macro also check Condition_2 or does it go immediately to Line 5? If Condition_1 is not satisfied, will it execute Line 3 then check if Condition_2 is satisfied? Thanks!

Thanks for checking the problem and for the suggestions. I un- and reinstalled ME Pro which seems to have cured the activate on window gaining focus problem as well as some others I was having (hopefully for good). However this current problem still persists. I've removed the window activate command from the macro, so all it does is paste or type text into an already-activated window such as Notepad or Wordpad. Thus there are no issues of window activation times. Most of the time it works but perhaps 5% of the time it does not do the clipboard paste even though it does the simulate keystrokes enter. I've noticed that whenever this error occurs the macro beeps. I assume this must be an error catch routine built into ME4, but have no clues beyond that.

Thanks, Terry. I should have done it before, but I finally did thoroughly uninstall and reinstall ME Pro, and this and other problems I reported now seem to have gone away, hopefully for good!

I don't see that it should make any difference, but for example I ran it in Notepad with a character highlighted that should then have been deleted, but wasn't.

A macro simplified to the following: Keystroke Speed: 50 milliseconds Text Type (Simulate Keystrokes): <DELETE> instead of doing what it's supposed to do, instead runs rapidly and repeatedly (about 10 times per second) without doing anything. I must finally abort the macro. If instead of "<DELETE>" an ordinary letter is substituted, the macro works correctly. Do others find the same problem?

I should have mentioned that I had a wait 500 msec command after the Window Activate command in the test macro, and in any case I was calling the macro when the window already had the focus. So I don't think it's a question of timing. I tried another series of runs later on, and the problem wasn't as bad - two bad pastes out of 50 times - but it's still there.

I ran the following simple macro written in ME 3 60 times. It always behaved as expected: Window Activate: Untitled - Notepad Text Type: Text1 //Paste "Text1" using the clipboard Text Type: Text2 //Enter "Text2" by simulating keystrokes I ran the same macro written in ME Pro 60 times. 44 of the times it worked correctly; 16 of the times it wrote "Text2" but not "Text1" There seem to be problems of stability of ME Pro vs. ME 3. See also my earlier post, "Macro responds sporadically or not at all to window gaining focus." Are others experiencing this problem?

Thanks for the suggestions and offers of help. The test macro is essentially one line: Beep. I am sure that the activating window has the focus. During my tests I launched the activating window many times in succession, always under the same conditions. Sometimes the macro ran; other times it didn't (while in ME 3 it always ran). Strangely, I'm finding that now both the original macro and the test macro are working once again! Perhaps there's something strange about my system, though I'm sure I don't know what it is. BTW, I hit upon the following clumsy, but workable, workaround that might possibly be of use to others. The working macro (as opposed to the test macro) is quite complex, and I'd thoroughly rewritten it with some changes in switching to ME Pro. I didn't want to go back and update the macro in ME 3, so I exported the ME Pro macro as a playable macro, then wrote a simple macro in ME 3 (which does consistently respond to the activating window); this macro launches the ME Pro playable macro. This requires, of course, that both ME 3 and ME Pro be installed on the system.

I had a macro in ME3 that responded to a window title gaining focus. It worked fine. The macro converted to ME Pro worked for a time, then stopped working. No other macro uses this activation. I wrote a test macro in ME Pro with the same activation, which does nothing more than beep. I disabled the original macro so there would be no conflicts. The test macro also worked for a time, then worked every *other* time(!), then finally stopped responding altogether. If I shut down ME Pro and reactivate ME3 the original ME3 macro still works fine. Any explanations for this bizarre behavior?

I've had a perhaps related problem that began occurring around the time I upgraded to Macro Express Pro from Macro Express 3. Frequently (but not always) when I try to paste something from the clipboard I get a Windows message that I never encountered before, saying "Unable to unload the clipboard." Nevertheless, after I click OK to dismiss the message, the clipboard contents are pasted correctly. I don't know for sure that ME Pro is the cause as I haven't done any troubleshooting, but I wonder if other users are encountering the same problem.

The problem with shutting down other running processes is that one may in fact want them to be running during idle time. Out of curiosity, does Macro Express use a Windows utility to determine whether there's been keyboard/mouse activity? Since keyboard/mouse activity constitutes a rather low-level input process, I would think (perhaps naively) that it would be relatively easy to reliably determine whether such activity had occurred or not.

I originally had the schedule for my macro set to wait 10 min, run every 15 min, but I was having the same problem as terrypin that the macro never ran, so I shortened the time to 2 min / 1 min for testing. As I understand from the explanatory material, "After the computer has been idle for m minutes, run every n minutes" means that in the absence of keyboard/mouse activity the macro will run at (m+n) minutes, (m+2n) minutes, (m+3n) minutes, etc. Thus I did mean 3 minutes in my closing question. (Actually, it would seem to make more sense to have the scheduler run the macro at m, m+n, m+2n... minutes, but I suppose that's another issue.) My computer was not absolutely idle during the wait period in the sense that there were various background programs running, but nothing, as far as I know, that simulated keystrokes or mouse actions. Since terrypin's 2nd macro does simulate keystrokes I would expect a 3-min repeat time for it, based on a 2 min / 1 min schedule. My macro calls a Visual Basic executable which writes to a file, but I didn't think writing to a file constituted keyboard activity.