paul

Yes, I now realize you are/were missing the menu bar immediately below "Macro Express Pro - Explorer", comprising the options

File Macro Category Search Options Tools Help

and I have no idea how to recover that! Needless to say, I don't know why it disappeared, and I don't seem able to replicate that behaviour on my system. Sure looks like a bug to me, which you may care to report (I presume you are using the latest version of MEP - i.e. 4.1.7.1)?

Works perfectly for me under Windows 7 Home Premium.

BTW, I suggest removing the " - untitled" portion of the window name, leaving it simply as Notepad.

Options / View

Make sure both Toolbar and Sidebar are ticked.

What a nonsense this is - can anyone name a single application where View is located under Options? Has Insight never heard of any Windows standards?

Note that the wait for IE webpage command is not 100% reliable, either. JavaScript and AJAX appear to throw off the timing. So even when I script for IE, I am usually forced to add a time delay.

AFAIK, the AutoIt IE code does handle javascript correctly. It's certainly very comprehensive.

As my Dad liked to say, "You learn something every day." He forgot to mention that sometimes you feel really dumb that you hadn't figured it out already.

Actually, I don't think there's any such thing as a dumb question! And why should you have thought of Alt+spacebar - it's not exactly obvious!

IMHO, definitely a bug (or even two bugs) you should report.

Oops! I was using the "Launch Program AND Activate Window: command, which works.

But you're quite right - the "Activate OR Launch" command fails as you described. Sorry about that.

BUT if you tick the wildcards box, it works!!!

Even AutoIt has no code for Firefox, whereas they have a comprehensive set of functions for IE; so the answer is almost certainly No.

Works fine for me (even with itune as the partial title).

I know exactly what the problem is! It's God's punishment for going over to the dark side (Apple)!!

Thanks. However the database I am using does not have a COPY right-click. I use ACT! for contact management and it does not have a right click copy. Besides it's not as elegant/smooth.

Instead of a right-click context menu, is there a menu option under a top-level entry called, say, Edit?

Once you have selected your text, how about getting your macro to do a right-click and then choose the Copy option? Would that work better?

Paul, ...

Are any of the issues you are interested in included in the many changes released last week?

Only one - "Made a change to keep the running man icon from staying in the system tray after the macro has terminated."

The major one of variables not working in "Run macro from a variable" is not mentioned, nor the one of the display in the script editor of available macro commands being garbled. The first of these was reported in March. Perhaps the second, reported in January, is fixed by your "Fixed a bug where the command pane could get confused and displayed the wrong information." - I shan't know until I can escape from the UK (what a horrible place it has become in the 20 years I've been away!) back to Oz.

I submitted this as a bug. Gosh I hope they fix this.

Well, I don't see why you think you're so special!

I have submitted several bug reports for MEP in the last few months. Initially I'd get a confirmation that they've received the bug report. But never another word! I suppose I have up to half a dozen outstanding bugs, and no evidence of any further interest on Insight's part. And some of these bugs are serious ones, for example the inability to create a macro in a variable and then run it when the macro refers to any variables other than %t[n]%, %n[n]%, etc.

My impression is that Insight has bitten off more than they can chew, and have essentially given up on producing a product that compares in any way with its predecessor for speed or reliability.

Have you tried moving your mouse over the ME icon in the tray? That should provide the name of the currently running macro (try it when you next see that text box).

Take a look at something I published earlier. You need only download the utility linked to in the Shutdown URL at the top of the page.

Waking a machine up

The reason you're getting this is, I suspect, that the first reference in your macro to %N72% lies in a command where ME assumes a text variable.

Now, MEP comes with some variables predefined, and I suspect you're trying to use the integer ones. Where you are trying to address a non-array variable called %N72%, what MEP predefines for you is an array variable called N with 99 "slots", as in %N[1]% thru %N[99]%. So you should be naming your variable %N[72]%, at which point all should be well. And I'll bet you have a text variable called %N72%, which you can delete.

MEP has many problems with variables, and Insight doesn't seem to fix or even recognize any longer.

How about add an option to set random variables to not repeat the last X generated numbers in a row? Useful for making some random things seem more random. Or when we need to create non consecutive numbers.

The moment you try to alter what the next random number is, it is obviously no longer a random number. Oh for some clear thought!

any idea what index numbers are good for? macro express 3.x didnt have them. why are they in 4.x?

If you don't know what they are used for, then:

1) Why do you want to know whether you can change them?

2) Why do you even care about them?

I don't see the point of asking questions about a feature you never had in an earlier version, and whose purpose is unknown to you.

You know what? If you ask questions about such esoteric features, then I suspect most forum members are going to ignore not only this type of question, but also others from you which might have more purpose!

The Professional version of Macro Express has the ability to watch designated folders and run macros when files are deleted, added or modified. Alternatively there is a utility which will do this for you.

Folder Monitor

When you invoke the 2nd macro (via a Macro Run command), you are not running the version of your 2nd macro open in the script editor.

My technique for resolving this is to include the code of the 2nd macro in the 1st macro while testing.

ASCII File Begin Process: "xx" (Comma Delimited Text (.csv))
...
ASCII File End Process

The 3 dots in the above example represent code you write to process the contents of the T variable, i.e. %t[1]% contains the first value of your .csv file, %t[2]% contains the 2nd value, etc. Each time your ... code is executed, MEP moves to the next row in your file. Thus, in your code, you need to display your form each time as if for the 1st time - if you have 10 rows of 5 values in your .csv file, then your form will be displayed 10 times, and you will be using variables %t[1]% through %t[5]%. You will need to insert code to detect when your form is closed each time (use a Repeat command to test when your form window has been closed) so that you can process the edited values (if applicable), and then have MEP display the next row of data.

An alternative (better?) method might be:

set string t10 to your gappy string
repeat until n1 <> n1 -- endless loop
 set integer n1 to the length of variable t10
 variable modify string: replace "  " in t10 with " " --replace all instances
 set integer n2 to the length of variable t10
 if n2 = n1 repeat exit --because nothing changed, we're done
end repeat

Just for fun, I wrote a macro to write all the pixels on my 1280x1024 screen to a file. I then rewrote the macro in AutoIt.

MEP takes 3.5 minutes to run, while AutoIt takes 2.25 minutes; so AutoIt is not that much quicker in this case.

%N1%, %T1%, %D1% are the only arrays available for Macro Express 3.x. You cannot specify %N[1]% in ME3; you're probably thinking about Macro Express Pro.

That would be because this is a Macro Express Pro forum, and I don't expect to find ME3 messages in it!

I heard rumor that there will be no more development of AutoIt. I haven't tried to confirm, however.

Here's the word:

"What I know is that there is a tiff between a couple of the AutoIt developers and it has not yet been amicably resolved. It may not play out well, but I think it is too soon to say. They may work it out and there may be others who can fill the shoes. Not pleasant at the moment, but I don’t think that development is doomed by any means at this point."