I have not changed RP_WAIT from it's default setting.

The program is already running when the script is launched. I am sure this is probably something peculiar to the program and not a fault of MS.

I will post a log file later but just to clarify. the export process is like rendering an image (except that we are dealing with audio). When the export dialog is open and the button "Export" is pressed then the export begins. Sometimes there are other dialogs that appear after the button is pressed...

This is odd: In my script I have a command that works perfectly: WaitWindowOpen>Export Audio Mixdown* PushButton>Export Audio Mixdown*,Export WaitWindowClosed>Export Audio Mixdown I needed to insert some stuff after the "Export" button had been pressed (there are some other dialogs that appear under...

Hi all, Just to let you know that this has been solved: My app has feature that presses F2 before taking the screen-shot. I just received this from the guy who was having trouble: F2 !!!!!! I have a blank screen saver which.... is assigned to F2. LOL - what's happening is your app is invoking my win...

No it's not a Vista issue. I am using Vista and it works perfectly. He is using XP.

In my main macro the line is very simple. GetScreenRes>mx,my ScreenCapture>0,0,mx,my,%SCRIPT_DIR%\graphics\export.bmp And this is working perfectly for everyone except this one guy. He uses two monitors But so do I And he has tried with only 1 monitor I have written a very simple tool fro him to tes...

If "printscreen" is used (Press Print Screen), and then an "edit-paste" performed in an image application (such as mspaint, etc), is it also black there? I'm wondering if this is something specific to just msched, or just a screenshot-type thing in general. Me too... The guy said that printscreen s...

Hi there, One of my users is experiencing this problem. There is a section of my code that uses the screenshot feature etc. It works great but this one person could never get a result from it. We have now realised that the reason for this is that the screen image taken is always completely black. I ...

Wouldn't: WaitReady>0 be useful for this purpose? I am using this in a similar way in a script that runs things form the command line. From help: WaitReady suspends script execution until the foreground window has finished processing mouse, keyboard, show window, and optionally, paint events. Issue ...

mtettmar wrote:Goto will always go to the first matching label. Duplicate labels is a no-no and I suppose Macro Scheduler really ought to not even let you create a duplicate label.

Understood.

In my laziness I expected it to go to the "nearest" matching label but of course 1st makes much more sense.

Me_again wrote:It was your phrase, I just borrowed it

Absolutely: Sloppy code indeed. I take that on the chin.

I do use Subs as well of course.

I suppose at least it shows I am not a proud man by the fact that I posted this up for you all to see.

I suppose this is just me but I would be interested to hear your opinion on it: I had a lot of confusion tonight after a slight redesign of one of my scripts. It basically involved a GOTO command This section was in this case skipped due to another IF>THEN Show>LWarning Label>LWarningLoop GetDialogA...

Thank you Marcus. I will looking at option 1 I think.

You saved me hours of trial and error there as I was thinking I had done something wrong.

Yes I did see that thanks but it's not relevant to me.

Just try this:

Let>modkey=ALT
Let>key=F

Press %modkey%
Send>%key%

etc. and see if it works for you.



I will give it another try though.