background execuation?

[bunny123]

HI,

I need to automate a execuation progress, i.e. fill out user id, passwd, click the menu, button, ..... right now, I can run it visually. My question, can I run it at the background? When I minimize the window, everything messed up.

Please advise.

Thank you

[i386]

HI,

I need to automate a execuation progress, i.e. fill out user id, passwd, click the menu, button, ..... right now, I can run it visually. My question, can I run it at the background? When I minimize the window, everything messed up.

Please advise.

Thank you

It all depends on what you have to do. Also, if you could post the part of the script that is causing you problems or all of it then I am sure you would get faster support and help.

[mikehunt114]

HI,

I need to automate a execuation progress, i.e. fill out user id, passwd, click the menu, button, ..... right now, I can run it visually. My question, can I run it at the background? When I minimize the window, everything messed up.

Please advise.

Thank you

Probably, can you give more specific info? Otherwise look at the Control* and Win* commands I guess.

[bunny123]

The script is quite simple. just some activities,

run("C:\Program Files\WinSCP3\WinSCP3.exe")

WinWaitActive("WinSCP Login")

ControlSend("WinSCP Login","","TEdit2","ipadd")

ControlSend("WinSCP Login","","TEdit1","userid")

ControlSend("WinSCP Login","","TPasswordEdit1","passwd")

ControlClick("WinSCP Login","","TButton20")

WinWaitActive("userid - userid@ipaddr - WinSCP")

After log in, i use mouseclick event to move mouse to the certain point to click some folder, it works when window opening, but when i minimize the window, even cannot log in. Do I have to run it on the window.

Please advise

[Jos]

Try replacing WinWaitActive() with WinWait()..

Mouseclick's won't work ... you will have to use Control functions ..

Edited December 1, 2006 by JdeB

[mikehunt114]

The Control* commands will all work while the window is minimized. If you use the same sort of commands to run the rest of your script it should work fine. Post the whole script as well as console output to tell us where your script is hanging.

[AcidCorps]

ok well what I want to do to make it easier is include a product key in the cmd switch. for example

Setup.exe /Key 1234-5678-90

it will start my script "/key" and have 1234-5678-90 set as $cdkey

[McGod]

script.exe /key 1234-5678-90

In your script, you can use

$CmdLine[0] = 2

$CmdLine[1] = "/key"

$CmdLine[2] = "1234-5678-90"

$CmdLine is generated with the switches

[AcidCorps]

i need the reverse of what you just did, so that i don't need to supply a cd key with it.

The user would type into the cmd window Setup.exe /Key 1234-5678-90

and the script will run Setup.exe and set $cdkey = 1234-5678-90

[herewasplato]

i need the reverse of what you just did, so that i don't need to supply a cd key with it.

The user would type into the cmd window Setup.exe /Key 1234-5678-90

and the script will run Setup.exe and set $cdkey = 1234-5678-90

Go to the help file.

Go to the index tab.

Type in command.

Read the info under "Command Line Parameters".

...and you should find that what Chip told you is what you do want.

If you start your script using:

Setup.exe /Key 1234-5678-90

Then when setup.exe runs there will be an array automatically populated as follows:

$CmdLine[0] = 2

$CmdLine[1] = "/key"

$CmdLine[2] = "1234-5678-90"

You can write your script to make use of that special array.

If you must have $cdkey = 1234-5678-90 then

$cdkey = $CmdLine[2]

...enjoy...

[AcidCorps]

ok sorry, thank you