Feature Request: License Dialog option to NOT install its RTF file

[NewsArchive]

[Saturday, March 19, 2005 11:23 PM]

I am using the License dialog conditionally to display RTF regarding upgrade
conditions. These are RTF files that do not belong in the installed file set,
which the License dialog forces. I tried working around this by installing
the RTF files as support files and using a variable both in the string
resource, and directly in the License Agreement ID. Neither works, and I
understand that is expected. It would be useful to have a dialog level option
to not install a given RTF.

--
Best regards,

Mark

[NewsArchive]

[Monday, March 21, 2005 2:52 PM]

Mark,

Can't you just HIDE the License Agreement dialog for upgrades?

And if you have different license agreements for, say, a new install and an
upgrade install, you can add two License Agreement dialogs (with two
different license agreement files) and HIDE one dialog.

Thanks,
Friedrich

--
Friedrich Linder
CEO, Lindersoft
www.lindersoft.com
1.954.252.3910

[NewsArchive]

[Monday, March 21, 2005 5:55 PM]

>Mark,
>
>Can't you just HIDE the License Agreement dialog for upgrades?
>
>And if you have different license agreements for, say, a new install and an
>upgrade install, you can add two License Agreement dialogs (with two
>different license agreement files) and HIDE one dialog.

Friedrich,

My workaround is to simply delete the unwanted RTF file at the end of the
script. That works nicely. FWIW, only one of the dialogs is actually used for
an EULA. The other two are used conditionally depending on the nature of the
upgrade. The reason I don't want their files installed is they are not
licenses, but simply upgrade information I happen to be displaying in RTF.
The license dialog is ideal for this as I need its "accept or exit" behavior.

--
Best regards,

Mark

[NewsArchive]

[Monday, March 21, 2005 6:36 PM]

Mark,

I think it's no problem to add a function so we can "read" a license or
readme file from within the "support directory" (or other directories) and
display it in the license agreement or readme dialog. IMO, it's only a
small compiler modification. I'll check this.

Thanks,
Friedrich

--
Friedrich Linder
CEO, Lindersoft
www.lindersoft.com
1.954.252.3910

[NewsArchive]

[Monday, March 21, 2005 6:48 PM]

>Mark,
>
>I think it's no problem to add a function so we can "read" a license or
>readme file from within the "support directory" (or other directories) and
>display it in the license agreement or readme dialog. IMO, it's only a
>small compiler modification. I'll check this.

Friedrich,

If that makes sense to you. I'm happy with just deleting them. In fact, with
the exception of the issue I emailed you about, I'm completely ecstatic about
SB5 at this point. It is really shaping up nicely.

--
Best regards,

Mark

[NewsArchive]

[Tuesday, March 22, 2005 12:33 PM]

Mark,

You can now add readme and license agreement files (unlimited number) to the
Support Files section. Then define a variable and set it to a .rtf file.

For example:

If %MODE% Equals "UPGRADE" Then
Set Variable %RTF_FILE% to %TMPDIR%\upgradetext.rtf
Else
Set Variable %RTF_FILE% to %TMPDIR%\newtext.rtf
End

You can then add this variable to the Readme or License Agreement dialog(s).

All files in the Support Files section are automatically compiled into the
setup.exe and removed from the target machine when the setup.exe terminates.

Thanks,
Friedrich

--
Friedrich Linder
CEO, Lindersoft
www.lindersoft.com
1.954.252.3910

[NewsArchive]

[Tuesday, March 22, 2005 5:49 PM]

>Mark,
>
>You can now add readme and license agreement files (unlimited number) to the
>Support Files section. Then define a variable and set it to a .rtf file.
>
>For example:
>
>If %MODE% Equals "UPGRADE" Then
> Set Variable %RTF FILE% to %TMPDIR%\upgradetext.rtf
>Else
> Set Variable %RTF FILE% to %TMPDIR%\newtext.rtf
>End
>
>You can then add this variable to the Readme or License Agreement dialog(s).
>
>All files in the Support Files section are automatically compiled into the
>setup.exe and removed from the target machine when the setup.exe terminates.

Very nice. Thanks, Friedrich.


--
Best regards,

Mark