paul

I believe that is what I said when, in the message accompanying the code, I wrote "I wrote myself a DisplayPausing macro in ME3, before we had the ability to update an existing textbox. You'll see that it does indeed "change" the header, and I have never observed any performance problems with it."

AutoIt has a comprehensive user-developed library for Internet Explorer. AutoIt In the Help, look at User Defined Functions Reference (at the bottom of the left-hand panel) - IE Management.

Yes, it works. I set my wheel click to Ctrl-J, and wrote a mcro activated by Ctrl-J. When I clicked the wheel, the macro ran.

There are 2 possibilities: - have the mouse button generate a keystroke (preceded by Ctrl or similar), where the keystroke, e.g. Ctrl-X, fires your macro - have the mouse button run Meproc.exe You'll need to read the SetPoint documentation to see which of these is possible for your device (yes, I'm sorry, I know that reading documentation of any sort is sheer anathema to you, but it can't be helped).

I imagine that you need to configure the device using the standard Logitech software SetPoint.

I wrote myself a DisplayPausing macro in ME3, before we had the ability to update an existing textbox. You'll see that it does indeed "change" the header, and I have never observed any performance problems with it. // Timeout number of seconds If Variable %N[91]% Equals "0" Variable Set Integer %N[91]% to 10 End If // Display Pause dialog box for N91 seconds If Variable %T[99]% Equals "" Variable Set String %T[99]% to "the job in hand." End If Repeat Until %N[91]% Equals "0" Sound File: Windows XP Battery Low.wav Text Box Display: Pausing (closes and continues after %N[91]% seconds) Delay: 1 seconds If Window "Pausing (closes and continues after %N[92]% seconds)" is running Text Box Close: Pausing (closes and continues after %N[92]% seconds) End If If Not Window "Pausing (closes and continues after %N[91]% seconds)" is running Clear Variables Variable Save: Save All Variables Macro Stop Else Variable Modify Integer set %N[92]% to the contents of %N[91]% Variable Modify Integer %N[91]%: Decrement End If End Repeat <COMMENT Value="Timeout number of seconds"/> <IF VARIABLE Variable="%N[91]%" Condition="\x00" Value="0" IgnoreCase="FALSE"/> <VARIABLE SET INTEGER Option="\x00" Destination="%N[91]%" Value="10"/> <END IF/> <COMMENT/> <COMMENT Value="Display Pause dialog box for N91 seconds"/> <IF VARIABLE Variable="%T[99]%" Condition="\x00" IgnoreCase="FALSE"/> <VARIABLE SET STRING Option="\x00" Destination="%T[99]%" Value="the job in hand." NoEmbeddedVars="FALSE"/> <END IF/> <REPEAT UNTIL Variable="%N[91]%" Condition="\x00" Value="0"/> <SOUND FILE File="C:\\WINDOWS\\Media\\Windows XP Battery Low.wav" Wait="FALSE" _IGNORE="0x0007"/> <TEXT BOX DISPLAY Title="Pausing (closes and continues after %N[91]% seconds)" Content="Close this dialogue box to abort all further processing for %T[99]%" Left="1760" Top="467" Width="320" Height="84" Monitor="0" OnTop="FALSE" Keep_Focus="TRUE" Mode="\x02" Delay="2"/> <DELAY Flags="\x01" Time="1"/> <IF WINDOW Option="\x01" Title="Pausing (closes and continues after %N[92]% seconds)" Partial="TRUE" Wildcards="FALSE"/> <TEXT BOX CLOSE Header="Pausing (closes and continues after %N[92]% seconds)"/> <END IF/> <IF NOT WINDOW Option="\x01" Title="Pausing (closes and continues after %N[91]% seconds)" Partial="TRUE" Wildcards="FALSE"/> <CLEAR VARIABLES Type="Text Variables" Option="\x02"/> <VARIABLE SAVE Option="\x00"/> <MACRO STOP/> <ELSE/> <VARIABLE MODIFY INTEGER Option="\x06" Destination="%N[92]%" Variable="%N[91]%"/> <VARIABLE MODIFY INTEGER Option="\x08" Destination="%N[91]%"/> <END IF/> <END REPEAT/>

I'm running 3 monitors at 1280x1024. M1 is on the left, M2 is is the middle, M3 is on the right; M2 is my main display. So here are my numbers: Monitor Coordinates Macro Displays M1 -1280, 0: -1 , 1023 x=-1284, y=-4, WW=1288, WH=979 M2 0 , 0: 1279, 1023 x=-4 , y=-4, WW=1288, WH=980 M3 1280 , 0: 2559, 1023 x=1276 , y=-4, WW=1288, WH=979 The WH discrepancy for M2 is because M2 has the real taskbar, whereas M1 and M3 use Actual Windows Manager's taskbar, which is obviously 1 pixel too short. I believe MEP's window width is wrong - it's 8 pixels too large, though this also goes with the top left x value which always seems 4 pixels too low.

All irrelevant! We're trying to locate the cause of a problem, which is why you need to follow my suggestion. I'm not suggesting the increasing delays as a solution to solving the problem, but as a solution to diagnosing the problem. And in your tests with these longer delays, there's no need to run the "total displacement", but merely some smallish subset simply to determine if the problem goes away or not. If the timing turns out to be, say, 3 seconds, then increasing the delays from 1 ms to 10 ms is surely irrelevant!

Now try 1 second to 10 seconds and see if any work. If yes, then clearly moving a map imposes an intolerable load, and MEP is simply too fast for its own good (now that's a rare complaint, isn't it?).

I too always have UltraEdit on standby. Also Directory Opus.

Some disappointing news! A bug I've not seen for quite some time has made a re-appearance. With Macro Express (v4.2.2.1) dormant on my Windows 7 x64 system, I was running SUPER © to convert a single .mkv fi;le to .avi. Suddenly the conversion went into super slow mode, and the keyboard became very unresponsive. Yes, that old bug is back. I opened Task Manager (which took around 3 minutes to open), then I had to open a second copy of Task Manager; I then killed the process MacExp.exe *32 (this took another 3 minutes or so), and this made no difference; finally, after another 3 minutes, I managed to kill MEProx64.exe, at which the problem went away. This is exactly the behaviour I have always seen (I've always had to open Task Manager twice, and the elapse times are similar). What is different is that killing MacExp.exe did not solve the problem until I'd also killed MEProx64.exe.

I suspect that any kind of "solution" is going to produce the wrong answer one day, thus simply replacing one, perceived, "wrong" answer with another, real, wrong answer!

At times we are all faced with questions we are unable to answer. I believe yours is an example of this!

There is a new free utility that has recently been written which I believe may be of great interest to long-time Macro Expressers. It allows you to access any context-menu item directly from the command-line. Here's a simple example: Open Explorer, navigate to some Acrobat document and right-click to see the Acrobat context menu. This menu includes the command Print. Suppose you need to run this menu item from within a macro. At present, you simulate a right mouse click, then move down the menu as many lines as is needed until you reach Print, then left-click the mouse. And you have to write the ME code to do this. With this utility, you'd open a command prompt and run it with the name of your Acrobat document (you do this only once). This shows you the context menu, from which you select Print. The output from this utility now displays a command plus parameters to allow you, straight from the command line, to Print your Acrobat document, thereby avoiding the need for clicking and moving the mouse up or down from within your macro. You can now copy and paste this commanbd plus parameters into your macro. Take a look (it's the 17th utility listed) - Cautomaton.

But surely the kind of problem described here is common among [almost?] all languages? I am entirely unsurprised by the difficulties perhaps most ME users have when dealing with FP numbers (and I certainly don't exclude myself from their number) precisely because ME allows laymen users to do various things that some people would prefer restricted to the kingdom of the "computer geek"! When doing FP stuff with computers, rounding is a real problem, and cannot be swept under the carpet simply to protect the innocents.

I am strongly opposed to this.

I don't understand what you are saying. An hour on Google has yielded the statement that "Delphi uses Banker's rounding", which means that an exact half value causes a rounding to an even number. Please see this URL for some examples: My link The very first example given in this example exactly demonstrates my point! implying that, say, -1.5 will round to -2 (with which I entirely concur).

I'd be very interested to see any authority where rounding -9.600001 could ever produce -9.5!

Only in Macro Express Pro.

MEP Explorer Window - Options / Preferences / Email / SMTP Settings / Email Address

I'm surprised to read this. For a while I was using RDP extensively inder XP since my development machine was remote, and pressing Win-L always locked the local workstation (and I don't know whether the remote one was locked or not).

DIsable/Enable Lock Workstation

How many times in the last 2 years or so must Terrypin have felt the same, I wonder? We were always telling him his problems were unique, so it must be his machine!

UltraMon! UltraMon

You'll need to use AutoIt or VbScript to get the handle of Macro Express, or the application you wish to control, e.g. Excel, then use the Windows API to invoke LockWindowUpdate twice, once to lock and once to release.