chris

I've managed to fix the problem with the debugger pane. The variable values pane was getting messed up because you were using [%Index%] as a part of the variable and we weren't taking that into account. The next build has this fixed. As for the clipboard speed in Writer, please go into MEPro's options > Preferences > Playback > Delays and double-check your "failed clipboard commands" delay. I would recommend setting it no higher than 250 ms. If the clipboard can't be opened by MEPro (because Writer still has it locked), then MEPro will wait for the specified time before trying again, up to five times. This might help you out. Also, make sure that you're not using this in the debugger as there is more information being passed back and forth between the debugger and the player (unlike in ME3), so it's a tad slower that way, too.

That's correct. Now, the only limit is the amount of free memory you have on your system.

Just to let you know, this was a bug as the dialog box wasn't supposed to disable the OK button. It has been fixed and will be available in the next release.

Yes, it is a popular request. So popular that it is on our list of things to do for a future upgrade (it's actually quite high on that list).

It turns out that we had the code to handle the swapped mouse buttons, but we missed the code to turn it on (this was my fault). The issue has been fixed and we're planning a new release probably before the end of the year.

When you open a macro with MEPro, it will convert the macro into MEPro's format. That means that there is no way to use it with ME3 once converted. If you need to continue using an ME3 format, you need to edit it with ME3. Currently, there is no "Save As" feature in any version of Macro Express. So, in the explorer, you'll have to do a copy and then edit whichever copy you like.

Regarding your second issue (the category conversion), I was wondering if you had a backup copy of the file that you encountered this issue with. I'm trying to create a fix for the program because it should have brought your categories over during the conversion and therefore making it not necessary to recreate your categories. The reason your macros are automatically jumping into the categories when you create them is because that information is being preserved, but for whatever reason, the categories themselves didn't get imported. If you have a backup of the file, I was wondering if you would be willing to send it in so that we can test it and see if we missed something during the conversion process.

The capability for gestures doesn't exist, yet. It is something that is being researched, though.

Not at this time. Sorry.

One other thing to consider is that SDL generally uses the DirectInput interface (the input mechanism for DirectX) on Windows machines. So, getting it to work in VBA SDL is not really the same as getting it to work in Macro Express as DirectInput bypasses the hooks completely.

Technically, it doesn't support wildcards. However, since we used Delphi to create the program, there's a little "flaw" that will allow you to use a wildcard in the If File Exists command. When checking for the existance of a file, Delphi uses an API that accepts wildcards. That's why it appears to work in Macro 3. That said, I can't guarantee that this will be workable in any future version of Macro Express. It depends entirely upon whether or not the Delphi framework uses a different API to test for the existence of a file.

So, if I understand you correctly, you want to select a file in PowerDesk and have Macro Express recognize it (presumably using a hotkey), get the selected filename and then upload it to your FTP server? If so, the only thing I can see potentially being a problem is getting the information from PowerDesk. The first thing I would do is try to copy the file to the clipboard (using Ctrl+C). If this copies the full filepath into the clipboard then you can do the rest using Macro Express pretty easily. If it doesn't copy that information to the clipboard, then we have to figure out how to access the filepath differently.

It's due to a bug in the application. I'm getting it fixed right now. Here's a fixed version of the command for you. If you'll notice, the only difference is the %T1%|%T1%; code has been changed to %T1%; <TVAR2:01:01:cory@bluepointdesign.com; cory_jackson@sbcglobal.net><EMAIL2:Center:Center:Center:Center:Center:Center:RNR1TO%T1%;S1TestA1>

If you don't want all of the users to share the same settings (i.e. window positions, current macro file, etc.) then you'll need to adjust one preference. Go into Options | Preferences | Miscellaneous and uncheck the "All Users use Same Settings" option. With that cleared, each of your users will be able to set up Macro Express in any way that want, without interfering with the other users on the system.

The TerminateProcess command will only work with one instance of a program. If you have multiple instances, then the best way to shut them all down would be to use a scrip like the one I've included below: <IVAR2:01:01:0> <REP3:08:000001:000002:0001:0:01:1> <IFOTH:06:1:PROGRAM.EXE> <TERMPROC:001000:1:F:PROGRAM.EXE> <ELSE> <IVAR2:01:01:1> <ENDIF> <ENDREP> I've placed each command on a separate line for readability only. If you copy and paste this code, you will get several TextType commands scattered throughout the script. Just remove them and you should be set.

Sometimes, the shortkeys buffer can get "clogged" up. Macro Express does have a way to clean it up by simply pressing the control key a couple of times. Does that work at all for you?

The problem is that even though Internet Explorer is renamed, the program is still there and is integrated with the system. In fact, the InternetGetConnectedState API is contained in a DLL provided by Internet Explorer 4.0 and later. Within Windows, there is no way to completely remove IE. Even with programs that claim to do so, they can't remove every single piece. So, even if you don't use it, it is constantly affecting your system. This is one of the reasons Microsoft got in trouble for bundling IE. It's just tied too much into the system.

Make sure that your time zone settings in your board control panel is set correctly. Go to "My Controls" -> "Board Settings" and you'll see the time zone information at the top.

Typically, this is a result of the program you are running this on. For example, if you run a shortkey in RoboHelp, this happens. ShortKeys (another program from Insight Software that just does text replacement) has this problem in Word. What's going on is that the backspace is occasionally missed by the program, even though Macro Express is sending it. We have been looking into this for a while with limited success. It seems that the main problem is that the OS wasn't designed to accept keyboard input (simulated or otherwise) at speeds that Macro Express is capable of putting it out at. That's not really a fault of MS, either, as the OS has a lot to do in the background that can cause this. Rest assurred, though, that the problem is known and is actively being worked on.

The InternetGetConnectedState API (which Macro Express is using) can report a false-positive under a certain circumstance. I don't know if you've ever seen this, but Internet Explorer can work in offline mode. What happens is Internet Explorer detects that there is no connection and will either attempt to dial-up the connection or it will ask you if you want to work in offline mode (depending on your settings). If you select offline mode, all* internet-enabled programs will act as though the internet connection is there, but they won't be able to get out to the internet. You can check this out for yourself. If Macro Express is reporting that you are online when you are not, go into Internet Explorer and click on the File menu. If there is a checkbox next to "Work Offline" then all* of your applications (including Macro Express) will believe that there is an active internet connection and work accordingly. I hope that this helps. It is frustrating, isn't it? (* All programs that use InternetGetConnectedState will be fooled. Those that detect it by other means may not. However, most programs use this API as it is what Microsoft HIGHLY recommends to programmers).