kevin

Oh, it exists. We just aren't going to advertise the fact yet.

When a new version of Macro Express Pro is released we announce it on this forum, via email with the Macro Express News email newsletter and with an RSS feed. We always wait one business day to announce so we can find out from a smaller audience what problems there may be. So far Macro Express Pro v 4.1.1.1 has two issues that are serious enough that we may decide to hold off on the announcement until we determine how to resolve them. So, this is NOT an announcement that Macro Express Pro v 4.1.1.1 is available. We want to add an automated update feature but there are other issues that have taken priority. (Non-sticky settings and crashes when Variable Restore command used, for example.)

When Macro Express Pro crashes, it brings up a separate program, the ISS Bug Reporter. The Bug Reporter collects information about the crash and offers to send it to us using one of 4 methods. Please, please, please, when you get a crash, send us the information. The crash report includes information about what the program was doing when the crash occurred. "But," you might say, "it is easy to duplicate the problem. Just try it." Well, that doesn't always work. Often you get a crash and we don't. (Why do you think the problem slipped past our Q/A people? ) Once you set up the ISS Bug Reporter it is easy to send subsequent crash reports. Please help us improve the quality of Macro Express Pro by sending us the crash reports.

When Macro Express Pro crashes the ISS Bug Reporter is launched and offers to send information about the crash to us. Have you seen the ISS Bug Reporter? Have you sent the crash reports? Please contact Insight Software Solution's support people. See the Contact Us page for contact information.

To move the mouse to the coordinates %N[1]%, %N[2]% use the Mouse Move: %N[1]%, %N[2]% Relative to Current Window macro command.

To understand Windows Controls look in the Macro Express help. When Macro Express Pro is installed a macro file with samples is installed in the Program Files folder. Open c:\Program Files\Macro Express Pro\samples.mex. Depending on which version of windows you are using or its configuration you may not be able to run the macros from the Program Files\Macro Express Pro folder. If that is the case then you can copy the file to your My Documents folder and then open it from there. You can also download the sample macros from our Sample Macros web page. The sample macro that Cory is referring to is named 'Calc ulator and Note pad' (note the extra spaces). By looking at this macro and reading the help you should have a pretty good understanding of how to use script commands that interact with Window Controls.

Push Button Marketer uses an OEM version of Macro Express 3 named Macro Marketer. It is not based on Macro Express Pro.

Use the Text File Begin/End Process commands like this: Text File Begin Process: "test.txt" // Add macro commands here Text File End Process A sample is shown in the help.

To move a folder from one location to another on the same drive use the Rename File or Files command. To copy a folder use the Copy File or Files:. To delete a folder use the Delete Folder. To move a folder from one location to another on different drives combine the Copy File or Files: and Delete Folder commands.

What were you typing before the shortkey before you tried the technique of typing a space before the shortkey? This is the critical piece of information for us. If you type 'zuaBc ' and your shortkey macro doesn't activate, that is an unknown bug and we want to know. If you type '<Arrow Down>aBc ' and it doesn't work then that is what we already know about and have fixed. If you type something else before the 'aBc ' and it doesn't work then we want to know. Perhaps because you never contacted support to ask about shortkey issues?

To Alexis, Terry and all others who are reporting that their shortkey do not always work: What shortkeys settings are you using? 'Use Prefix' or 'Use Suffix'? When one of your shortkey macros doesn't work, take a moment to think about what you did immediately before trying the shortkey. See if changing what you do allows the shortkey macro to work. This moment of thought followed by your description of what happened can help us find and fix any problems. Macro Express Pro needs to separate out the 'shortkey' from all the other typing that is going on. It uses one set of rules to do this for the 'Use Prefix' option and another set of rules for the 'Use Suffix' option. This can be complicated. I have typically used the 'Use Prefix' option. After reading posts in this forum where people report having trouble with shortkey macros I switched to 'Use Suffix'. After several days of use one of my shortkey macros did not activate. I stopped and thought for a moment about what I did immediately prior to typing the shortkey macro and realized I had just typed one of the Arrow keys. If you type an arrow key immediately prior to the shortkey activation then the shortkey will not work. This has been fixed and will be available in the next release of Macro Express Pro. The next time your shortkey fails, try typing the shortkey again but with a space in front of it. For example, if you type <Arrow key>'aBc' and your macro does not work try typing <Arrow key>' aBc'. If this works then you are experiencing the same issue we have discovered and fixed. If that does not explain what you are experiencing then please, just after a shortkey macro fails to activate, take a moment to think about what you were doing and see if you can repeat the problem. Then report the results to us. Here is one more thing to try. When a shortkey macro fails to activate, press and release the Ctrl (or Control) key and try typing your macro again. Pressing the Ctrl key tells Macro Express to empty the shortkey buffer. This 'kick in the pants' helps Macro Express Pro determine when a shortkey is being typed.

The Windows API's have some kind of visible property. We may have chosen the term 'hidden'. The windows shown are all reported by Windows. Macro Express Pro does nothing other than request the list of windows via the Windows EnumWindows API (may not be the exact name). It may be that Stilletto is only listing visible windows. Nonetheless, the list of windows you are seeing is the list of windows reported by Windows itself.

Cory, this is interesting. I am working on a computer right now that has many funny symptoms. But it is scanning clean now. Maybe it is time to reformat it. Do you find that Vista is less susceptible to malware than XP?

As I said: Macro Express Pro does not keep a list of windows. When you ask for the list via a macro command, Macro Express Pro asks Windows for the list of windows. The list is not held in a file, a cache or registry keys. Do you have another program that enumerates the visible and hidden windows currently running? If so, tell us what it shows.

Macro Express Pro gets the list of windows, both visible and hidden, from Windows. Do you ever turn off your computer? From your description it sounds like you leave it on for weeks at a time. Personally, I turn my computers off each night. As Macro Express Pro runs it requests memory from Windows (alloc). Then, when finished with that block of memory, it tells Windows it no longer needs that block (free). Windows frees up most of the memory but with each alloc/free cycle Windows keeps 16 bytes flagged as used. Depending on the commands used in your macros and how often they run, over time the accumulation of 16 bytes blocks adds up and starts to affect your computer's performance. When Macro Express Pro is closed, all memory is freed. We recommend that you periodically restart Macro Express Pro (if not your computer). A scheduled macro that runs at 2:00 am containing the Restart Macro Express command will do this automatically. To be on the safe side I would run this daily but you should do this a minimum of once a week.

If you click on the downloaded file then it will execute. Instead, from within the Macro Express Editor, click File, Import, Import Macros, Import a Playable Macro. This will import the macro into your existing macro file so you can view it.

It would be fairly easy to have Macro Express email the fax as an attachment. The only difficulty that I can see would be in determining who the fax should be sent to. As a simple first stage you could write a macro that displays each fax one at a time and a person could choose the recipient. Then the macro could email it to that person. Later you may be able to open the fax in some kind of OCR program to grab the recipient.

Yes, both Macro Express and Macro Express Pro will be updated.

Until now I have stayed out of this discussion because this is a 'user' forum. I do have an opinion about one thing. When I see macro script or macro code that is not contained within code tags, I give that topic less attention and, depending on how much time I have at that moment, I often stop reading right then. It is the user's choice whether or not to use the code tags but if you want me to read the issue you should use code tags (for both macro script and macro code). Just sayin. The 'codebox' '\codebox' tags have the horizontal scrolling bug but the 'code' '\code' tags do not. I have at times edited someone else's codebox tags to code tags to make their post readable. It seems that the point of this entire topic can be summed up this way: You are asking others to spend their time and effort to read, understand and respond to your issue. You should make it as easy as possible for them. The more effort you put in, the more effort we will put in.

Macro Express Pro has Lock Keyboard and Mouse and Unlock Keyboard and Mouse. There are no plans at this time to add this to Macro Express. All variables are passed from one macro to another when they are run via the Macro Run command. To make variables available between macros that are not executed via the Macro Run command requires that you save them to a file, the registry, or via the Save Variables and Restore Variables commands.

These descriptions sound like two symptoms of the same issue. This is the first report of this behavior. We are working on a new version of Macro Express that contain changes to improve compatibility with Windows 7. We will look into the issue. At this point we do not have a time frame for this new version. Questions regarding this new release should be directed to the Insight Software Solutions support people. See our Contact Us page for contact information. Bug reports, including issues introduced by Windows 7, should be reported via our Report a Bug web page. You can also access this by clicking the 'Support' link from within Macro Express itself (Help, On The Web, Support) and then clicking on the 'Report a Bug' link.

We are working on a new version of Macro Express that will interact with 64bit programs. It will also contain changes to improve compatibility with Windows 7. At this point we do not have a time frame for this new version. Questions regarding this new release should be directed to the Insight Software Solutions support people. See our Contact Us page for contact information.

I'm sorry. The discussion in this thread regarding importing preferences seemed to me like the topic in another thread started by you that discusses importing preferences. My mistake.

We are not sure what is causing the slow down. We have 'officially' asked questions on the forum to try to get more information. We do not have any news at this time other than we are working on the issue.

Repeating the same problems in multiple posts will NOT help resolve the issue. Please confine your discussion of each problem to a single post. This is a 'User' discussion forum. If you want an official response from Insight Software Solutions, please contact our support people directly. Our contact page has the telephone number and email address for support.