Archive: RC1 Documentation Mistakes and Suggestions


RC1 Documentation Mistakes and Suggestions
1) Chapter 5: Compile Time Commands:

<b>5.4.6 !else</b>
[ifdef|ifndef|ifmacrodef|ifmacrondef [...]]


...

5.4.8 !insertmacro
!insertmacro macro_name [parameter] [...]
So as you mean here I have to put this way in a script

!insertmacro !insertmacro macro_name [parameter]


(this apply to "5.4.9 !macro" and "5.4.11 !undef" too)


2) Install Options Documentation:

Lack information about "codes to modify the page when it's already loaded", like:

- "how to disable or enable controls"
- "how to set the text of a label"
- "how to change the state of a textbox"
- "how to change a image"
- "how to get a text from a textbox, use it and put a modified text, based on the text got before"

So will help to make pages more "playfull".

1) Fixed

2) You can just write to the INI file in validation/notify functions.


I think that the documentation for LandString should mention that the use of 0 for language_id will make that the default string used for unspecified languages.

Vytautas


Lack information about "codes to modify the page when it's already loaded" (reffering to installer script, not INI file).


So you want to change normal NSIS pages? That's not related to InstallOptions. You can find documentation about interface commands like SetCtlColors and EnableWindow etc. in the users manual.

LangString with langauge 0 only makes it use the langauge of the last inserted langauge file.


Maybe that should be mentioned in the docs?

And is there a way to specify a default LandString then?

Vytautas


No, not with the LangString command. You can however create a language file system with defines to specify a default string.

I'll add info about the 0 ID to the documentation.


So you want to change normal NSIS pages? That's not related to InstallOptions. You can find documentation about interface commands like SetCtlColors and EnableWindow etc. in the users manual.
But doesn't have any codes to help customize the interface anywhere like i.e. "how to change the state of a textbox".

That's all a part of the Microsoft MSDN documentation. To change a text you should send a WM_SETTEXT message.

I don't think we should copy the whole Windows user interface documentation to the NSIS manual.