InstallAware

Welcome Michael, here is a test question for you.

How can I most easily provide a Print License Agreement feature? I notice the newer setups provide this functionality. The tiny little license window does not allow for easy reading.

Hi Steve!

You should be able to do this if you add a Print button to your form, and then capture the click event on that button, and call Run Program on the license agreement file, open wordpad or notepad, with the print command line parameter.

You may study the CD Autorun template if you would like to find out how to capture clicks on form buttons - it is the perfect example.

Does this get me a pass on the test

That CD AutoRun template is awesome. I see now how to do the printing using wordpad.

I haven't reviewed the CD Autorun template before because I wasn't making any CD install. I wish I had because I now have some new ideas on how this template can be used for other purposes. This template is good because it also shows how to do a loop ... which i didn't want to get into because I read you couldn't do looping ... but i see now there are some exceptions and you can do some menu processing style loops.

Thankyou!

MichaelNesmith wrote:You should be able to do this if you add a Print button to your form, and then capture the click event on that button, and call Run Program on the license agreement file, open wordpad or notepad, with the print command line parameter.

You may study the CD Autorun template if you would like to find out how to capture clicks on form buttons - it is the perfect example.

It was easy to add a print button to the Autorun example. In the wizard dialog I inserted a BitBtn button named "Print". I did not modifiy Object Rules or Object Behavior. In fact, I want to Have the control "Print" write to a variable, but that option is greyed out on the Object Behavior dialog. I can't see any difference between the Object Propeties of my button and the other buttons that do allow writing values to variable.

In the script there is a comment "// Exit Applet" and then several "ifs" referring to a variable "CHOICE". What is the applet? From where/when the variable CHOICE? If I try to add to the script:

If Variable CHOICE Equals PRINT
Run Program $PROGRAMFILES$\\Windows NT\\accessories\\wordpad.exe /p $SUPPORTDIR$\\license.rtf (WAIT)
end

then nothing happens (I added license.rtf as a support file ...Remember that you may include any file as a support file, and access it while the installation is running using the SUPPORTDIR variable).

I even tried moving this Run Program command into the "If Variable CHOICE Equals WEBSITE" section, and nothing happens.

When I add the Print button to the licensecheck dialog of a "Windows Installer" themed wizard project, I have no idea where to invoke the Run Program command, assuming I could get it to work.

We really want to buy InstallAware. I'm a novice at installation packages, so I'm somewhat at a loss here . I've read the entire help file (even copied into a document and created a PDF which I have read). I'm reading all the forum messages, and have read all the material on the ia website, but I'm not getting anywhere.

Thanks in advance for the assistance (my supervisor is awaiting some results before he'll spring for the purchase).

Hello there,

the things you ask can be done and a much better way (custom dialogs etc).
I can provide consulting services and create the whole setup for you and your company, at a very competitive price.

If you are interested you can email me at pkefal (at) installaware (dot) com.Describe what exactly you want to do, and i'll reply to you how long it's going to take and how its going to cost.


Thank you,

Hi!

Easy answer for this one: The Display Dialog command is set to return its result in the CHOICE variable. That's where the infamous CHOICE comes from!

For capturing individual button clicks, you do not assign them to variables. Just set their "Performs Action" field to "Return from Dialog" and be sure the Display Dialog command is writing to a variable in the "Return Result in Variable" field. Then just read that variable...which, in the autorun sample, is CHOICE.

The value that "CHOICE" holds is the Name property of the button on the form that was clicked. So you can use the "Object Properties" window to customize the name of your button after plopping it on the form, and then just read the return using CHOICE.

Let me know if that helps!

Yes, that is exactly what I needed. I figured that was what CHOICE was, but the hint I needed was setting "Performs Action" to "Return from Dialog".

Now I need to debug the line



which did not work. In fact, all we need there is:



and VIOLA!

Thank you very much for your prompt assistance!