ANN: Inno Setup 6.5.4 released

[Martijn Laan]

Hi everyone,

Inno Setup 6.5.4 has been released.

This version fixes a problem with Pascal Scripting event function CurInstallProgressChanged.

Download: https://www.jrsoftware.org/isdl.php

For the complete list of what's new/changed, see: What's new in this version?.

To support our work please purchase a license or make a donation. Thanks in advance!

Greetings,
Martijn Laan

[Martijn Laan]

Hi everyone,

For the next release, we are working hard on various enhancements, including:

• Adding support for dark mode (forced or automatic) and custom styles to Setup and Uninstall.
  
• Includes support for dark and custom styled task dialogs.
• Includes support for right to left languages.

A preview version is available temporarily.

You should not use this version in production. However, please try your own scripts in dark mode or with a custom style, and report any successes or failures here. Thank you in advance.

What's new in this preview version?

Download - uses the Polar Light or Polar Dark style, depending on your Windows system settings, including styled title bars which is optional

Updated WizardStyle help topic - includes example screenshots.

Please purchase a license or donate to support this work. Thank you! ♥

Greetings,
Martijn Laan

[LordFreddy073]

  Hi, thanks for the preview release. I encountered a bug on the wizard page.

  

--
You received this message because you are subscribed to the Google Groups "innosetup" group.
To unsubscribe from this group and stop receiving emails from it, send an email to innosetup+...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/innosetup/175904057563.7.3012997584203635893.925947274%40innosetup.nl.

[Martijn Laan]

Sorry, but what's the bug? Thanks for testing!

Greetings,
Martijn

Op 28-9-2025 om 08:50 schreef LordFreddy073:

[LordFreddy073]

Please refer to the attached image. In the Wizard Style section, toggle between Classic and Modern mode, and then click Preview. When Classic mode is selected, a blank area appears around the opened window. If this is expected behavior, I apologize for bringing this up.

--
You received this message because you are subscribed to the Google Groups "innosetup" group.
To unsubscribe from this group and stop receiving emails from it, send an email to innosetup+...@googlegroups.com.

To view this discussion visit https://groups.google.com/d/msgid/innosetup/175904235431.11.9335733689101209198.925964863%40innosetup.nl.

[bovirus]

@Martin

What do you think to change the ID name "Inno Setup Setup Data" in "Inno Setup Installer Data" (to avoid double "Setup" string?

[Martijn Laan]

Hi,

To be honest, I don't see any value in this idea. 

Greetings,

Martijn

-------- Original Message --------

To view this discussion visit https://groups.google.com/d/msgid/innosetup/240d1ae4-47fb-4b8f-a43a-1d58eaed09fbn%40googlegroups.com.

[LordFreddy073]

I found a bug. All UI elements that accept a color parameter fail to apply the specified color and fall back to default colors when a style is active. For example, in CodeClasses.iss adding:
```
color := clYellow;
Font.Color := clRed;
```
to the StaticText2 element has no effect while the style is active. If I remove 'dynamic' from WizardStyle, the setup applies the colors correctly. This behavior also occurs with VCL styles (e.g. the built-in “Polar, slate, zircon” styles). I have not tested every control, but it likely affects other controls that expose color properties.

[Martijn Laan]

Hi,

Thanks, but that's the expected behavior for styled controls.

Greetings,

Martijn

-------- Original Message --------

--

You received this message because you are subscribed to the Google Groups "innosetup" group.
To unsubscribe from this group and stop receiving emails from it, send an email to innosetup+...@googlegroups.com.

To view this discussion visit https://groups.google.com/d/msgid/innosetup/CAKnaeKmStoiOQdx%3DsB%3DaLFkgqMENGTYTucdveHF9wZg9Sgc%3D_Q%40mail.gmail.com.

[Martijn Laan]

Hi,

The examples use transparency to ensure the classic style example shows smaller than modern style example. A side effect is indeed a blank area in the preview windows as well. To keep the code simple I did not try to 'fix' this.

Greetings,

Martijn

-------- Original Message --------

To view this discussion visit https://groups.google.com/d/msgid/innosetup/CAKnaeK%3D-rJL-Qae7nphLnT1n_aDu6EQe37nYme%3DuXx2O-ZhViw%40mail.gmail.com.

[LordFreddy073]

Can you add the 'StyleElements' property to 'TControl'? It should accept the flags seFont, seClient, and seBorder, so with this, it's possible to use color when style is activated too.

[Martijn Laan]

Yes I will do that, thanks for the suggestion.

Greetings,
Martijn

Op 28-9-2025 om 20:49 schreef LordFreddy073:

--

You received this message because you are subscribed to the Google Groups "innosetup" group.
To unsubscribe from this group and stop receiving emails from it, send an email to innosetup+...@googlegroups.com.

To view this discussion visit https://groups.google.com/d/msgid/innosetup/CAKnaeKmg4TnRzk6xsPFBQGuRvr%2BK4-qRO5apry09D1MQOfP2Hg%40mail.gmail.com.

[LordFreddy073]

Hi, I have some more suggestions and I would be happy if you listen to me:

1. Can you change the type of the following and similar functions to Int64 type? So that they can accept larger values?
```
SetArrayLength => parameter (I).
SetLength => parameter (L).
Length, GetArrayLength => function type.
GetIniInt => parameters (Default, Min, Max), function type.
SetIniInt => parameter (Value).
Round => function type.
TStream Class => All functions and procedures that use LongInt.
```
*** I think it is better to change LongInt to Int64 for all functions supported by inno setup ***

2. If possible, can you change or add the similar function and procedure in TStream class to use type 'Byte' or 'array of Byte' instead of type AnyString? For example:
```
changes:
function Read(var Buffer: AnyString; ByteCount: Longint): Longint;
To:
function Read(var Buffer: Byte; ByteCount: Longint): Longint;
Or:
function Read(var Buffer: array of Byte; ByteCount: Longint): Longint;
```

3. This is actually personal :)
Can you add a boolean 'ShowFiles' property to the 'TFolderTreeView' class to also show the files, so the user can select them? Something like the 'BIF_BROWSEINCLUDEFILES' flag for the Windows API function 'SHBrowseForFolder'?
Also, I have to tell you that I have no problem using the API function for this, but a native element that supports this is better and also has more room for customization.

Thanks!

[Eivind Bakkestuen]

The language dialog is cut off, when running on a 4K display with 200% scaling

Caption and hints appear to have smaller fonts than expected

the editor doesn't fill the IDE window after starting from the installer, editor is a small window upper left

Other than that, great work on the new styling, will definitely make use of this!

--

You received this message because you are subscribed to the Google Groups "innosetup" group.
To unsubscribe from this group and stop receiving emails from it, send an email to innosetup+...@googlegroups.com.

To view this discussion visit https://groups.google.com/d/msgid/innosetup/175904057563.7.3012997584203635893.925947274%40innosetup.nl.

[Jernej Simončič]

On Wednesday, October 1, 2025, 09:57:58, Eivind Bakkestuen wrote:

The language dialog is cut off, when running on a 4K display with 200% scaling

I'm running 225% scaling at home (5120x2880, 27″), 168% at work (3840x2160, 27″), and I did not notice this problem; will test on my mini laptop when I get back home, that one is 200%.

 

-- 
< Jernej Simončič ><><><><>< https://eternallybored.org/ >

The most expensive component is the one that breaks.
       -- Law of New Fangled Gadgetry

[Martijn Laan]

Thanks for testing, that's really odd what you're seeing.

Re: IDE: I didn't make styling changes to the IDE between this preview and version 6.5. Is this also happening with 6.5?

Re: Setup:

Why the language dialog is cut off I also don't understand. I can only offer bunch of questions.

• This is a screenshot of Inno Setup's own installer right?
• Is it only the language dialog which has this?
• Was your system already in 200% before starting the installer?
• Can you reproduce it if you reboot?
• Does the same problem occur if you put Windows in light mode?
• Does the log file say anything special?

The preview has styled title bars enabled (they are disabled by default) and those are drawn by Delphi's VCL Styles code. I haven't actually tested those on high DPI myself yet I realize now.

Other than that, great work on the new styling, will definitely make use of this!

Thanks and good to hear!

Greetings,
Martijn

Op 1-10-2025 om 09:57 schreef Eivind Bakkestuen:

The language dialog is cut off, when running on a 4K display with 200% scaling

Caption and hints appear to have smaller fonts than expected

the editor doesn't fill the IDE window after starting from the installer, editor is a small window upper left

Other than that, great work on the new styling, will definitely make use of this!

On Sun, Sep 28, 2025 at 4:23 PM 'Martijn Laan' via innosetup <inno...@googlegroups.com> wrote:

Hi everyone,

For the next release, we are working hard on various enhancements, including:

• Adding support for dark mode (forced or automatic) and custom styles to Setup and Uninstall.
  
• Includes support for dark and custom styled task dialogs.
• Includes support for right to left languages.

A preview version is available temporarily.

You should not use this version in production. However, please try your own scripts in dark mode or with a custom style, and report any successes or failures here. Thank you in advance.

What's new in this preview version?

Download - uses the Polar Light or Polar Dark style, depending on your Windows system settings, including styled title bars which is optional

Updated WizardStyle help topic - includes example screenshots.

Please purchase a license or donate to support this work. Thank you! ♥

Greetings,
Martijn Laan

--
You received this message because you are subscribed to the Google Groups "innosetup" group.
To unsubscribe from this group and stop receiving emails from it, send an email to innosetup+...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/innosetup/175904057563.7.3012997584203635893.925947274%40innosetup.nl.

--
You received this message because you are subscribed to the Google Groups "innosetup" group.
To unsubscribe from this group and stop receiving emails from it, send an email to innosetup+...@googlegroups.com.

To view this discussion visit https://groups.google.com/d/msgid/innosetup/CAH4EOO5LRq5GZN95HAeDNWpqOrrqV8GYWfkRW155wqtXn7OGpg%40mail.gmail.com.

[Martijn Laan]

Hi,

Could you please try this installer?

https://files.jrsoftware.org/is/dev/innosetup-6.6.0-preview-2.exe

It's the same as before except that styled title bars are turned off.

The title bar will still be dark if Windows is in dark mode, but this uses Windows itself (DWMWA_USE_IMMERSIVE_DARK_MODE).

Thanks in advance.

Greetings,
Martijn

Op 1-10-2025 om 09:57 schreef Eivind Bakkestuen:

The language dialog is cut off, when running on a 4K display with 200% scaling

Caption and hints appear to have smaller fonts than expected

the editor doesn't fill the IDE window after starting from the installer, editor is a small window upper left

Other than that, great work on the new styling, will definitely make use of this!

On Sun, Sep 28, 2025 at 4:23 PM 'Martijn Laan' via innosetup <inno...@googlegroups.com> wrote:

Hi everyone,

For the next release, we are working hard on various enhancements, including:

• Adding support for dark mode (forced or automatic) and custom styles to Setup and Uninstall.
  
• Includes support for dark and custom styled task dialogs.
• Includes support for right to left languages.

A preview version is available temporarily.

You should not use this version in production. However, please try your own scripts in dark mode or with a custom style, and report any successes or failures here. Thank you in advance.

What's new in this preview version?

Download - uses the Polar Light or Polar Dark style, depending on your Windows system settings, including styled title bars which is optional

Updated WizardStyle help topic - includes example screenshots.

Please purchase a license or donate to support this work. Thank you! ♥

Greetings,
Martijn Laan

--
You received this message because you are subscribed to the Google Groups "innosetup" group.
To unsubscribe from this group and stop receiving emails from it, send an email to innosetup+...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/innosetup/175904057563.7.3012997584203635893.925947274%40innosetup.nl.

--
You received this message because you are subscribed to the Google Groups "innosetup" group.
To unsubscribe from this group and stop receiving emails from it, send an email to innosetup+...@googlegroups.com.

To view this discussion visit https://groups.google.com/d/msgid/innosetup/CAH4EOO5LRq5GZN95HAeDNWpqOrrqV8GYWfkRW155wqtXn7OGpg%40mail.gmail.com.

[Jernej Simončič]

On Wednesday, October 1, 2025, 16:24:50, 'Martijn Laan' via innosetup wrote:

Could you please try this installer?

https://files.jrsoftware.org/is/dev/innosetup-6.6.0-preview-2.exe

I just tested both installers in several of my VMWare VMs and on Servers 2019 and 2016 over RDP, and while -2 fixes the problem on Windows 10 and 11, Server 2019 and older have cut-off buttons and non-scaled titlebar. Using light or dark mode doesn't make a difference.

 

On my own workstation the problem doesn't appear, apparently because I use high contrast mode, which disables theming.

 

(top is original installer, bottom is -2):

Windows 11:

 

Windows 10:

 

Windows Server 2019 (over RDP; not sure why both windows are showing focus):

 

Windows Server 2016 (over RDP; same focus weirdness as above):

 

Windows 8.1:

 

Windows 7:

 

 

-- 
< Jernej Simončič ><><><><>< https://eternallybored.org/ >

No matter how many alterations, cheap pants never fit.
       -- Firth's Law of Tailoring

[Jernej Simončič]

On Wednesday, October 1, 2025, 16:24:50, 'Martijn Laan' via innosetup wrote:

Could you please try this installer?

https://files.jrsoftware.org/is/dev/innosetup-6.6.0-preview-2.exe

The wizard itself also has some spacing issues in the original 6.6.0 preview and on older Windows versions, but those at least don't result in cut-off controls:

 

 

 

-- 
< Jernej Simončič ><><><><>< https://eternallybored.org/ >

If you assign N persons to write a compiler you'll get a N-1 pass compiler.
       -- Conway's Law #1

[Martijn Laan]

Wow, thanks a lot for the extensive testing. It is clear that the styled title bars are the problem:

Older versions of Windows lack the DWMWA_USE_IMMERSIVE_DARK_MODE API I mentioned earlier and it that case it currently leaves the title bars styled. This explains why you're still seeing the problem on older versions.

The reason light mode doesnt make a difference is that this installer also uses a style in light mode ('Polar Light'). Forgot about that when I asked the question.

Were all your screenshots at 200% DPI? Are you seeing differences between different DPI values?

Luckily I did a bunch of work to be able to turn of styling of all title bars including in message boxes (by using a custom messagebox implementation), so a simple fix would be to disallow styled title bars if DPI isn't at 100%.

But I will check to VCL Styles Forms title bar code to see if I can spot the problem, though I'm afraid it might be unreadable code based on my experience with the VCL Styles Messagebox title bar code I did already study (and which is now unused due to the custom implementation I mentioned).

Greetings,

Martijn

-------- Original Message --------

On Wednesday, 10/01/25 at 22:31 Jernej Simončič <jernej|s-g....@eternallybored.org> wrote:

On Wednesday, October 1, 2025, 16:24:50, 'Martijn Laan' via innosetup wrote:

Could you please try this installer?

https://files.jrsoftware.org/is/dev/innosetup-6.6.0-preview-2.exe

I just tested both installers in several of my VMWare VMs and on Servers 2019 and 2016 over RDP, and while -2 fixes the problem on Windows 10 and 11, Server 2019 and older have cut-off buttons and non-scaled titlebar. Using light or dark mode doesn't make a difference.

 

On my own workstation the problem doesn't appear, apparently because I use high contrast mode, which disables theming.

 

(top is original installer, bottom is -2):

Windows 11:

 

Windows 10:

 

Windows Server 2019 (over RDP; not sure why both windows are showing focus):

 

Windows Server 2016 (over RDP; same focus weirdness as above):

 

Windows 8.1:

 

Windows 7:

 

 

-- 
< Jernej Simončič ><><><><>< https://eternallybored.org/ >

No matter how many alterations, cheap pants never fit.
       -- Firth's Law of Tailoring

--

You received this message because you are subscribed to the Google Groups "innosetup" group.
To unsubscribe from this group and stop receiving emails from it, send an email to innosetup+...@googlegroups.com.

To view this discussion visit https://groups.google.com/d/msgid/innosetup/1889271429.20251001223049%40eternallybored.org.

[Jernej Simončič]

On Wednesday, October 1, 2025, 23:05:06, 'Martijn Laan' via innosetup wrote:

Were all your screenshots at 200% DPI? Are you seeing differences between different DPI values?

They were at 225% DPI.

 

-- 
< Jernej Simončič ><><><><>< https://eternallybored.org/ >

Bad regulation begets worse regulation.
       -- Mobil's Maxim

[Jernej Simončič]

On Wednesday, October 1, 2025, 23:05:06, 'Martijn Laan' via innosetup wrote:

Older versions of Windows lack the DWMWA_USE_IMMERSIVE_DARK_MODE API I mentioned earlier and it that case it currently leaves the title bars styled. This explains why you're still seeing the problem on older versions.

Speaking of DWMWA_USE_IMMERSIVE_DARK_MODE, I think it's actually supported since Windows 10 1809 (or even 1803), it just wasn't documented until Windows 11 (most programs that I have and support dark mode have no problems enabling it on Server 2019, which is 1809).

 

-- 
< Jernej Simončič ><><><><>< https://eternallybored.org/ >

Anything that begins well ends badly. Anything that begins badly ends worse.
       -- Universal Law

[Martijn Laan]

Op 2-10-2025 om 10:23 schreef Jernej Simončič:

Speaking of DWMWA_USE_IMMERSIVE_DARK_MODE, I think it's actually supported since Windows 10 1809 (or even 1803), it just wasn't documented until Windows 11 (most programs that I have and support dark mode have no problems enabling it on Server 2019, which is 1809).

Yeah, thanks, that's correct, but enabling it on older versions of Windows requires using a different value (or even values IIRC) than the documented one for the DWMWA_USE_IMMERSIVE_DARK_MODE constant.

We chose to only use the documented value, which is 20.

The first version that introduced the value of 20 is 19041 so that's what we use as the minimum version, even though https://learn.microsoft.com/en-us/windows/win32/api/dwmapi/ne-dwmapi-dwmwindowattribute says to use 22000

Greetings,
Martijn

[Martijn Laan]

Hi,

Op 1-10-2025 om 23:05 schreef 'Martijn Laan' via innosetup:

But I will check to VCL Styles Forms title bar code to see if I can spot the problem

I found the problem: Setup doesn't use VCL's built-in Scaled property for DPI scaling, and instead handles this by itself. This is because our scaling code predates VCL's built-in support for it.

A side effect is that the FCurrentPPI property of VCL controls (which includes forms) is always set to 96, when it should be, for example, 120 when DPI is 125%.

In turn, this causes the styled title bars to not scale themselves, and I suppose it could cause other issues as well.

Using a class helper, we can directly update the FCurrentPPI property ourselves. I need some time to see if that's a good approach or not. 

Greetings,
Martijn

[Eivind Bakkestuen]

preview 2 looks correct, its the bottom of these, on the same desktop at the same time

To view this discussion visit https://groups.google.com/d/msgid/innosetup/175932869711.7.2520078344498121136.931566893%40innosetup.nl.

[Eivind Bakkestuen]

PS, hints are still small and virtually unreadable on the 200% zoom on a laptop screen, and the 2 lower left images are also very small and could probably need a refresh :) ( size appears okish in image below because I've zoomed in on the area of interest )

To view this discussion visit https://groups.google.com/d/msgid/innosetup/175932869711.7.2520078344498121136.931566893%40innosetup.nl.

[Martijn Laan]

Hi,

Thanks for testing! Hints being small might actually be the same problem, I will work on it soon.

For the images I dont have high dpi versions, nor was I able to find good alternatives so far.

Greetings,

Martijn 

-------- Original Message --------

To view this discussion visit https://groups.google.com/d/msgid/innosetup/CAH4EOO6WmXPZ5khkA-NFLDBFkHQYY1ZEm8vse2hR7_NMKCOR4Q%40mail.gmail.com.

[Martijn Laan]

Hi everyone,

I have released an update to the 6.6.0 preview. See the download link below.

Main improvements in this update are:

• Fixed an issue with styled title bars in high DPI scenarios, along with other DPI improvements, such as proper hint scaling (even when Setup is not in dark mode or using a custom style).
• Improved the appearance of the custom implementation for task dialogs and message boxes.
• Added new StyleElements and StyleName properties to support class TControl.
  See CodeClasses.iss for an example, which also demonstrates the use of IsDarkInstallMode.
• Included other unrelated improvements, such as:
• Improved contrast ratio for various syntax highlighting colors in the Compiler IDE, particularly in dark mode.
• Internal changes preparing for a 64-bit version of the "setup loader" program.

Like before this preview includes:

• Adding support for dark mode (forced or automatic) and custom styles to Setup and Uninstall.
  
• Includes support for dark and custom styled task dialogs.

• Includes support for right-to-left languages.

You should not use this version in production. However, please try your own scripts in dark mode or with a custom style, and report any successes or failures here. Thank you in advance.

What's new in this preview version?

Download - uses the Polar Light or Polar Dark style, depending on your Windows system settings, including styled title bars which is optional.

Updated WizardStyle help topic - includes example screenshots.

Please purchase a license or donate to support this work. Thank you! ♥

Greetings,
Martijn Laan

Screenshot of the preview installer showing the Polar Dark style when Windows is in dark mode and uses 125% DPI

[LordFreddy073]

  Thank you for adding the 'StyleElements' property. Also could you please clarify the purpose of the new 'StyleName' property? Specifically, what does it do and in which scenarios should it be used?

 "Bug?": I hadn’t noticed before, but the VCL style is not applied to the scrollbar of 'TFolderTreeView'

  

[Bruno Lopes da Silva]

I think would be nice having a Default/modern light version with custom widgets. This would reduce the inconsistency with Dark mode. The sizing of the widgets on `modern dynamic`, specially the buttons, is different after all.

[Martijn Laan]

Hi,

You can use a custom light style by setting the WizardStyleFile directive to any VCL Styles file (*.vsf). These style files are available from for example Embarcadero GetIt. See https://getitnow.embarcadero.com/category/styles/?p=1. AFAIK downloading these styles requires installation of the Delphi, which can be the free Community Edition. Earlier I have reached out to Embarcadero to confirm whether these style files are redistributable and am awaiting a definitive response.

The default dark style is "Windows11 Dark 1.0", available at https://getitnow.embarcadero.com/vcl-windows-style-windows11-dark/. For a corresponding light style, you can use "Windows11 Light 1.0" from https://getitnow.embarcadero.com/vcl-windows-style-windows11-light/.

Regarding sizing differences, I am not aware of any changes in sizing between modern and classic, nor between different VCL styles, including when using the native (unstyled) appearance. 

Greetings,
Martijn

-------- Original Message --------

--

You received this message because you are subscribed to the Google Groups "innosetup" group.
To unsubscribe from this group and stop receiving emails from it, send an email to innosetup+...@googlegroups.com.

To view this discussion visit https://groups.google.com/d/msgid/innosetup/e912f8dd-458d-4c43-8f3f-ff4d4c327715n%40googlegroups.com.

[Martijn Laan]

Hey,

Documentation of the various VCL classes is beyond the scope of our documentation. The classes available in [Code] are mostly simple wrappers around the VCL classes, including the StyleName property. For further reference, see http://docwiki.embarcadero.com/RADStudio/Athens/en/VCL.

I do not believe there is currently a scenario in Inno Setup where using the StyleName property is useful.

I have made a change to the scrollbar styling of the TFolderTreeView control, and also noticed and fixed a mouseover color issue. Thank you for testing. 

Greetings,
Martijn

Op 8-10-2025 om 21:15 schreef LordFreddy073:

  Thank you for adding the 'StyleElements' property. Also could you please clarify the purpose of the new 'StyleName' property? Specifically, what does it do and in which scenarios should it be used?

 "Bug?": I hadn’t noticed before, but the VCL style is not applied to the scrollbar of 'TFolderTreeView'

  

--
You received this message because you are subscribed to the Google Groups "innosetup" group.
To unsubscribe from this group and stop receiving emails from it, send an email to innosetup+...@googlegroups.com.

To view this discussion visit https://groups.google.com/d/msgid/innosetup/CAKnaeK%3DtaKWesRsqNwE6YgSNMyAkuFCf7p5y0XeYOfQrk0tmQA%40mail.gmail.com.

[Bruno Lopes da Silva]

> Regarding sizing differences, I am not aware of any changes in sizing between modern and classic, nor between different VCL styles, including when using the native (unstyled) appearance. 

Martijn, you can reproduce the buttons sizing differences on fractional scalling 125% (1080p screen) by creating an installer with:

```

WizardStyle=modern dynamic
WizardSizePercent=100
WizardResizable=no

DialogFontName=Segoe UI
DialogFontSize=9

```

The result will be (I justposed a bit of the dark mode screenshot to clarify):

[Martijn Laan]

Hi,

Yes, that is correct. Setting 9 pt Segoe UI as the font causes a scaling difference. This behavior is unrelated to anything in version 6.6.0.

Coincidentally, we are already planning to address this in the version following 6.6.0. You will be able to use Segoe UI without a scaling difference, and 9 pt Segoe UI will become the new default font. It will then still be possible to revert to 8 pt Tahoma, also without a scaling difference.

Greetings,
Martijn

Op 10-10-2025 om 16:11 schreef Bruno Lopes da Silva:

[Martijn Laan]

Sorry, I probably misunderstood your screenshot and how it shows native and styled at once.

You used 9 pt Segoe UI for both of them?

Greetings,
Martijn

Op 10-10-2025 om 16:11 schreef Bruno Lopes da Silva:

> Regarding sizing differences, I am not aware of any changes in sizing between modern and classic, nor between different VCL styles, including when using the native (unstyled) appearance. 

Martijn, you can reproduce the buttons sizing differences on fractional scalling 125% (1080p screen) by creating an installer with:

```

WizardStyle=modern dynamic
WizardSizePercent=100
WizardResizable=no

DialogFontName=Segoe UI
DialogFontSize=9

```

The result will be (I justposed a bit of the dark mode screenshot to clarify):

To view this discussion visit https://groups.google.com/d/msgid/innosetup/02b560b9-9f63-46e5-a89a-42f7e949a287n%40googlegroups.com.

[Martijn Laan]

Hey,

I checked and the buttons are the same size (88x27 at 100% with 9 pt Segoe UI and Default.isl) but the native button as drawn by Windows (11) only uses 25 pixels of this height.

The built-in dark style uses all 27 pixels. The built-in Zircon style uses 26 pixels, with the 26th being used for a shadow.

BTW, with 8pt Tahoma the size is 75x23. With my earlier comments I meant that in the future 9pt Segoe UI will use 75x23 as well.

Greetings,
Martijn

Op 10-10-2025 om 20:01 schreef 'Martijn Laan' via innosetup:

To view this discussion visit https://groups.google.com/d/msgid/innosetup/176011930141.6.1386871028431231936.947483081%40innosetup.nl.

[Martijn Laan]

Here's how this would look. What do you think? For comparison I also included the dark version and below that the native/unstyled version.

Both styled versions are without styled title bars.

Op 9-10-2025 om 12:33 schreef Bruno Lopes da Silva:

--

[Alex Born]

If you run the innosetup-6.6.0-preview.exe installer on a system with DPI>100% and click the [Browse] button on the installation directory selection page, the directory selection dialog appears incorrectly (Windows 11 25H2).

среда, 8 октября 2025 г. в 15:00:05 UTC+2, Martijn Laan:

[Martijn Laan]

Hi Alex,

I was able to reproduce the issue and have fixed it. Thank you very much for testing.

Greetings,
Martijn

Op 11-10-2025 om 12:16 schreef Alex Born:

If you run the innosetup-6.6.0-preview.exe installer on a system with DPI>100% and click the [Browse] button on the installation directory selection page, the directory selection dialog appears incorrectly (Windows 11 25H2).

среда, 8 октября 2025 г. в 15:00:05 UTC+2, Martijn Laan:

Hi everyone,

I have released an update to the 6.6.0 preview. See the download link below.

Main improvements in this update are:

• Fixed an issue with styled title bars in high DPI scenarios, along with other DPI improvements, such as proper hint scaling (even when Setup is not in dark mode or using a custom style).
• Improved the appearance of the custom implementation for task dialogs and message boxes.
• Added new StyleElements and StyleName properties to support class TControl.
  See CodeClasses.iss for an example, which also demonstrates the use of IsDarkInstallMode.
• Included other unrelated improvements, such as:
• Improved contrast ratio for various syntax highlighting colors in the Compiler IDE, particularly in dark mode.
• Internal changes preparing for a 64-bit version of the "setup loader" program.

Like before this preview includes:

• Adding support for dark mode (forced or automatic) and custom styles to Setup and Uninstall.
  
• Includes support for dark and custom styled task dialogs.

• Includes support for right-to-left languages.

You should not use this version in production. However, please try your own scripts in dark mode or with a custom style, and report any successes or failures here. Thank you in advance.

What's new in this preview version?

Download - uses the Polar Light or Polar Dark style, depending on your Windows system settings, including styled title bars which is optional.

Updated WizardStyle help topic - includes example screenshots.

Please purchase a license or donate to support this work. Thank you! ♥

Greetings,
Martijn Laan

Screenshot of the preview installer showing the Polar Dark style when Windows is in dark mode and uses 125% DPI

--

You received this message because you are subscribed to the Google Groups "innosetup" group.
To unsubscribe from this group and stop receiving emails from it, send an email to innosetup+...@googlegroups.com.

To view this discussion visit https://groups.google.com/d/msgid/innosetup/8b237e62-fa1a-4bf0-bfae-94b83892a335n%40googlegroups.com.

[Andrew Truckle]

I adjusted my script to use png transparent and now it crashes:

The png references are:

```

WizardImageFile={#InnoPath}\Images\ms???x???.png
WizardImageFileDynamicDark={#InnoPath}\Images\ms???x???.png

``` 

If I revert to using my original bmp ones that have the white backgrounds I get no errors.

Andrew

[Andrew Truckle]

Sorry, partly my fault. I needed:

```

WizardImageFile={#InnoPath}\Images\ms???x???.bmp
WizardSmallImageFile={#InnoPath}\Images\NewPNG\msicon*.png
WizardImageFileDynamicDark={#InnoPath}\Images\ms???x???.bmp
WizardSmallImageFileDynamicDark={#InnoPath}\Images\NewPNG\msicon*.png
WizardStyle=modern dynamic

```

I was setting the png files against the wrong things. That is now sorted. But please tell me why is it that in dark mode i am still seeing white background for these png images when they are transparent? Should be dark. 

[Martijn Laan]

Hi,

See the WizardImageBackColor and WizardImageBackColor help topics, as also mentioned in the WizardImageFile and WizardSmallImageFile help topics.

The bmp vs. png part of your message I do not understand. Can you please clarify?

Greetings,
Martijn

Op 11-10-2025 om 16:35 schreef Andrew Truckle:

Sorry, partly my fault. I needed:

```

WizardImageFile={#InnoPath}\Images\ms???x???.bmp
WizardSmallImageFile={#InnoPath}\Images\NewPNG\msicon*.png
WizardImageFileDynamicDark={#InnoPath}\Images\ms???x???.bmp
WizardSmallImageFileDynamicDark={#InnoPath}\Images\NewPNG\msicon*.png
WizardStyle=modern dynamic

```

I was setting the png files against the wrong things. That is now sorted. But please tell me why is it that in dark mode i am still seeing white background for these png images when they are transparent? Should be dark. 

On Saturday, 11 October 2025 at 15:30:36 UTC+1 Andrew Truckle wrote:

I adjusted my script to use png transparent and now it crashes:

To view this discussion visit https://groups.google.com/d/msgid/innosetup/0752f3bf-579e-401a-9a3c-cdc0925abb2an%40googlegroups.com.

[Andrew Truckle]

But why isn’t the back colour automatic? If it is transparent and is using native title bar why have to state the back colour ourselves?

You received this message because you are subscribed to a topic in the Google Groups "innosetup" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/innosetup/UdtujEcEtE4/unsubscribe.
To unsubscribe from this group and all its topics, send an email to innosetup+...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/innosetup/176019505045.6.12739088335790737251.948724247%40innosetup.nl.

[Martijn Laan]

Hi,

I am not entirely sure I understand your question. Support for transparent wizard images is not new, and the wizard images and title bars are not directly related.

Are you suggesting that the default values for WizardImageBackColor and WizardSmallImageBackColor should be changed? If so, could you clarify how, keeping backward compatibility in mind? If someone was already using a transparent bmp, then the appearance should not suddenly change.

Can you also still clarify the bmp vs png part of your message. You mentioned "partly my fault." Was there an issue with how Setup handles these formats?

Thanks in advance.

Greetings,
Martijn

Op 11-10-2025 om 17:18 schreef Andrew Truckle:

To view this discussion visit https://groups.google.com/d/msgid/innosetup/CAKSr1pfDh%2BwLEKiQ9_cEX_PgB%2B89Ym_4PP5OajF%3Dnt968G1gEw%40mail.gmail.com.

[Bruno Lopes da Silva]

>  You used 9 pt Segoe UI for both of them?

Yes, Martijn. I just changed the system theme between the screenshots.

>  Here's how this would look. What do you think? For comparison I also included the dark version and below that the native/unstyled version.

In your non-scalled screenshots I still can notice the styled buttons are bigger than the native ones so still a problem.

(I must add that, while my screenshot does not show, the sizing difference make the Back and Next buttons slightly overlap when one of them is hovered by the mouse, so this is a problem)

[Bruno Lopes da Silva]

Ah, now I see there is a new "modern windows11" light variant. Thank you.

But why it have the same grey background from Windows XP era? 

Should not the default background color on such theme be white which is used since Windows Vista?

[Andrew Truckle]

> Are you suggesting that the default values for WizardImageBackColor and WizardSmallImageBackColor should be changed? If so, could you clarify how, keeping backward compatibility in mind? If someone was already using a transparent bmp, then the appearance should not suddenly change.

I see the docs say:

| The standard WizardImageFile, WizardSmallImageFile, WizardImageBackColor, WizardSmallImageBackColor, and WizardStyleFile settings are used for dynamic light mode.

And for the dark version:

----

[Setup]: WizardSmallImageBackColorDynamicDark
Default value:

clNone
Description:
Overrides WizardSmallImageBackColor when using WizardStyle with dynamic mode and Windows is in dark mode. Ignored otherwise.

For all details see WizardSmallImageBackColor.

---

I just don't understand why it is not using the window colour. According to this help text for WizardSmallImageBackColor :

===
Default value:

clNone if the built-in small wizard image is used, clWindow otherwise.

===

I am using my own. so it shiould be using clWindow.  So for dynamic dark mode i thought it would use the window back colour and not white.

> Can you also still clarify the bmp vs png part of your message. You mentioned "partly my fault." Was there an issue with how Setup handles these formats?

This can be ignored. I was updating WizardImageFile instead of WizardSmallImageFile. No problem there.

[Martijn Laan]

Hi,

Op 11-10-2025 om 18:21 schreef Andrew Truckle:

I am using my own. so it shiould be using clWindow.  So for dynamic dark mode i thought it would use the window back colour and not white.

Thanks, I understand now. The image controls aren’t aware of styles at the moment so they're not asking the style for its version of clWindow. I should be able to fix that, thanks for reporting.

Greetings,
Martijn

[Martijn Laan]

Hi,

Op 11-10-2025 om 17:46 schreef Bruno Lopes da Silva:

>  You used 9 pt Segoe UI for both of them?

Yes, Martijn. I just changed the system theme between the screenshots.

>  Here's how this would look. What do you think? For comparison I also included the dark version and below that the native/unstyled version.

In your non-scalled screenshots I still can notice the styled buttons are bigger than the native ones

I know they appear bigger in this specific style, but the actual sizes are the same. You can confirm that by outputting the sizes using [Code] or by inspecting them with a tool like Microsoft's Spy++.

 so still a problem.

Why is it a problem?

(I must add that, while my screenshot does not show, the sizing difference make the Back and Next buttons slightly overlap when one of them is hovered by the mouse, so this is a problem)

Are you sure? I tried 8 pt Tahoma at 100%, 9 pt Segoe UI at 100%, and 9 pt Segoe UI at 125% and in all cases the buttons are touching in this style, and not overlapping.

They are in fact always touching but Windows 11's own native style does not use all space like I said, making them appear to not touch.

Greetings,
Martijn

To view this discussion visit https://groups.google.com/d/msgid/innosetup/4540ae89-51f0-495c-8f80-16f3ee5173ecn%40googlegroups.com.

[Martijn Laan]

Hi,

Op 11-10-2025 om 17:53 schreef Bruno Lopes da Silva:

But why it have the same grey background from Windows XP era? 

It's correct the background isn't full white, but it's also nowhere near the grey from Windows XP.

It is in fact almost the same color as Windows 11 itself uses in for example the settings screen: the one from the style is even a little bit less grey (#F9F9F9 for the style vs #F3F3F3 for Windows 11).



Having said that, to be clear, I am not the author of any of these styles.

They are all from Embarcadero. There are more available than the few I built in and you can use those as well via WizardStyleFile and WizardStyleFileDynamicDark.

You can browse them at https://getitnow.embarcadero.com/category/styles and the ones saying 'Not Required' under 'Subscription' are free. Downloading requires a Delphi installation AFAIK, which may be a Community Edition for the free styles.

Another source of VCL Styles files is https://www.delphistyles.com/vcl/

FireMonkey (FMX) Styles files are not supported.

Greetings,
Martijn

[Martijn Laan]

Hey,

Op 11-10-2025 om 18:54 schreef 'Martijn Laan' via innosetup:

 They are in fact always touching but Windows 11's own native style does not use all space like I said, making them appear to not touch.

I've now made it so when a custom style is active it adds a 2-pixel space between the buttons, regardless of DPI.

This makes things look similar to Windows 11 for all built-in styles, except for Zircon because that one is already like Windows 11. So with Zircon active there will be a 4-pixel space. Adding a directive to be able to change this does not seem worth it.

Greetings,
Martijn

[Bruno Lopes da Silva]

Hi. Martin, thanks for the triaging and fixes regarding the new windows 11 light theme and back/next spacing.

[Martijn Laan]

Hi everyone,

I have released a second update to the 6.6.0 preview. See the download link below.

This update:

• Adds a new built-in 'windows11' style, enabling a light counterpart of the built-in dark style.
• Improves TFolderTreeView styling.
• Makes setting the StyleName property to 'windows' to disable styling of a specific control work.
• Fixes an issue with icon colors in message boxes in dark Uninstall.
• Fixes an issue with browse for folder dialogs when DPI > 100%.
• Makes bitmap image controls style aware when BackColor=clWindow.
• Keeps the Back and Next buttons apart when styled, both in Setup and in the Compiler IDE's New Script Wizard.

And also (not related to dark mode or custom styles):

• Compiler IDE: Updates the default dialog font from 8pt Segoe UI to 9pt Segoe UI.
• Adds a few Pascal Scripting functions.
• Reverts the change made to the CurPageChanged event function in version 6.5.0.
• Fixes issue with the shared file dialog in Uninstall. This issue is not present in 6.5.4.

[LordFreddy073]

  Hi, thanks for the update. I’ve found a bug in the TFolderTreeView class — please see the attached video.  

--

You received this message because you are subscribed to the Google Groups "innosetup" group.
To unsubscribe from this group and stop receiving emails from it, send an email to innosetup+...@googlegroups.com.

To view this discussion visit https://groups.google.com/d/msgid/innosetup/176043916599.8.17456578350087415010.952661525%40innosetup.nl.

[Martijn Laan]

Hi,

Impressive find, thank you. I was able to reproduce. Please try this version:

https://files.jrsoftware.org/is/dev/innosetup-6.6.0-preview-2.exe

You will get a SmartScreen warning and that's ok.

Greetings,
Martijn

Op 14-10-2025 om 14:08 schreef LordFreddy073:

To view this discussion visit https://groups.google.com/d/msgid/innosetup/CAKnaeKkZNW-cxmhvYdvL3RJs5yDzv6%2BmnwCq6niTJQcHnvbRRg%40mail.gmail.com.

[Jernej Simončič]

On Tuesday, October 14, 2025, 14:08:52, LordFreddy073 wrote:

  Hi, thanks for the update. I’ve found a bug in the TFolderTreeView class — please see the attached video.  

Just curious – what tool did you use to make the video (I'm mostly interested in the mouse visualisation)?

 

-- 
< Jernej Simončič ><><><><>< https://eternallybored.org/ >

The obvious answer is always overlooked.
       -- Whitehead's Law

[Andrew Truckle]

Thanks! The wizard icon now have the correct background. And I updated the script to use windows11 colours for light mode.

Andrew

[LordFreddy073]

Thanks for the fix — it’s working perfectly now.  

[LordFreddy073]

Hi — I used OBS for video capture, and SpotOnTheMouse for mouse visualization.

[LordFreddy073]

Hi — I’ve developed a custom script to replace the native BrowseForFolder function. However, when I enable IncludeTitleBar in WizardStyle, the custom dialog becomes visually buggy (please see the attached screenshots). Could you please advise on how to resolve this issue? Thank you!

[Martijn Laan]

Hi,

Are you using CreateCustomForm for this in the same way as CodeClasses.iss does? It does not show this problem for me.

Can you please provide a minimal script that does show the problem?

Styled title bars change the non-client area of forms and are very sensitive in my experience.

Greetings,
Martijn

Op 14-10-2025 om 18:01 schreef LordFreddy073:

Hi — I’ve developed a custom script to replace the native BrowseForFolder function. However, when I enable IncludeTitleBar in WizardStyle, the custom dialog becomes visually buggy (please see the attached screenshots). Could you please advise on how to resolve this issue? Thank you!

--
You received this message because you are subscribed to the Google Groups "innosetup" group.
To unsubscribe from this group and stop receiving emails from it, send an email to innosetup+...@googlegroups.com.

To view this discussion visit https://groups.google.com/d/msgid/innosetup/CAKnaeK%3D%2B9tae4f7Q7fQRDb97sH%2BqELtYKqrU4Ohgz72s9QgKRg%40mail.gmail.com.

[LordFreddy073]

Yes!

On Tue, Oct 14, 2025 at 8:20 PM 'Martijn Laan' via innosetup <inno...@googlegroups.com> wrote:

Are you using CreateCustomForm for this in the same way as CodeClasses.iss does? It does not show this problem for me.

 

You can reproduce the bug by adding the following lines to the FormButtonOnClick procedure inside CodeClasses.iss:

procedure FormButtonOnClick(Sender: TObject);
var
  Form: TSetupForm;
  Edit: TNewEdit;
  OKButton, CancelButton: TNewButton;
  W: Integer;
begin
  Form := CreateCustomForm();
  try
    Form.ClientWidth := ScaleX(256);
    Form.ClientHeight := ScaleY(128);
    with Form.Constraints do
    begin
      MaxWidth := Form.Width;
      MaxHeight := Form.Height;
      MinWidth := Form.Width;
      MinHeight := Form.Height;
    end;
    Form.Position := poDesktopCenter;
    Form.Caption := 'TSetupForm';
.
.
.
end;

[Martijn Laan]

Hi,

I suppose your Constraints break Delphi's TFormStyleHook.UpdateForm, which first decreases the form size by 1 and then increases it with 1 again 🤷

It has a comment saying: "// need to update non-client and client size of the styled form"

So you should just remove your Constraints code again? The form isn't resizeable by the user anyway.

Greetings,
Martijn

Op 14-10-2025 om 19:33 schreef LordFreddy073:

--

You received this message because you are subscribed to the Google Groups "innosetup" group.
To unsubscribe from this group and stop receiving emails from it, send an email to innosetup+...@googlegroups.com.

To view this discussion visit https://groups.google.com/d/msgid/innosetup/CAKnaeKkeJf6k6D3q_1xF2ohwZxtf9xdvmt_%2BbxY06CKAgY4d3w%40mail.gmail.com.

[LordFreddy073]

Understood, I’ll make those changes. However, I noticed something curious: if I remove the Position property or move it above the ClientWidth property, the issue no longer occurs. Could you please explain why that happens?  

[Martijn Laan]

Hi,

No, sorry. You would need to ask Embarcadero about that. The VCL is sensitive to the order of operations in many ways, and you cannot arbitrarily rearrange property assignments.

To be honest, I recommend removing the code you added to set the Position property. This manual assignment is both inferior to, and inconsistent with, the automatic positioning that is already built in.

I suggest following the approach shown in CodeClasses.iss.

Greetings,
Martijn

Op 14-10-2025 om 20:07 schreef LordFreddy073:

> Understood, I’ll make those changes. However, I noticed something curious: if I remove the Position property or move it above the ClientWidth property, the issue no longer occurs. Could you please explain why that happens?  

Greetings,
Martijn

Op 14-10-2025 om 20:07 schreef LordFreddy073:

--

You received this message because you are subscribed to the Google Groups "innosetup" group.
To unsubscribe from this group and stop receiving emails from it, send an email to innosetup+...@googlegroups.com.

To view this discussion visit https://groups.google.com/d/msgid/innosetup/CAKnaeKkxtOrpVUb0kWYsAc0BYnEfOXZPL8s5sHhtMWPSyU8YNQ%40mail.gmail.com.

[Bruno Lopes da Silva]

> I have released a second update to the 6.6.0 preview. See the download link below.

Hi, Martijn. There is some way to keep using the Windows native icons instead of the custom Inno ones on dark mode?

On modern style we have IDI_QUESTION:

But on dark mode we have this one:

[Martijn Laan]

Hi,

No, there isn’t. But they wouldn’t be suitable for dark mode anyway since these are light icons.

Also, you should be aware that Windows doesn’t actually support dark mode internally. This is why every application has to reinvent the wheel.

Greetings,
Martijn

Op 15-10-2025 om 13:22 schreef Bruno Lopes da Silva:

> I have released a second update to the 6.6.0 preview. See the download link below.

Hi, Martijn. There is some way to keep using the Windows native icons instead of the custom Inno ones on dark mode?

On modern style we have IDI_QUESTION:

But on dark mode we have this one:

--

You received this message because you are subscribed to the Google Groups "innosetup" group.
To unsubscribe from this group and stop receiving emails from it, send an email to innosetup+...@googlegroups.com.

To view this discussion visit https://groups.google.com/d/msgid/innosetup/c626baa3-3ed5-47e7-8303-9cff758dcba8n%40googlegroups.com.

[Jernej Simončič]

On Wednesday, October 15, 2025, 13:56:01, 'Martijn Laan' via innosetup wrote:

Also, you should be aware that Windows doesn’t actually support dark mode internally.

*cough*

 

:)

 

(actually, I just noticed a problem – there's no text in the message box titlebar, and it's the same with the About Setup message box)

 

-- 
< Jernej Simončič ><><><><>< https://eternallybored.org/ >

The one day you'd sell your soul for something, souls are a glut.
       -- Mason's First Law of Synergism

[Martijn Laan]

Hey,

That just looks like a native message box with a high-contrast theme active, or am I misunderstanding?

I know there are high-contrast themes that are dark, which just makes it extra strange that Windows has no real dark mode support. You would think they could have combined that with the Aero theming resources, but those are also only partially implemented. And the parts that are implemented are undocumented. It's extremely annoying.

Greetings,
Martijn

Op 15-10-2025 om 14:07 schreef Jernej Simončič:

On Wednesday, October 15, 2025, 13:56:01, 'Martijn Laan' via innosetup wrote:

Also, you should be aware that Windows doesn’t actually support dark mode internally.

*cough*

 

:)

 

(actually, I just noticed a problem – there's no text in the message box titlebar, and it's the same with the About Setup message box)

 

-- 
< Jernej Simončič ><><><><>< https://eternallybored.org/ >

The one day you'd sell your soul for something, souls are a glut.
       -- Mason's First Law of Synergism

--
You received this message because you are subscribed to the Google Groups "innosetup" group.
To unsubscribe from this group and stop receiving emails from it, send an email to innosetup+...@googlegroups.com.

To view this discussion visit https://groups.google.com/d/msgid/innosetup/1778743940.20251015140721%40eternallybored.org.

[Jernej Simončič]

On Wednesday, October 15, 2025, 14:20:17, 'Martijn Laan' via innosetup wrote:

That just looks like a native message box with a high-contrast theme active, or am I misunderstanding?

Correct. However, while making that screenshot, I noticed that Inno's message box aren't showing any text in the titlebar, which I thought was an Inno bug, but it seems to be a problem with my RDP connection to home, as I tried on another computer (with same settings), and titlebar text appears fine there.

 

I know there are high-contrast themes that are dark, which just makes it extra strange that Windows has no real dark mode support. You would think they could have combined that with the Aero theming resources, but those are also only partially implemented. And the parts that are implemented are undocumented. It's extremely annoying.

Yea, Windows has supported changing window colours at least since Windows 3.1, and still provides everything needed for programs to use those colours, even if themes removed support for letting user change them. Instead they reinvented the wheel for dark mode.

 

-- 
< Jernej Simončič ><><><><>< https://eternallybored.org/ >

Always remember to pillage before you burn.
       -- Attila's Instruction

[Bruno Lopes da Silva]

> No, there isn’t. But they wouldn’t be suitable for dark mode anyway since these are light icons.

Most of them are on medium luminance spectrum. IMO they fit well on both styles (modern and modern dynamic).

The IDI_WARNING, for example, looks like this on this dialog we created with Inno and Windows API:

>  Also, you should be aware that Windows doesn’t actually support dark mode internally. This is why every application has to reinvent the wheel.

Well, I know, and you are doing a great job. Even so, that does not mean the icons need to be (even more) reinveted (I say "even more" because Inno used to have even more native icons but there is a movement on Inno of replacing them in favor of proprietary/custom ones: https://groups.google.com/g/innosetup/c/wiIsKBqqTg0/m/9GrWCTSFAQAJ). This makes the installer look "less native".

Anyway, gimp users lived years with Win32 light mode only, they continue with light mode.

[Martijn Laan]

Hi,

Thanks for the screenshot. Which API did you use and is it able to get icons of at least 64x64 for high DPI as well?

Greetings,

Martijn

-------- Original Message --------

On Wednesday, 10/15/25 at 19:41 Bruno Lopes da Silva <brunv...@gmail.com> wrote:

> No, there isn’t. But they wouldn’t be suitable for dark mode anyway since these are light icons.

Most of them are on medium luminance spectrum. IMO they fit well on both styles (modern and modern dynamic).

The IDI_WARNING, for example, looks like this on this dialog we created with Inno and Windows API:

To view this discussion visit https://groups.google.com/d/msgid/innosetup/d87620f9-e0f1-4c42-9b0c-edd9f88a29fdn%40googlegroups.com.

[Andrew Truckle]

It look more like a task dialog. I use the task dialog for message boxes in my app since I have the darktaskdialog wrapper on GitHub for c++. 

You received this message because you are subscribed to a topic in the Google Groups "innosetup" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/innosetup/UdtujEcEtE4/unsubscribe.
To unsubscribe from this group and all its topics, send an email to innosetup+...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/innosetup/176053083430.6.5009598357271574330.954627336%40innosetup.nl.

[Martijn Laan]

Task dialogs don’t display help (‘?’) icons.  

Greetings,

Martijn

-------- Original Message --------

To view this discussion visit https://groups.google.com/d/msgid/innosetup/CAKSr1peo9i8cDagJnCfS%3DbbxDB%2BJgcNTHySaZ%3DJ%2B_SnZo%3D-U%3DQ%40mail.gmail.com.

[Bruno Lopes da Silva]

> Thanks for the screenshot. Which API did you use and is it able to get icons of at least 64x64 for high DPI as well?

We use `ExtractIcon` targeting Windows 10/11 imageres.dll: https://gitlab.gnome.org/GNOME/gimp/-/blob/master/build/windows/installer/util_MessageWithURL.isi#L217. Viewing such dialog on 175% scaling is crisp but the icon size choosen (by Windows?) is 50px:

The icon we handle scaling in an explicit way to 64px (which is used by 175% fractional scaling and beyond) is the folder icon: https://gitlab.gnome.org/GNOME/gimp/-/blob/master/build/windows/installer/base_gimp3264.iss?ref_type=heads#L1068. But it looks distorted IMO.

You can see by yourself: https://download.gimp.org/gimp/v3.1/windows/gimp-3.1.4-setup.exe

[Martijn Laan]

Hi,

I see, thanks. There are quite a few Win32 API calls that can retrieve these icons in different ways, but directly accessing imageres.dll is not one of them. In other words, this is an undocumented technique and not really suitable for use in an installer.

However, I suspect that SHGetStockIconInfo, when used together with SHGSI_ICONLOCATION, might return imageres.dll as the source. I will look into this later. LoadIconWithScaleDown also seems like a good candidate. I was not aware of either of these before.

By the way, task dialogs allow URLs. I would therefore recommend using a task dialog instead, especially since it appears that you introduced the code because you wanted to show a URL. 

Greetings,
Martijn

Op 16-10-2025 om 01:33 schreef Bruno Lopes da Silva:

> Thanks for the screenshot. Which API did you use and is it able to get icons of at least 64x64 for high DPI as well?

We use `ExtractIcon` targeting Windows 10/11 imageres.dll: https://gitlab.gnome.org/GNOME/gimp/-/blob/master/build/windows/installer/util_MessageWithURL.isi#L217. Viewing such dialog on 175% scaling is crisp but the icon size choosen (by Windows?) is 50px:

To view this discussion visit https://groups.google.com/d/msgid/innosetup/3847404b-88f8-48bc-8288-fee9536a36a9n%40googlegroups.com.

[Andrew Truckle]

I cater for help icon too on win32 using documented functions:

int CMeetingScheduleAssistantApp::DoMessageBox(LPCTSTR lpszPrompt, UINT nType, UINT nIDPrompt)
{
CString strContent = CString(lpszPrompt);
CString strTitle = CString();

if (!CTaskDialog::IsSupported())
return CWinAppEx::DoMessageBox(lpszPrompt, nType, nIDPrompt);

VERIFY(strTitle.LoadString(AFX_IDS_APP_TITLE));
CTaskDialog dlgTaskMessageBox(strContent, _T(""), strTitle);

dlgTaskMessageBox.SetDialogWidth(DetectMessageBoxWidth());
HICON hQuestionIcon = ::LoadIcon(nullptr, IDI_QUESTION);

// Icon
switch (nType & MB_ICONMASK)
{
case MB_ICONERROR:
dlgTaskMessageBox.SetMainIcon(TD_ERROR_ICON);
break;
case MB_ICONWARNING:
dlgTaskMessageBox.SetMainIcon(TD_WARNING_ICON);
break;
case MB_ICONINFORMATION:
dlgTaskMessageBox.SetMainIcon(TD_INFORMATION_ICON);
break;
case MB_ICONQUESTION:
dlgTaskMessageBox.SetMainIcon(hQuestionIcon);
break;
default:
break;
}

// Buttons
int nCommonButtons = 0;
switch (nType & MB_TYPEMASK)
{
case MB_YESNOCANCEL:
nCommonButtons |= TDCBF_CANCEL_BUTTON;
[[fallthrough]];
case MB_YESNO:
nCommonButtons |= TDCBF_YES_BUTTON | TDCBF_NO_BUTTON;
break;

case MB_RETRYCANCEL:
nCommonButtons |= TDCBF_RETRY_BUTTON | TDCBF_NO_BUTTON;
break;

case MB_OKCANCEL:
nCommonButtons |= TDCBF_CANCEL_BUTTON;
[[fallthrough]];
case MB_OK:
default:
nCommonButtons |= TDCBF_OK_BUTTON;
}
dlgTaskMessageBox.SetCommonButtons(nCommonButtons);

return static_cast<int>(dlgTaskMessageBox.DoModal());
}

To view this discussion visit https://groups.google.com/d/msgid/innosetup/176056262340.6.11089180541256062224.955573532%40innosetup.nl.

[Jernej Simončič]

On Thursday, October 16, 2025, 08:32:05, 'Martijn Laan' via innosetup wrote:

By the way, task dialogs allow URLs. I would therefore recommend using a task dialog instead, especially since it appears that you introduced the code because you wanted to show a URL. 

This dialog predates Inno's support for task dialogs :)

 

-- 
< Jernej Simončič ><><><><>< https://eternallybored.org/ >

The only people making money these days are the ones who sell computer paper.
       -- Wain's Conclusion

[Martijn Laan]

Sorry, I meant when you create task dialogs yourself using the Win32 API.

Currently the built-in task dialog support does not allow links I think, and improving that is on my list of things to do. 

Greetings,

Martijn

-------- Original Message --------

--

You received this message because you are subscribed to the Google Groups "innosetup" group.
To unsubscribe from this group and stop receiving emails from it, send an email to innosetup+...@googlegroups.com.

To view this discussion visit https://groups.google.com/d/msgid/innosetup/597625804.20251016095000%40eternallybored.org.

[Martijn Laan]

Hi,

I was able to find the right combination of Win32 API calls to get to the high-dpi versions of all stock icons, for use in message boxes, task dialogs, built-in wizard pages, and your own custom wizard pages.

Examples below. The full list of available icons can be seen at https://learn.microsoft.com/en-us/windows/win32/api/shellapi/ne-shellapi-shstockiconid

Greetings,
Martijn

[Martijn Laan]

Hi everyone,

I have released a third and hopefully final update to the 6.6.0 preview. See the download link below.

Changes:

• Setup now always uses high-quality, system-defined icons instead of custom ones on message boxes, task dialogs, the 'Select Destination Location' and 'Preparing to Install' wizard pages, and on the 'Setup Needs the Next Disk' form.
  
  You can use these icons from [Code] as well, see the new custom page added to CodeClasses.iss.
  
  
• Updated Setup and Uninstall's default regular font from 8-point Tahoma to 9-point Segoe UI, without changes in scaling. Also updated Setup's default large font used on the 'Welcome' and 'Setup Completed' wizard pages from 12-point Verdana to 14-point Segoe UI.
  
  The revision history and the help file explain how to revert to the old fonts again if you want.
  
  
• The BrowseForFolder function which can be called from [Code] and is used by the 'Setup Needs the Next Disk' form (but not the 'Select Destination Location' wizard page) has been updated to use the modern folder picker from Windows.
  
  
• The preview installer itself now uses the windows11 custom style instead of polar.

Like before this preview includes:

• Adding support for dark mode (forced or automatic) and custom styles to Setup and Uninstall.
  
• Includes support for dark and custom styled task dialogs.
• Includes support for right-to-left languages.

You should not use this version in production. However, please try your own scripts (including uninstallation) in dark mode or with a custom style, and report any successes or failures here. Thank you in advance.

What's new in this preview version?

Download - uses the windows11 light or dark style, depending on your Windows system settings, including styled title bars which is optional.

[Andrew Truckle]

When I compile with latest version I get 2 warnings:

1> Warning: The [LangOptions] section directive "TitleFontSize" is obsolete and ignored in this version of Inno Setup.
1> Warning: The [LangOptions] section directive "CopyrightFontSize" is obsolete and ignored in this version of Inno Setup.

But I have no [LangOptions] in my ISS to my knowledge?

[Andrew Truckle]

Also:

CheckCompilerVersionUsed Exception - 'Input string was not in a correct format.'

[Martijn Laan]

Hi,

Thanks for testing.

I suspect one of your translations sets these directives. They have been obsolete for some time now but a warning was missing.

Greetings,
Martijn

Op 23-10-2025 om 10:57 schreef Andrew Truckle:

--

You received this message because you are subscribed to the Google Groups "innosetup" group.
To unsubscribe from this group and stop receiving emails from it, send an email to innosetup+...@googlegroups.com.

To view this discussion visit https://groups.google.com/d/msgid/innosetup/54cbdc95-6f99-4294-a75c-3d47899139b8n%40googlegroups.com.

[Martijn Laan]

Hi,

Op 23-10-2025 om 11:00 schreef Andrew Truckle:

CheckCompilerVersionUsed Exception - 'Input string was not in a correct format.'

Sorry, I am not sure what you mean. "CheckCompilerVersionUsed" is not a string I can find in Inno Setup.

Can you please provide an example that reproduces the problem?

Greetings,
Martijn Laan

[Andrew Truckle]

You are right:

Search "[LangOptions]" (77 hits in 40 files of 1198 searched) [Extended]
  D:\My Programs\2022\MeetSchedAssist\Inno\l.ara\Arabic.isl (2 hits)
Line  11: [LangOptions]
  D:\My Programs\2022\MeetSchedAssist\Inno\l.guj\Gujarati.isl (2 hits)
Line  11: [LangOptions]
  D:\My Programs\2022\MeetSchedAssist\Inno\l.ind\Indonesian.isl (1 hit)
Line  14: [LangOptions]

[Andrew Truckle]

Hi, for this matter I confirm that the issue is outside of Inno building. It is either Visual Studio of the Visual & Installer compiler.

Andrew

--
You received this message because you are subscribed to a topic in the Google Groups "innosetup" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/innosetup/UdtujEcEtE4/unsubscribe.
To unsubscribe from this group and all its topics, send an email to innosetup+...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/innosetup/176121232024.7.11564611783151218502.967737816%40innosetup.nl.

[Bruno Lopes da Silva]

As a regression, the buttons are now rather tiny (almost without margings around the text inside the button itself).

This is inconsistent with the previous code which rendered the native buttons on the "right size" for 125% scaling, the same as Win + R dialog

NOTE: I have disabled my [LangOptions] since the preview 3 have Segoe UI as default.

[Martijn Laan]

Hi,

I am not sure what the screenshot is supposed to show, but Windows uses two different sizes of buttons.

Larger ones like the Open common dialog for example.
Smaller ones like in task dialogs and Vista-style wizards for example.

If you want the sizes you had with 9pt Segoe UI in 6.5 then set the following, as explained in whatsnew and the help:

[LangOptions]
DialogFontBaseScaleHeight=13
DialogFontBaseScaleWidth=6

Without this default sizes will be the same as they were in 6.5, which is the same as for example Windows task dialogs.

Greetings,
Martijn

Op 23-10-2025 om 18:45 schreef Bruno Lopes da Silva:

[Bruno Lopes da Silva]

> If you want the sizes you had with 9pt Segoe UI in 6.5 then set the following, as explained in whatsnew and the help:

Thank you. I can confirm DialogFontBaseScaleHeight=13 + DialogFontBaseScaleWidth=6 combo restores the larger buttons we are used on GIMP installer.

---

Now, the only difference I see on 6.6.0 preview 3 (on the right of the image below) is the position of the title ("Acordo de Licensiamento"), which is 3px closer to the title bar compared to the previous Inno.

The subtitle ("Por favor..") is 1px closer to the title compared to before preview 3.

Anyway, just to keep this written, maybe not a big deal. The installer looks very good with the new native icons and such👍.

[Martijn Laan]

Hi,

Op 24-10-2025 om 16:40 schreef Bruno Lopes da Silva:

Now, the only difference I see on 6.6.0 preview 3 (on the right of the image below) is the position of the title ("Acordo de Licensiamento"), which is 3px closer to the title bar compared to the previous Inno.

Yes, the alignment and sizing of the two top labels have been improved and fixed.

There will be more such improvements in the final 6.6 release.

Greetings,
Martijn

[Andrew Truckle]

With the dark mode being such a big feature (IMHO) how do you feel about jumping straight to 7.0? Instead of 6.6?

--
You received this message because you are subscribed to a topic in the Google Groups "innosetup" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/innosetup/UdtujEcEtE4/unsubscribe.
To unsubscribe from this group and all its topics, send an email to innosetup+...@googlegroups.com.

To view this discussion visit https://groups.google.com/d/msgid/innosetup/176124180278.7.7594882515178191506.968620899%40innosetup.nl.

[Martijn Laan]

Hi,

I'm glad to hear you like the dark mode so much. To me, a major version jump usually suggests breaking backward compatibility. However, I've worked hard to ensure that backward compatibility is preserved, so I think 6.6 is a better match.

Greetings,
Martijn

Op 27-10-2025 om 14:37 schreef Andrew Truckle:

With the dark mode being such a big feature (IMHO) how do you feel about jumping straight to 7.0? Instead of 6.6?

On Thu, 23 Oct 2025 at 18:50, 'Martijn Laan' via innosetup <inno...@googlegroups.com> wrote:

Hi,

I am not sure what the screenshot is supposed to show, but Windows uses two different sizes of buttons.

Larger ones like the Open common dialog for example.
Smaller ones like in task dialogs and Vista-style wizards for example.

If you want the sizes you had with 9pt Segoe UI in 6.5 then set the following, as explained in whatsnew and the help:

[LangOptions]
DialogFontBaseScaleHeight=13
DialogFontBaseScaleWidth=6

Without this default sizes will be the same as they were in 6.5, which is the same as for example Windows task dialogs.

Greetings,
Martijn

Op 23-10-2025 om 18:45 schreef Bruno Lopes da Silva:

As a regression, the buttons are now rather tiny (almost without margings around the text inside the button itself).

This is inconsistent with the previous code which rendered the native buttons on the "right size" for 125% scaling, the same as Win + R dialog

NOTE: I have disabled my [LangOptions] since the preview 3 have Segoe UI as default.

--
You received this message because you are subscribed to a topic in the Google Groups "innosetup" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/innosetup/UdtujEcEtE4/unsubscribe.
To unsubscribe from this group and all its topics, send an email to innosetup+...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/innosetup/176124180278.7.7594882515178191506.968620899%40innosetup.nl.

--

You received this message because you are subscribed to the Google Groups "innosetup" group.

To unsubscribe from this group and stop receiving emails from it, send an email to innosetup+...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/innosetup/CAKSr1pdPQGrL8M1LpFGRmw8L6nNYgBBFNhUbDtRQQxUBN%3DCexg%40mail.gmail.com.

[Martijn Laan]

Hi everyone,

I have released a fourth update to the 6.6.0 preview. See the download link below.

A fourth update wasn't planned initially, but we did more improvements than expected. Please try them out.

Changes related to custom styles:

• Added new excludelightbuttons modifier: Disables custom styling of all buttons (including command link buttons, as used in task dialogs) when a light style is active.
• The preview installer now uses this style: modern dynamic windows11 excludelightbuttons.
• Other minor improvements and fixes.

Other changes to the look and feel:

• WizardSizePercent now always defaults to 120,120, instead of only when you are using WizardStyle=modern. As a result, if you are using WizardStyle=classic, your Setup windows will increase in size by 20% by default.
• WizardSizePercent is now supported by Uninstall. As a result, your uninstaller window will increase in size by 20% by default.
• Setup and Uninstall now keep the original aspect ratio of their windows when scaling for DPI. As a result, your Setup and Uninstall windows will by default be 16% wider at 125% DPI or higher. Can be disabled by setting new [Setup] section directive WizardKeepAspectRatio to no.
• Support for [Setup] section directive WizardResizable has been dropped, so the user will no longer be able to resize the main Setup wizard window. This change, together with the next one, has enabled several alignment improvements.
• Wizard form sizing for WizardSizePercent is now done before event function InitializeWizard is called, instead of after, consistent with scaling for system DPI or for a custom DialogFontSize. If you have custom controls that must grow with WizardSizePercent, and those controls use the Anchors property to achieve this (that is, they have both akLeft and akRight set, or both akTop and akBottom set), and they do not use SurfaceWidth or SurfaceHeight, you must either start using the new SurfaceExtraWidth and SurfaceExtraHeight properties (as demonstrated by the updated CodeClasses.iss example script), or switch to using SurfaceWidth and SurfaceHeight. Existing custom code that assigns the Anchors property can be removed from your scripts.
• The prototype of support function CreateCustomForm has changed. Support class TSetupForm has changed as well: function FlipSizeAndCenterIfNeeded has been renamed to FlipAndCenterIfNeeded, property SizeAndCenterOnShow has been renamed to CenterOnShow, and property KeepSizeX is now read-only. See CodeClasses.iss for an updated CreateCustomForm/TSetupForm example.

Other changes:

• Security improvements.
• Compiler IDE: Enabled dark mode support for the menus on Windows 11 Version 25H2 (2025 Update).
• Setup command line parameter '/SUPPRESSMSGBOXES' can now suppress additional early fatal error messages and the final restart error message.

Like before this preview includes:

• Adding support for dark mode (forced or automatic) and custom styles to Setup and Uninstall.
  
• Includes support for dark and custom styled task dialogs.
• Includes support for right-to-left languages.

• Segoe UI as the font for Setup and Uninstall, without changes in scaling.
• The use of system-defined icons instead of custom ones in a few places. 

You should not use this version in production. However, please try your own scripts (including uninstallation) in dark mode or with a custom style, and report any successes or failures here. Thank you in advance.

What's new in this preview version?

Download - uses the windows11 light or dark style, depending on your Windows system settings, excluding buttons when a light style is active, which is optional.

[Bruno Lopes da Silva]

Hi, Martijn. I tested the Preview 4 and noticed that there is a string ("Exit Setup?") not being displayed in the dark mode version of the exit message dialog:

The margin is also different, way smaller (probably because it is a custom messsage dialog). The native light dialog have more margin and I think would be interesting to replicate that.

[Martijn Laan]

Thanks. 

What DPI and DialogFontName/Size settings is this?

Greetings,

Martijn 

-------- Original Message --------

--

You received this message because you are subscribed to the Google Groups "innosetup" group.
To unsubscribe from this group and stop receiving emails from it, send an email to innosetup+...@googlegroups.com.

To view this discussion visit https://groups.google.com/d/msgid/innosetup/22ce33ec-01ec-4b3a-a954-e4c4d18834f0n%40googlegroups.com.

[Martijn Laan]

Hi,

Op 5-11-2025 om 16:19 schreef Bruno Lopes da Silva:

noticed that there is a string ("Exit Setup?") not being displayed in the dark mode version of the exit message dialog

Was able to fix this, thanks.

Greetings,
Martijn

[Bruno Lopes da Silva]

Thanks. I just noticed another difference, now on task dialog (don't know if it was fixed by 1285016) 😅:

The native one in light mode have the installer icon on the title bar and in the dialog itself:

The one in dark mode do not have the icon (and the margins, buttons sizes are different, lack of bottom bezel etc):

Thanks in advance.

[Martijn Laan]

Hi,

Thanks. I was able to reproduce the issue. It's been an issue in all previews I believe.

You need to use dynamic mode, set Windows to dark mode and use a custom SetupIconFile.

Setup will then expect there to be two icons available, light + dark, and will want to use the dark one, but it's not there because of the custom SetupIconFile.

As for the other differences, these are known and, in my opinion, reasonable. There are similar differences between native message boxes and task dialogs as well, and I am not planning to attempt to recreate them. To avoid such differences between light and dark mode, I have added the built-in windows11 custom style earlier. 

But thanks for reporting them anyway.

Greetings,
Martijn

Op 5-11-2025 om 19:38 schreef Bruno Lopes da Silva:

Thanks. I just noticed another difference, now on task dialog (don't know if it was fixed by 1285016) 😅:

The native one in light mode have the installer icon on the title bar and in the dialog itself:

The one in dark mode do not have the icon (and the margins, buttons sizes are different, lack of bottom bezel etc):

Thanks in advance.

Em quarta-feira, 5 de novembro de 2025 às 13:04:24 UTC-3, Martijn Laan escreveu:

Hi,

Op 5-11-2025 om 16:19 schreef Bruno Lopes da Silva:

noticed that there is a string ("Exit Setup?") not being displayed in the dark mode version of the exit message dialog

Was able to fix this, thanks.

Greetings,
Martijn

--

You received this message because you are subscribed to the Google Groups "innosetup" group.
To unsubscribe from this group and stop receiving emails from it, send an email to innosetup+...@googlegroups.com.

To view this discussion visit https://groups.google.com/d/msgid/innosetup/e0f1941b-1cf6-4eb6-8fde-10834b3b634fn%40googlegroups.com.

[Bruno Lopes da Silva]

Thank you for your hard work again. Despite the little inconsistencies the overall result is clearly very good 👏. I already made a branch adapting the scripts for 6.6.0.