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.

Hi there, I wrote a script that defines some keys to be pressed in my main script. I won't go into detail now but I have come across a problem which I'm sure will be quite easy for more experienced users to solve. Example: My main script requires the pressing of the "k" key to open a dialog. Some us...

I did edit my post above once again before I saw your new post. My apologies. It is tricky stuff though for a n00b like me. After reading the help I would still never have been able to do what you did for me although maybe I would have realised that the dll error was because I had something incorrec...

Sorry, no I didn't see the LibFunc documentation I don't know where that would be? EDIT: OK found it and added an extra red face... and I also posted back before you posted.

Apologies.

Ok I have got around this by entering a word as the value of that edit box and then doing this before the dialog action loop begins: LibFunc>User32,FindWindowExA,edit2Hwnd,dlgHwnd,0,TEdit,number Let>Dialog1.msEdit1=%deftracks% rda>Dialog1 Hope this makes sense. It does seem though, that using an act...

OK this works great except I have found a problem or even a "bug" if you like. //Get Handle of filename Edit Box LibFunc>User32,FindWindowA,dlgHwnd,TForm,Export Settings LibFunc>User32,FindWindowExA,edit1Hwnd,dlgHwnd,0,TEdit,%deffilename% LibFunc>User32,FindWindowExA,edit2Hwnd,dlgHwnd,0,TEdit,%deftr...