mfseeker

I have a Linux box (Debian dist.). I would like to be able to run my ME Pro on it using VirtualBox with a Windows 7 virtual system. ME runs, but none of the activation options work.

I know this is a big topic, but, thanks to Terry, I have been investigating PowerPro. What incredible flexibility! It is overwhelming at first. Before I go too much further, I would like to know whether I am going to get into peculiar situations because I am trying to use both MEP and PowerPro. What determines the order of activation precedence between PowerPro and MEP? Is it simply a matter of which program stars first? Do both absorb the activating event (such as a hot-key or window activation), or do they pass the activation through to the other program? Do the different sorts of activation event exhibit the same precedence behaviour? "Restore Keyboard and Mouse Hooks" will force MEP to have precedence for keyboard and mouse events. Does that command work to give priority to MEP over PowerPro? Is it always necessary, if that is what you want? Is there any way of reversing the precedence of the two programs? What about non-keyboard/mouse activations? Do they establish precedence differently? Of course, I could do a whole bunch of tests to answer these questions, but if someone already knows the answers, I would just as soon spend my time trying to gain a minimal mastery of PowerPro.

Yes, I am using ME Pro. Here are some quick results: ME Pro, Clipboard Empty Method, 100 loops: 250 ms (default) ==> 21 s 10 ms ==> 1.5 s 0 ms ==> 15 ms I would guess this is a very significant issue for many of us. At the least, developers should be made aware of it. More study seems to be called for. When do we really need delays? The price paid for using a 250 ms default delay, so as not to have to introduce delays on a case by case basis, seems rather high. I have recently completed my "Toggle Text Case" macro (emulating Microsoft Word's Shift/F3 command). Using the default 250 ms, there is a noticeable delay in the execution of the macro. With the 0 ms setting, the macro is perceptually instantaneous. However, it also runs erratically, sometimes succeeding, sometimes failing.

That would be great, Cory. So far I haven't graduated to designing large macros, but even in smaller macros there are occasions where we are working in loops with many reps such that timing info becomes important.

Right. I knew that. Sorry for the slip Cory.

Thanks Terry. I didn't think to scroll down the selection box, so I missed this option. Stan

I didn't get that result. I timed a loop of 100 reps of Clipboard Empty at 21 seconds. I timed setting T1="", then writing T1 to the clipboard in a 100 rep loop at 25 seconds.

MEP lets us measure seconds using the “Variable Set Integer %timeNow%: Set to the Current Second” command. Is there any way of measuring milliseconds--by accessing the Registry, perhaps? I have searched both my Registry and these forums to no avail.

A short piece of code can be saved either as a snippet or as a macro. If my macro uses that piece of code in several places, am I better off calling it as a macro or inserting it from a snippet? If I insert the code from a snippet, I can give users one macro rather than two. If I call the code as a macro, does it take significantly longer than the inline code?

Scasper, As far as existing macros are concerned, you will have to do it manually. However, there is a simple solution for the future. Whenever you think you might need a variable in other macros, use Save to Environment Variable under Variable Modify String. Such values can then be read into any future macro by Set from Environment Variable under Variable Set String. Did I say this was simple? Well, not quite. You do have to remember to save these variables whenever their values are changed by a macro that you want to allow to change them permanently. These will all be string variables, so if you need other types, you will have to convert them when you read and write them. Of course, you could also achieve the same thing by using a text file, provided you remember the file's name and location. Stan (mfseeker)

I'm sorry. Allthough I boarded the Macro Express bus back in 2004, I have been inactive until recently, so I do not know how to submit a support incident. On the ISS site I find forms for reporting bugs and requesting features but nothing about "support incidents". Do I just send them an email? If so, should I mark it somehow as a support incident?

My OS is XP. I hesitate to trouble ISS with a report if I am the only one who can reproduce it. If the glitch is idiosyncratic, I don't want them to waste time on it--especially now that we have so recently benefited from all their good work in bringing us the new update. Stan

Well, the restart in safe mode yielded no improvement.

Yes, I am on 4.0.1.1. Yes, "Switch Focus" is enabled. I am not using any other clipboard utitlities. My system is a 2.8 Ghz P4 with 3GB of RAM. It is very responsive. Adware infection is doubtful. I am using the new Norton. It seems to do a good job on adware. I have tried half second delays before, after and throughout. No help. F9 fails too. But now, suddenly, F9 does work, but F7 still fails. Inserting one second delays doesn't help. I will now restart in safe mode, as you suggest.

Rest In Peace lovely, useful filter.

With the new update, I can no longer figure out how to invoke the filter capability of the Variable Values (Debugger).

This is odd. I have a macro that copies a phrase from a text to the clipboard. It does the job when I run the macro, but when I try to step through the macro with F7 the clipboard remains empty. Changing the delay pref or inserting delays doesn't help. Try this with any text processing program (Notepad will do) containing some selected text. Try first with F7; then run it with Test Run. You might want to empty the clipboard first between runs. <CLIPBOARD COPY/> <VARIABLE SET STRING Option="\x02" Destination="%TestText%"/> <TEXT BOX DISPLAY Content="{\\rtf1\\ansi\\ansicpg1252\\deff0\\deflang1033{\\fonttbl{\\f0\\fnil\\fcharset0 Tahoma;}{\\f1\\fnil Tahoma;}}\r\n\\viewkind4\\uc1\\pard\\lang4105\\f0\\fs16 Here is the text from the clipboard:\r\n\\par \r\n\\par %TestText%\\lang1033\\f1 \r\n\\par }\r\n" Left="Center" Top="Center" Width="278" Height="200" Monitor="0" OnTop="FALSE" Keep_Focus="TRUE" Mode="\x00" Delay="0"/>

Thanks for explaining this further and for looking into the code again. Nevertheless, it is really annoying to have to keep waiting for it. I just tested again with no windows open except the macro editor window itself. The delay seems to be just as long as when several windows are open. Perhaps this will be of some use to you in fixing the problem. Stan

Well guys, I have egg on my face. I discovered what was causing the delay in the execution of my capitalization macro in Open Office Writer. The activation I had chosen was Shift/F5. For some reason in Writer, and only in Writer, I was not releasing the Shift key for five seconds after I pressed the combination. So long as the Shift key is depressed the macro's execution is delayed. I have verified that I can get the same delay in any editor and that I can eliminate it from Writer simply by promptly releasing both keys. I am sorry to have caused needless fuss. I can only hope my folly is of benefit to someone else. I did learn a lot along the way. Thanks especially to Cory and Chris for furthering my Macro Express Pro education.

I can report the same problems Terry is having with the F9 delay. The delay also occurs with F7 and F8. Chris, your answer that the problem is "due to the fact that MEPro is querying all of those windows for their titles" can't be right because, as Terry has reported, the first time I run F9 there is no delay. I also checked my processes and found the failed attempts to "Enable Autodial" at the rate of about two per second. Does this have anything to do with the fact that I have not yet upgraded my license to Macro Express Pro?

I am not running it in the editor. In fact, the editor is closed. In Open Office Writer the macro takes about five seconds to change the case of the selection, regardless of the length of the selection. In other programs (this reply editor, for instance), it is almost instantaneous. The "failed clipboard commands" setting was the default 250 ms. I reset it to 100 ms. That made no perceptible difference in the delay. Cory, I am copying the selected text to a string variable, processing it, and then pasting it back into the original document. When the text is being converted to Title Case I am using your macro. When the conversion is to lowercase or Uppercase, I am not. All three cases show the same five second delay.

Thanks for the leg up, Cory. Well, my macro is finished. It recognizes the case of either a selected word/phrase or the word in which the cursor is located, and it replaces lowercase with Title Case, Title Case with ALL CAPS, & ALL CAPS with lowercase. I have avoided arrays, and in the conversion to Title Case I have used a slightly modified version of your macro. Unfortunately, my dream of creating a macro that would work in any text editing application has faltered with OpenOffice Writer (my primary application). My macro works there, but it takes too long. For every other application I have tried (including Microsoft Word, where it is superfluous), the replacement is virtually instantaneous. For Writer, it takes several seconds. If anyone wants the macro, I could make it available (of course, with your permission to use your macro). I notice that you posted your macro on your site. Lacking a site, as I do, what it the best place to make our macros available to others? Stan

Does anyone know where to find documentation for the Variables Values Debugger. This is a wonderful feature, but mine doesn't seem to work properly. It shows me some values as they are set, but not others. Specifically, it doesn't show array variables that are set within a Repeat. I would also like to know how to get the filter feature to work consistently.

Aha! The problem seems to have been with my debug variables display. The value of StringText is displayed properly by the Variable Values Debugger, but it does not display the Letters array values as I step though the repeat. Your addition of the Text Box display revealed that they were being correctly set. Maybe you are not the only one who has a broken debug pane. Thanks for alerting me to the proper use of the CODEBOX. I haven't been on this forum since 2004 when I did my last serious work with Macro Express. Yes, I have a bunch of words to which I do want to apply a capitalization rule. Uppercase and lowercase are easy. Its Title Case that is responsible for my contortions. I'd welcome a better way to do this--or anything else, for that matter. Thanks again. Stan

I'm not sure whether you are asking me for the code of the test snippet or of the actual macro I am developing. The test snippet's code is: <VARIABLE SET STRING Option="\x00" Destination="%StringText%" Value="some words"/> <REPEAT START Start="1" Step="1" Count="10" Save="TRUE" Variable="Index"/> <VARIABLE MODIFY STRING Option="\x09" Destination="%Letters[%Index%]%" Variable="%StringText%" Start="%Index%" Count="1"/> <END REPEAT/> The actual macro will emulate Microsoft Word's capitalization command (normally triggered in Word by Shift/F3) for use in non-Word applications. Most immediately I want to use it in Open Office (though I don't want it restricted to that ap), because I am trying to wean myself from Microsoft. If you want the script or code as it stands now, I can send it to you. Thanks for your help. Stan