Cory

Since it's a virtual window I don't think what you think is the title is that for the system. I'm guessing MEP is seeing the correct window title which is hidden. The window title you're seeing is the one runnon on the virtual server. If that's the case, then you will not be able to access that string of characters. Activation using that code will not work. acantor: calee showed what that string is in a prior post. It had "Remote" at the end of it and the string is not visible. (what is it with lower case these days... 🙂 ) I think your best bet is to find something that has that code available and can be collected. I would use a control like the one you mentioned where a barcode was also visible. Trigger the macro on the appearance of that control, collect the text from that control, evaluate it for the desired sting, and if apparent issue the warning or whatever you want to do. Note that all but your annunciation at the end will be instantaneous and invisible to the user. My concern is that a virtualized app is probably just graphic depicting the app running elsewhere. There might just be one big control showing a graphic. Like a video player. When you click on a button, you're actually just creating an even to send a click to the remote app at that coordinate. All your inputs are being executed by proxy. If so, MEP will not be able to access the real control on the server. However sometimes there will be a pass through for printing, file savings, and clipboard, just like in a VM or remote control app. If so you could use the VM apps invisible title as activation, then do something with the keyboard or mouse like Ctrl+A, or click on a coordinate to highlight the text in the remote control, fire a Ctrl+C at it, and then have it copy and transmit the text to your local clipboard for evaluation. There might be some delays so I would start experimenting with at least 100 ms delays between steps then reduce them as far as reliable. If I were you I'd first see what the MEP Windows Controls commands identify with the picker tool and then see what text I could get from there. Also it will show you want to local (accessible) window title is. In this graphic you can see the title of the window for which control I was selecting was "Macro Express Pro - Script Editor [Test]:". Show us what you find if you need more help.

Remote... This sounds like it's a virtualized app like VMWare's Thinapp. Like a VM (virtual machine) but for an app. If so, you're not really in the app. This is a program that essentially gives you a window into an app that's running on a server someplace, typically the cloud. Is this the case? You might want to look and see what the name of the actual process is with Process Explorer or Task Manager. Is this the case?

I changed the window title of my sandbox app to that from the OPs sample and scripted MEP to get the topmost window title and it works fine. But it still could be that the OP typed in the text as opposed to capturing it losing something like a Unicode character.

Can you capture the title of the window by another means? If we can I can make a simple app that used that text which anyone can test with.

I doubt it as the break is happening in the middle of a string of numerals. But there are some. Like a zero with a slash through it. Also unicode extended characters just use two bytes where MEP decodes them one byte at a time. So one typically sees two garbage characters then it continues. Aside: I have successfully used MEP with Unicode by employing some replacements as a workaround.

Is it unicode?

If it's a normal Winform window one can probably get all the text easily using the Windows Controls commands in MEP and launch a warning if the control text contains the code. You could also use the control as the activation. This would all happen in a few milliseconds and invisible to the user if one didn't pop up a message. I could also imagine one could save a graphic with the clipboard and do something with it.

That is strange. I'm sure it's not an MEP militation, but it's odd that it can't get the whole title. Like I said, it might be that the 8 is a unicode character or something like that. Are there any other controls on the window? Like a status bar at the bottom? THen you could do as rberg suggested and have it invisibly check that for the ID you want to have trigger.

If anyone wants, I can create a simple WinForm program which will set the window title to whatever they specify in a text box for testing macros.

Testing. Using the Set Variable from Window Title did not truncate the long window title. I used Repeat With Windows command and the long window title was not truncated as you described. Again... GIve us an sample of the title which is failing. I also recommend you make a small macro to grab the text of the top window and display it in a message box to see for yourself.

I found an answer that WinForms support Unicode.

I created a WinForm app and set the windows title to "This is a super long window title and I can't imagine any developer making it longer than this This is a super long window title and I can't imagine any developer making it longer than this This is a super long window title and I can't imagine any developer making it longer than this 1234321" And made the activation for a window title containing text 1234321 and it works fine. I suspect you're jumping to conclusions that MEP is limiting it depth of characters searched. I believe your problem is something else. As rberg said it would be more helpful if you provided the actual text. One though I had is perhaps the title contains unicode characters. MEP processes unicode data as if it's ASCII and is difficult when the character is an extended one.

You're welcome.

I would use Variable Modify Date/Time, Options tab, Add option, Integer or Value, enter 65, then select minutes.

The number of minutes in a day. Date/Time is at its core a decimal. 1 = 1 day.