1) "NSIS User Manual" Corrections
1.1) 4.9.10.2 IntOp
~ BITWISE NEGATEs value1 (i.e. 7 becomes
4294917288)
4294917288 ===> 4294967288
1.2) 4.8.1.13 DetailsButtonText
show details text ===> [show_details_text]
([] for optional choice indication = 0 parameters)
(_ for unique parameter indication = 1 parameter )
1.3) 4.8.1.19 InstallButtonText
install button text ===> [install_button_text]
1.4) 4.8.1.29 MiscButtonText
[back button text [next button text] [cancel button
text] [close button text]]
===> [back_button_text [next_button_text]
[cancel_button_text] [close_button_text]]
1.5) 4.8.1.37 SpaceTexts
[req text [avail text]] ===> [req_text [avail_text]]
1.6) 4.8.1.39 UninstallButtonText
text ===> [text]
2) "NSIS User Manual" Correction & Question
2.1) 4.8.1.10 CompletedText
text ===> [text]
2.2) CompletedText expects 0-2 parameters, what is the
function of 2nd parameter?
For a valid 2nd parameter the correction will be:
text ===> [text [2nd_parm]]
Best Regards,
Paulo R M Carneiro
prmc@br.com.br
Logged In: YES
user_id=584402
CompletedText should only accept one parameter, that's a bug
and it has been fixed. Thanks.
The other issues will be addressed in the, hopefully near,
future.
Logged In: NO
Hello,
I wanted to create Shortcuts Folder in Start\Programs for
all users and used the syntax given in program help:
SetShellVarContext all
CreateDirectory "$SMPROGRAMS\My Program"
The folder was created successfully but while uninstalling
it was not removed! I tried to add 'SetShellVarContext all'
parameter before 'RMDir "$SMPROGRAMS\My Program"' command
but it also did not work! And there is no information in
program help related to this topic! What should i do?
Please reply to aaleksanyants'at'yahoo.com
Best regards,
Andrey Aleksanyants
Logged In: YES
user_id=584402
How is it related to this bug report?
Try NSIS version 2.11, and if it doesn't work, open a forum
thread with more information.
Logged In: NO
Hi again and thank you for your reply,
My question does not relate to current bug report but it
also relates to NSIS user manual where I could not find the
required information, so I do not know how to write my
installation script: put "SetShellVarContext all" twice
(both in install and uninstall sections) or in install
section only?
Logged In: YES
user_id=584402
OK, fair enough. I've added this to SetShellVarContext's
description. It should be used twice. It affects a runtime
flag which is set to "current user" by default each time the
installer, or the uninstaller, starts running.
If you have further problems with the scripting, open a
forum thread with more information.
Logged In: NO
Hi again,
Could you please include the documentation for MUI 1.74
inside main program help so that it should be able to make a
search in it from help index? And below are given 2 strings
which are not described anywhere (why?) and I don't remeber
where could I find them from, but I need them very often:
!define MUI_WELCOMEPAGE_TITLE_3LINES
!define MUI_FINISHPAGE_TITLE_3LINES
This works OK, but ONLY in Installer! And when I try to add
an additional line in Uninstaller window, writing:
!define MUI_UNWELCOMEPAGE_TITLE_3LINES
!define MUI_UNFINISHPAGE_TITLE_3LINES
, this does not work, the title remains with 2 lines! What
should I do?
And one more problem: this string:
!define MUI_FINISHPAGE_NOAUTOCLOSE
works fine, but this one:
!define MUI_UNFINISHPAGE_NOAUTOCLOSE
does not work at all, the uninstaller jumps directly to
finish page!
Regards,
Andrey
Logged In: YES
user_id=584402
Adding the MUI documentation to the CHM is problematic. You
should open a feature request for this.
Those 3LINES defines are documented in the MUI readme under
the Pages section.
To use them for the uninstaller, simply define them above
the uninstaller page. No UN prefix is needed.
The auto close define works fine for me. Please attach an
example script to a new forum thread.
Please don't post your new bug reports to existing bug
reports. Please ask scripting questions in the forum, and
not in the bug tracker. More people respond in the forums
and it's easier to search.
I realize you might have come to this tracker from the "Need
support?" link on the project page. I'll remove that link,
questions should be asked in the forum, not the bug tracker.
But sadly, there's no way to specify an external link for
that page. I thought it'd be clear enough, I guess it's not.
Logged In: NO
Hi again,
> Those 3LINES defines are documented in the MUI readme
> under the Pages section.
Yes, you are right! But there is not any description for
using them with uninstaller!
> To use them for the uninstaller, simply define them
> abovethe uninstaller page. No UN prefix is needed.
BTW, why do I need to specify them twice? But I think it
should be more reasonable to use them in uninstaller too
without requiring any additional strings because the program
name remains long both in installer and uninstaller, don't
you agree?
> The auto close define works fine for me. Please attach an
> example script to a new forum thread.
I could send it to you by email if you provide me yours.
Could you please contact me via rubgeo at rambler.ru ?
> Please don't post your new bug reports to existing bug
> reports. Please ask scripting questions in the forum,
> and not in the bug tracker. More people respond in the
> forums and it's easier to search.
The problem was that I didn't really know if there are bugs
or just scripting questions, because, as I wrote above, I
thought that if there is no special string for uninstaller's
welcome and finish pages title displaying they should be
displayed the same way as in installer, but they didn't. And
till now I cannot stop jumping to finish page in UNistaller
- MUI_UNFINISHPAGE_NOAUTOCLOSE does not work independently
of its placing (I tried to place it in common MUI settings
and right above the MUI_UNPAGE_FINISH, both with no results)!
Regards,
Andrey
Logged In: YES
user_id=584402
A few lines above the description of that define, the readme
states: "Note: There is no difference between installer and
uninstaller page settings." and "Page Settings apply to a
single page and should be set before inserting a page macro.
If you have multiple pages of one type and you want to set a
setting for all them, put the setting before each page macro.".
Why not attach the script to a new forum thread? This way,
you could get a much faster response. If you wish to use
e-mail, send it to kichik@users.sf.net.
Logged In: YES
user_id=970495
Originator: NO
are those fixed already? :)
Logged In: YES
user_id=584402
Originator: NO
What could be easily fixed was already fixed. However, all of those "more than one word for parameter" to "[more_than_one_word_for_parameter]" changes were not done because there are tons of them. I wanted to form a standard for that first, if already changing the entire documentation. It's a bit of a mess now when it comes to parameter description. I remember I even wanted to create a defined C structure for describing parameters.