ControlClick

[Jojoba77]

Hi,

I've come on here to ask for help as a last resort. I have a little script to run through an install. I've managed to get ot to de-select various install components, but can not for the life of me get it to click 'no restart'. Please can someone tell me where I'm going wrong, in simplistic terms?

The line it fails on is the 'ControlClick' one. I have put a ; in front of the one after that,  so that I don't have to sit through repeated reboots for my every attempt! The attatched file should show the required properties of the check field I want.

Thank you

Edited January 12, 2016 by Jojoba77
typo

[jdelaney]

Don't use control sends...controlSetText is much better.

Specifically, for you checkboxes, use ControlCommand to make the checkbox 'check'ed.

I'd also suggest you use the ID of your controls...but installers are fairly stagnant, so it shouldn't matter.

Make sure the window you are performing action on is 'active', and the control you are doing action on is focused (controlfocus)...that will help you get up the accuracy.

Last suggestion is to use the silent command line params so you don't need to automate any of the app.

There are other little pitfalls in automating apps.  In the long run, you'll need to create functions to loop for ALL the necessary window states to be present, and another loop to wait for your control to be created.  It's possible you are attempting to click a control that hasn't been painted yet.

Edited January 12, 2016 by jdelaney

[Jojoba77]

Thank you for the suggestions, I shall give them a go.

This is my last resort tool for packaging as the exe file won't accept any silent switches.

Well something has changed . . .

 

Edited January 12, 2016 by Jojoba77

[jguinch]

Your setup seems to be made by Installshield.

Usually, an Installshield installation can be automated with something like setup.exe /s /v" /qb /norestart" (or use /qn for a silent install)

[Jojoba77]

 

There are other little pitfalls in automating apps.  In the long run, you'll need to create functions to loop for ALL the necessary window states to be present, and another loop to wait for your control to be created.  It's possible you are attempting to click a control that hasn't been painted yet.

Ah, thats a horrible downside. I had noticed it presented with a different install after an uninstall (it seems to retain some of your selectsions despite uninstalling)

[Jojoba77]

Your setup seems to be made by Installshield.

Usually, an Installshield installation can be automated with something like setup.exe /s /v" /qb /norestart" (or use /qn for a silent install)

I shall try this again too, it's the prefered method.

 

Thanks for all the feedback!

[jdelaney]

you used ControlSetText to 'send' the {enter} :)...that's why the text was modified to {enter}...to set the checkbox, look at ControlCommand in the help file.

You should never have to send enter to do what you want...you should always use ControlClick if it's a button, or ControlCommand to set check or uncheck on a checkbox (which is also a form of a button)

Also, just because an installer is created by installshield, doesn't mean the .iss files are present to do the silent install/update/uninstall...The provider would need to actually record the scenarios, and package them in.

Edited January 12, 2016 by jdelaney

[jguinch]

You're right jdelaney, it's a good point to accentuate it.
Most of the time, these parameters work, for this reason I suggested to try it