Jump to content
Macro Express Forums

Samrae

Members
  • Content Count

    411
  • Joined

  • Last visited

  • Days Won

    21

Samrae last won the day on December 1 2020

Samrae had the most liked content!

Community Reputation

16 Good

About Samrae

  • Rank
    Expert

Profile Information

  • Gender
    Male

Recent Profile Visitors

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

  1. To change the font and color within Macro Express itself try the preference settings: Click Options, Preferences, Appearance and then the General, Explorer, and Script Editor tabs.
  2. You're welcome. Perhaps you could add something like this: Variable Modify String: Replace ":\\" in %tFolder% with ":\"
  3. This is not a valid file path: Try this instead: M:\AttributeChangeDateFromShed.mex
  4. No, you were not wrong. UWP programs do not follow long established standards for Windows programming. Hooks work but many hotkeys are blocked. I cannot launch a UWP .exe using the Program Launch command so I have to launch it from the menus. They do not use Alt key shortcuts. The is no File menu. They are very slow and require long delays. They do not support Window Controls. Because you prefer to use Window Controls your statement that macros do not not work with UWP programs is not incorrect. Specifically, in this case, your macro activated with Ctrl+Keypad 9 did not
  5. Do you have a macro that uses the Keystroke Speed command? I discovered that if one macro sets the Keystroke Speed, to 500 say, and does not reset it back to 0 then all other macros that I run after that type text slowly. I try to remember to set Keystroke Speed back to 0 in any macro that changes it. You could check for this by putting a Keystroke Speed: 0 at the top of one of your macros that is typing slowly. If it starts to work more quickly you can search for the macro that slows down the keystroke speed. Another thing to check is whether the Delay after keystroke
  6. Stupid question: Does it help if you restart Macro Express and/or Windows? My macros slowed waaay down when we switched from Norton Internet Security to BitDefender. (I cannot wait to get rid of BitDefender. 🙁)
  7. I failed to mention that my macro is activated with Ctrl+Alt+a. It works whether or not Settings is already loaded. in other words, a Ctrl+Alt+a hotkey works as an activation from within the Settings application.
  8. It has been stated several times on forum that Macro Express does not work with UWP programs. That is not my experience. UWP programs behave differently than Win32 programs but, with some effort, I have been able to get Macro Express to work with them. I took this as a challenge to get Macro Express to work with Windows 10 Settings. Here is a macro that opens Windows Settings, navigates to Apps & Features, and closes Settings. Note: This macro was written with Macro Express Pro 6, not ME 4. // ----------------------------------- // Initialization // ----------
  9. The Code Tool is here in the forum software. When you are typing into the forum there should be a series of icons right above. The <> is the Code Tool Terry is demonstrating:
  10. To copy what you see in the Macro Script Editor, highlight the macro lines lines you want, right-click, and click "Copy Command Text". Then, in this forum, click the <> icon and type ctrl+v to paste. The result looks like this: Text Type (Simulate Keystrokes): <ALT>e Text Type (Simulate Keystrokes): <ALTD>e<ALTU> To copy macro commands that someone can copy from this forum and paste into Macro Express, highlight the macro lines you want, right-click, and click "Copy". Then, again, in this forum, click the <> icon and type ctrl+v to paste. The result looks l
  11. As recommended elsewhere, please put macro samples in a codebox (see <> above) instead of posting an image. When you have the macro do a Text Type <ALT>E what gets sent to the application is <ALT Down> <Shift Down> e <Shift Up> <ALT up>. What you need is: Text Type (Simulate Keystrokes): <ALT>e Sometimes that does not work reliably. This often works better: Text Type (Simulate Keystrokes): <ALTD>e<ALTU>
  12. Another thing you could do is to add a Wait for File Ready on the line above the Log Messages / Log Errors commands.
  13. Your answer came in just before as I submitted mine. Are we thinking alike now? 😃
×
×
  • Create New...