dragonleo/NSIS
1
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

- Docs fixes

Browse source 
- Command help for InstType fix


git-svn-id: https://svn.code.sf.net/p/nsis/code/NSIS/trunk@2312 212acab6-be3b-0410-9dea-997c60f758d6
This commit is contained in:
kichik 2003-03-16 17:40:22 +00:00
parent ab6fbe5fc7
commit 06f8b09e29
5 changed files with 8 additions and 8 deletions
Download patch file Download diff file Expand all files Collapse all files

2
Docs/src/attributes.but
View file

@ -144,7 +144,7 @@ Valid values for flag are "smooth" (smooth the progress bar) or "colored" (color
\S2{ainsttype} InstType
\c install_type_name | /NOCUSTOM | ([/LANG=lang_id] /CUSTOMSTRING=str)| /COMPONENTS.. ..ONLYONCUSTOM
\c install_type_name | /NOCUSTOM | ([/LANG=lang_id] /CUSTOMSTRING=str) | /COMPONENTSONLYONCUSTOM
Adds an install type to the install type list, or disables the custom install type. There can be as many as 8 types, each one specifying the name of the install. The first type is the default (generally 'Typical'). Each type is numbered, starting at 1. See SectionIn for information on how those numbers are used. If the /NOCUSTOM switch is specified, then the "custom" install type is disabled, and the user has to choose one of the pre-defined install types. Alternatively, if the /CUSTOMSTRING switch is specified, the parameter will override the "Custom" install type text. Alternatively, if the /COMPONENTSONLYONCUSTOM flag is specified, the component list will only be shown if the "Custom" install type is selected.

8
Docs/src/sec.but
View file

@ -30,14 +30,14 @@ Stores the text description of the section section_index into the output. If the
\c section_index inst_types
Sets the Install Types of the section specified by section_index. Note that the Section Index starts with Zero. Inst_types is a byte. Every bit of it is a flag that tells if the section is in that Install Type or not. For Example you have 3 Install Types and you want that the first section to be included in the Insttypes 1 and 3. Than the command looks like this:
Sets the install types the section section specified by section_index defaults to the enabled state in. Note that the section index starts with zero. Every bit of inst_types is a flag that tells if the section is in that install type or not. For example, if you have 3 install types and you want the first section to be included in install types 1 and 3, then the command should look like this:
\c SectionSetInstTypes 0 5
because the binary value for 5 is "00000101". The error flag will be set if an out of range section is specified.
because the binary value for 5 is "00000101". The error flag will be set if the section index specified is out of range.
\S2{SectionGetInstTypes} SectionGetInstTypes
\c section_index user_variable
\c section_index user_var(output)
Retrieves the Install Types of a section. See above for a description of how to deal with the output. The error flag will be set if an out of range section is specified.
Retrieves the install types flags array of a section. See above explanation about SectionSetInstTypes for a description of how to deal with the output. The error flag will be set if the section index specified is out of range.

2
Docs/src/sections.but
View file

@ -30,7 +30,7 @@ This command closes the current open section.
\c insttype_index [insttype_index] [RO]
This command specifies which Install Types (see InstType) the current section defaults to the enabled state in. Multiple SectionIn commands can be specified (they are combined). If you specify RO as a parameter, then the section will be Read-Only, meaning it will always be set to install.
This command specifies which install types (see InstType - \k{ainsttype}) the current section defaults to the enabled state in. Multiple SectionIn commands can be specified (they are combined). If you specify RO as a parameter, then the section will be read-only, meaning the user won't be able to change its state.
\S2{ssubsection} SubSection

2
Docs/src/tutorial.but
View file

@ -31,7 +31,7 @@ A NSIS script can contain Installer Attributes and Sections/Functions. You can a
\S1{installerattributes} Installer Attributes
Installer Attributes determine the behavior and the look and feel of your installer. With these attributes you can define what pages are shown in which order, texts that will shown during the installation, the number of installation types etc. Most of these commands can only be set and are not changeable during runtime.
Installer Attributes determine the behavior and the look and feel of your installer. With these attributes you can define what pages are shown in which order, texts that will be shown during the installation, the number of installation types etc. Most of these commands can only be set and are not changeable during runtime.
The most basic attributes are Name (\k{aname}), InstallDir (\k{ainstalldir}) and DirText (\k{adirtext}).

2
Source/tokens.cpp
View file

@ -86,7 +86,7 @@ static tokenType tokenlist[TOK__LAST] =
{TOK_INSTCOLORS,"InstallColors",1,1,"(/windows | (foreground_color background_color))"},
{TOK_INSTDIR,"InstallDir",1,0,"default_install_directory"},
{TOK_INSTPROGRESSFLAGS,"InstProgressFlags",0,-1,"[flag [...]]\n flag={smooth|colored}"},
{TOK_INSTTYPE,"InstType",1,1,"(/NOCUSTOM|[/LANG=lang_id] /CUSTOMSTRING=CustomStr|TypeName)"},
{TOK_INSTTYPE,"InstType",1,1,"install_type_name | /NOCUSTOM | ([/LANG=lang_id] /CUSTOMSTRING=str) | /COMPONENTSONLYONCUSTOM"},
{TOK_INTOP,"IntOp",3,1,"$(user_var: result) val1 OP [val2]\n OP=(+ - * / % | & ^ ~ ! || &&)"},
{TOK_INTCMP,"IntCmp",3,2,"val1 val2 jump_if_equal [jump_if_val1_less] [jump_if_val1_more]"},
{TOK_INTCMPU,"IntCmpU",3,2,"val1 val2 jump_if_equal [jump_if_val1_less] [jump_if_val1_more]"},