John Welch

Yeah, sorry about that. I've had to take care of a lot since the last time I posted -- including getting divorced...

I see what you mean. That was actually a screen shot of the screen in my capture program. I just wanted to show the button and we had not gotten into the positioning and all that. Nor was the mouse cursor in any particular place. The actual screen has absolutely no visible controls for resize, or min-max nor any scroll controls.

Thank you

1. 1920 x 1080 2. No. See image 3. This is the code I am using: <MOUSE MOVE Option="\x01" X="1504" Y="221" _PROMPT="0x000A"/> I haven't tried 1163,176 because the mouse positioning is working reliably so far. Since I reduced the delay time from 800ms to 100ms, I have not had a problem with the button being selected. 4. Well, when it was set to about 1200,176, the mouse simply went to the wrong spot on the screen. Same when I tried "window." 5. corded mouse 6. None at all.

Yes, thanks. In this case window and screen are always the same.

Cool. Thanks for the lead.

Sorry. I get what you are after, but no. I was very very certain about the position of the mouse cursor. That is why I posted an image which clearly shows that the cursor is all the way to the right of the screen and shows the same (nearly) position as the one that I captured that is working to press the button. They cannot both be position 1504. If I move that cursor back over onto the button and press ctrl-space, it will capture the coordinates 1504, 221 (or thereabouts) as the middle of the button.

Thanks. I wasn't sure how to do that with the macro and code. My mouse cursor was not moving. I need you t get that I really really checked that out. Did you see my picture of the elephant in the room? The mouse locator does not agree with the capture tool. Does yours? I will reduce the delays. It is possible that the mouse cursor is drifting with so many near 1 sec delays. I'll try them at your recommended 100ms delay.

I probably should have found this out first: Can I package ME macros for distribution? If so, is there added cost?

I think I've covered this pretty well already -- that I cannot use the tab key, shortcut keys or any other reliable user navigation means to get to the button I want. The user could be anywhere on the screen when the macro is started. I do not know what you mean by, "The solution that is most likely to work is more complex." Why would I not be able to simply tell the cursor where to go. It seems dead simple to me. ME should be able to reliably place a cursor with simple commands. E.G.: "Mouse Move: 1502, 221 Relative to Screen." While this position worked yesterday it did not today. Today I had to change it to: "Mouse Move: 1582, 227 Relative to Screen." The position of the button did not move so why would the coordinates be different?

Thanks

Window or screen make no difference in this case. The programmers coded it to not have any resize and it is always full screen. They don't even let the taskbar pop up if the mouse goes to the bottom of the screen. Bottom line is the button is always in exactly the same place.

1. The only code I recorded was the original cursor positioning, arrow key movements and enter key. All the rest I did. I don't know what the delays are for, but I made sure I them with each movement of the mouse or keys. This is the first ME macro I have written. 2. Note: This code is working for now. I changed the mouse to a left click because I found that I can left click anywhere on the button to get the drop down. Then just arrow down to where I want. Ran it today on a 1 1/2 hr job. Code is attached. 3. I've done this. It is how I found out that the positions that were working had stopped working. 4. Yes, they are fixed. 5. Look at the attached jpeg. It shows where the cursor is reported to be by the locator. However, if I position the corsor over the middle of the Meta-Corection" button and press ctrl-space, the numbers in the dialog box are what I get and what works. At first, not knowing about the ctrl-space facility, I was using the numbers from the locator, and that, of course, did not work. macex.mex Meta-Correction Macro.txt

Because it will be fun to work it out. Actually, I'd like to send an SMS to my phone. Last night I ran into a new problem: The macro stopped working. It had been selecting the button (which is also a drop down), then preforming the drop down, descending two menu items and then pressing enter. As of last night, it no longer selected the button. I got a different set of coordinates from the locator utility. I changed them while thinking that something else must be wrong. Then the button was selected, but the arrow keys would no longer select the menu items. Frustrating. Does ME have any problems with memory leaks that could be causing this? I ran it on and off all day yesterday while developing and then a batch of live tests -- so it had about a 12 hour workout. That's more than enough time for memory leaks to start effecting calculations.

Thank you everyone for your advice and ideas. I have this macro nearly complete and running the way I want. I am fine tuning bits right now like adding in the estimated time to completion and reading setup data from files and so forth. (That's actually done but I am getting one odd number that needs to be debugged.) I've already used it to save a heck of a lot of time where I do not have to sit in front of the computer waiting for long process to end just so I can start them again. (Sound of hair being pulled out.) My next addition will be to find a way to tell Alexa to tell me that the macro has completed. I'm thinking email trigger or the like. I haven't explored this yet.