Jump to content
Macro Express Forums


  • Posts

  • Joined

  • Last visited

  • Days Won


rberq last won the day on July 5

rberq had the most liked content!

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

rberq's Achievements

  1. Ah, but don't we all write intentionally-infinite loops (REPEAT UNTIL %X% IS NOT EQUAL TO %X%)? We do that because REPEAT START does not have a REPEAT INDEFINITELY option. But I agree -- it is always wise to explicitly limit the loop in case, heaven forbid, we commit an error in logic. Also, I generally embed the same 1/10 second delays like Cory does, if it's a macro the user is waiting for. Longer or shorter delays when waiting for the computer itself to finish doing something, when human perception is not involved.
  2. Look at the Repeat instructions. There is a "Repeat Until ...." that should do what you want. Though the logic might be easier if you use "Repeat Start...". For example, REPEAT START IF COLOR1 = XXXX AND IF COLOR2 = YYYYY DO STUFF ELSE REPEAT EXIT END IF END REPEAT
  3. A .mex file is not a macro. A .mex file contains many individual macros. You don't have to open the .mex file every time you want to activate a macro. Once you open it, it stays open, and all the macros within it can be activated via their hotkeys.
  4. If you copy the .mex file AFTER installing MEP on the new computer, the installation will already have created a .mex file. In Macro Explorer you can select File | Open to access the copy containing your macros, rather than the skeleton produced by installation.
  5. See screen image below. The file that MEP is working from should appear at the bottom of the screen, where the red arrow is pointing. You can copy the entire .mex file from the 'old' computer, and put it on the new computer -- just be sure to name it differently from the file that MEP is working from. Then in Macro Explorer, select File | Import | Import Macros, specify the copied .mex file at the bottom of the import screen, click Open, then select the individual macros to be imported.
  6. Do you mean Macro Express no longer starts up automatically when you start Windows? Or do you mean it no longer works, period, even if you start ME manually? Try reinstalling Macro Express and see if that starts it working again as you expect it to work. Then just for fun see if the deleted items have come back.
  7. I'm going to make a SWAG (Silly Wild-A** Guess). It's not a solution so it will satisfy no one. And my knowledge of Windows structure is vague enough I could be totally wrong. There -- so much for disclaimers. Q-Dir has been around for a long time. Over the years, an application's relationship to the keyboard has evolved from the primitive ability to interact directly with the BIOS, to present-day highly-structured "layers" of software between the application and the hardware. Perhaps Q-Dir generally adheres to Windows conventions, but has an old embedded module or two using an outdated technique that still works, but that sneaks in below the officially-correct level used by MEX. Like coming in the back door instead of the front. So sometimes MEX and Q-Dir communicate just fine, and sometimes not. OK, there's my semi-magical-mystical view of the machine's mind. Works for me, you guys can come up with your own religion. 😐
  8. Has either of you tried activating the macro with a hotkey that does not use ALT or CTRL? I like to use the keypad symbols -- slash, asterisk, minus sign, plus sign.
  9. Silly question, maybe --- do you by chance have some other macro triggered by <CTRLD>1<CTRLU> ??? Edit: Another simultaneous posting. acantor beat me this time.😐
  10. I have had macro typing fail intermittently if the keystrokes are entered too fast. Most of my macros have this standard command at the beginning: Keystroke Speed: 30 milliseconds That's usually fast enough to keep me from fidgeting, but slow enough so the application is not overwhelmed. Edit: Oops! We posted at the same time. I see you have already tried that.
  11. You can insert message boxes like this at many critical points in your macro, to determine how far the macro has progressed. Within the message box you can also display the values of variables, if you are wondering why IF conditions are not being met, and so on. Once debugging is complete, remove the message box commands -- or, better, just inactivate the commands so you can re-activate them six months from now when something changes and the macro suddenly stops working. 😉
  12. IF the Citation window ALWAYS appears in the same location on the screen, perhaps your macro could move the mouse to the specific location on the screen where the icon resides, then click the mouse. I have several macros triggered by hotkeys that do this, and as long as I run full-screen windows, the icon location is consistent. Of course, an application update sometimes moves the icons a little bit, then the macro must be adjusted for the new location.
  13. I was thinking of something similar. Maybe open the script in the Direct Editor, copy all to the clipboard, manipulate whatever needs to be manipulated to add a variable, then paste the modified content back into the Direct Editor, overlaying the original macro. Seems like a good way to get into trouble .... I have been trying to figure out why anyone would WANT to create variables on the fly. Perhaps to set up the "data" environment all at once, before starting to write the procedural logic for a macro. You could make a spreadsheet or text file with variable names and attributes, then read the file with a macro and make the variables all at once. Labor saver??? Or not?
  • Create New...