Using VCL Visual Styles and License RTF File text colour is wrong
I am trying out the VCL Visual Styles as an alternative to the skinning DLL I was previously using.
At the moment I am using the skin:
#define Skin "Carbon.vsf"
When the installer shows the RTF License file file the colouring is not as I expect:
The text is black and the background dark. But the other two pages are better:
I specify all my license files in the usual way in the [Languages] section:
Name: "English"; MessagesFile: "compiler:Default.isl"; LicenseFile: "..\..\Inno\l.eng\LicenseEnglish.rtf"; InfoAfterFile: "..\..\Inno\l.eng\InfoAfterEnglish.rtf"
How can I set this skin to use white text for the license file (like on the other pages I have shown)? Why doesn't it do so anyway?
Ideally i would like the Visual Studio 2019 Dark Theme as the skin but don't know how to do that - separate issue!
Update
If I try Amakrits style the license page looks like this:
And:
So it is doing the same thing for multiple style definitions.
For the benefit of readers of this question I had to re-create my RTF file in WordPad. It had been created in Microsoft Word and that seems to be the reason. Either that or some other RTF encoding issue.
Eitherway, creating the file again WordPad resolved the problem.
- Execute batch file in Inno Setup preprocessor during compilation with relative Path
- Read installer version from an .ini file stored in the same directory in Inno Setup
- Replace "Setup/Uninstall" string in UAC prompt for Inno Setup uninstaller
- Require minimum Inno Setup compiler version
- Resolve file paths relatively to a .iss file included from another folder
- Setting Inno Setup sign tool with relative paths
- Inno Setup preprocessor can read a file using FileOpen, but not using ReadIni
- Using path/value specified on Inno Setup compiler command-line in Inno Setup script
- Emit new line in Inno Setup preprocessor
- Function to add multiple source lines to Inno File section
- How to get the file name of the current Inno Setup script file?
- How to set my own variable in [Setup] and read it from [Code]
- How to read a [Setup] parameter in the Pascal code?
- Do not include duplicate files multiple times in the Inno Setup installer
- Can I select an #include path using a script and command line args in an Inno Setup installer?
- Automatically create new entry in "Programs and Features" for each new version
- Emitting value from Setup section in included file
- Extracting application version number using Inno Setup (but excluding the fourth number)
- Passing in version number to Inno Setup compiler
- How can I write the LanguageID into the Registry in Inno Setup?
- Inno Setup: Populating VersionInfoDescription and VersionInfoCopyright from an INI file using Pascal Scripting (scripted constant) setup property
- Can I use .isl files for the messages with preprocessor directives in Inno Setup?
- Inno Setup ParseVersion is not callable from [Code]
- Why would we need to use the #expr directive in Inno Setup?
- How do I create a Start Menu folder with Inno Setup?
- Start menu folder created by Inno Setup is not showing
- Inno Setup Registry entry for custom URL protocol
- Can Inno Setup compiler halt upon Exec() preprocessor function failure?
- Inno Setup preprocessor: Conditionally activate a #define (e.g. only when a certain Registry value is set)
- How can I pass command line parameters with a value to the Inno Setup Compiler, so I can use them in my code?