[Setup]
The following is a list of new
directives:
UsePreviousSetupType
Valid values: yes or no
Default value: yes
Description:
When this directive is yes, the default, at startup Setup will look in the registry to see if the same application is already installed, and if so, it will use the setup type and components settings from the previous installation as the default settings presented to the user in the wizard.
AlwaysShowComponentsList
Valid values: yes or no
Default value: yes.
Description:
If this directive is set to yes, Setup will always show the components list for customizable setups. If this is set to no Setup will only show the components list if the user selected a custom type from the type list.
FlatComponentsList
Valid values: yes or no
Default value: yes (modern style wizard), no (classic style
wizard)
Description:
When this directive is yes, Setup will use 'flat' checkboxes for the components list. Otherwise Setup will use '3d' checkboxes.
ShowComponentSizes
Valid values: yes or no
Default value: yes
Description:
When this directive is yes, Setup will show the size of a component in the components list.
Note:
Depending on the largest component, Setup will display sizes in
kilobytes or in megabytes.
DisableReadyMemo
Valid values: yes or no
Default value: no
Description:
If this is set to yes, Setup won't display a settings memo on the Ready To Install Page. Otherwise the memo is shown and contains information like the chosen setup type and the chosen
components.
[Types]
This new section is optional. It defines all of the setup types Setup will show
during installation.
Here is an example of a [Types] section:
[Types]
Name: "full"; Description: "Full installation"
Name: "compact"; Description: "Compact installation"
Name: "custom"; Description: "Custom installation"; Flags: iscustom
The following is a list of the supported parameters:
Name (required):
The internal name of the type. Used as parameter for components to instruct Setup to which types a component belongs.
Example:
Name: "full"
Description (required):
The description of the type. This description is shown during installation.
Example:
Description: "Full installation"
Flags:
This parameters is a set of extra options. Multiple options may be used by separating them by spaces. The following options are supported:
iscustom
Instructs setup that the type is a custom type. Whenever the end user manually changes the components selection during installation, Setup will set the setup type to the custom type. Note that if you don't define a custom type, Setup will only allow the user to choose a setup type and he/she can no longer manually select/unselect components.
Common parameters:
MinVersion, OnlyBelowVersion
Remarks:
-During compilation a set of default setup types is created if you define components in a [Components] section but don't define types.
These types are the same as the types in the example above.
[Components]
This new section is optional. It defines all of the components Setup will show
during installation for setup type customization.
Here is an example of a [Components] section:
[Components]
Name: "main"; Description: "Main Files"; Types: full compact custom; Flags: fixed
Name: "help"; Description: "Help Files"; Types: full
This example generates two components: A "main" component which gets installed if the end user selects a type with name "full",
"compact" or "custom" and a "help" component which only get installed if the end user selects the "full" type.
Since the "custom" type is customizable the
"help" component is also be installed if the user
wants to, even though "custom" isn't in the types list
of the "help" component.
The following is a list of the supported parameters:
Name (required):
The internal name of the component.
Example:
Name: "help"
Description (required):
The description of the component. This description is shown to the end user during installation.
Example:
Description: "Help Files"
Types:
A space separated list of types this component belongs to. If the end user selects a
type from this list, this component will be installed.
Example:
Types: full compact
Flags:
This parameters is a set of extra options. Multiple options may be used by separating them by spaces. The following options are supported:
fixed
Instructs Setup that this component can not be manually selected or unselected by the end user during installation.
restart
Instructs Setup to ask the user to restart the system if this component
is installed, regardless of whether this is necessary (because of [Files] section entries with the restartreplace flag).
Like AlwaysRestart but per component.
disablenouninstallwarning
Instructs Setup not to warn the user that this component
will not be uninstalled after he/she deselected this component
while it's already installed on his/her machine.
Common parameters:
MinVersion, OnlyBelowVersion
Remarks:
-Even if you disable customization because you didn't define a custom type, you can still use this section. Setup won't show the components list on the Select Components page (thereby disabling customization), but it will show the end user the selected components in the settings memo on the Ready To Install page.
-If you don't define components in this section, the Select Components page will be automatically skipped during installation, but the settings memo of the Ready To Install page still is shown.
-Depending on the complexity of your components, you can try to
use the [InstallDelete] section and the disablenouninstallwarning
flag to automatically 'uninstall' deselected components. See the
'classic' component in the My Inno Setup Extensions sample
script for an example.
[Dirs], [Files],
[Icons], [INI], [InstallDelete], [Registry], [Run],
[UninstallDelete], [UninstallRun]
The following is a list of new
parameters for entries in the above sections:
Components:
A space separated list of component names, telling Setup to
which components this entry belongs. If the end user select a component from this list,
this entry is processed (for example: the file is installed).
Here is a example:
[Files]
Source: "MyProg.exe"; DestDir: "{app}"; Components: main
Source: "MyProg.hlp"; DestDir: "{app}"; Components: help
Source: "Readme.txt"; DestDir: "{app}"; Flags: isreadme
[Icons]
Name: "{group}\My Program"; Filename: "{app}\MyProg.exe"; Components: main
Name: "{group}\My Program Help"; Filename: "{app}\MyProg.hlp"; Components: help
Remarks:
-A file without a Components parameter is always installed.
-The Components parameters are ignored if the [Components] section is empty.
-The Components parameter also works for displaying readme files. A 'isreadme' file will only be displayed if a component it belongs to is installed. If there are two readme's that should be displayed, Inno Setup (also the official) only displays the first in the script.
[Messages]
DefaultIsx.isl contains the
following new messages concerning setup types:
-WizardSelectComponents=Select Components
-SelectComponentsLabel=Select the components you want to install, clear the components you do not want to install:
-FullInstallation=Full installation
-CompactInstallation=Compact installation
-CustomInstallation=Custom installation
-ReadyMemoDir=Destination directory:
-ReadyMemoType=Setup Type:
-ReadyMemoComponents=Selected Components:
-ReadyMemoGroup=Program group:
-NoUninstallWarningTitle=Components Exist
-NoUninstallWarning=Setup has detected that the following components are already installed on your computer:%n%n%1%n%nDeselecting these components will not uninstall them.%n%nWould you like to continue anyway?
-ComponentSize1=%1 KB
-ComponentSize2=%1 MB
Setup now also supports
'[kb]' instead of '[mb]' in some messages. For example:
DiskSpaceMBLabel=The program requires at least
[kb] KB of disk space.
|