5 replies to this topic

[bhagelin]

I've been told that pure InstallScript projects do not use MSI. If this is the case, then why is there a "Direct Editor" in InstallScript projects that allows you to access and edit MSI-type tables?

[Stefan Krueger]

That is correct. But the project settings in the project file are stored in the same way as in MSI projects. InstalLScript projects have inherited the project file format from MSI projects.

[bhagelin]

I see, then would it be possible to change a value that is represented by the Direct Editor tables in order to enable/disable a dialog control at runtime?

More specifically, in the "Control" table chaning the attributes value from 1 to 3 enables a control.

[Stefan Krueger]

No because at runtime that project file isn't there anymore. Instead you have your compiled script, and a DLL with the dialog resources. You have to call script functions for this, or use a Basic MSI project instead.

[bhagelin]

Understood -- then I take it that there is no script function that will allow me to enable/disable a control?

Thank you for the information you've provided.

[bhagelin]

Solution (place in case DLG_INIT: of dialog's code):