6.6.0 to 6.6.1 problem

[JustDj]

Hi there. 

I am trying to understand why the same code behaves so differently between versions 6.6.0 and 6.6.1. In version 6.6.0, there are no issues and everything works as expected. However, in version 6.6.1, this page appears on top of the initial one, and I have not been able to resolve this behaviour.

Could you please advise what change introduced in version 6.6.1 might have caused this effect?

[Martijn Laan]

Hi,

I’m not sure what you mean by “this page appears on top of the initial one”. Also, the snippet as posted doesn’t compile for me.

One thing that does stands out: you're setting WizardForm as the parent of LicenseREV, which is almost certainly wrong. It should be parented to LicensePage.Surface instead (i.e. the surface of the page you want it to appear on). See the CodeClasses.iss example script.

Best wishes & greetings,
Martijn

Op 2-1-2026 om 04:03 schreef JustDj:

Hi there. 

I am trying to understand why the same code behaves so differently between versions 6.6.0 and 6.6.1. In version 6.6.0, there are no issues and everything works as expected. However, in version 6.6.1, this page appears on top of the initial one, and I have not been able to resolve this behaviour.

Could you please advise what change introduced in version 6.6.1 might have caused this effect?

--
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/39e6a565-e987-40a0-8be6-7e47b918cb1bn%40googlegroups.com.

[JustDj]

My project does not rely on standard Inno Setup mechanisms, so using Surface is not an option for me. Supporting it would require a complete rewrite of the core logic from scratch. This installer is likely one of the largest and most complex ever built on Inno Setup, which makes it impractical to isolate a small reproducible example to demonstrate the issue.

What I have clearly observed is a behavioural change between versions 6.6.0 and 6.6.1. In 6.6.0 everything works exactly as expected, while in 6.6.1 the behaviour has changed for TRichEditViewer. This issue does not occur with TNewMemo, which continues to behave correctly.

In version 6.6.0, TRichEditViewer is rendered properly on the intended page. However, starting with 6.6.1, it unexpectedly appears on the first custom page, and I have not found any way to prevent or override this behaviour.

Could you please clarify what changed between these versions, particularly in terms of how TRichEditViewer differs internally from TNewMemo, and what might explain this new rendering behaviour?

пятница, 2 января 2026 г. в 03:30:13 UTC-5, Martijn Laan:

[Martijn Laan]

Hi,

Thanks for the explanation but sorry, I don't understand what you're trying to say. Setting WizardForm as Parent is wrong if you expect the control to reliably appear on a custom page, because doing so makes it a sibling of the page, instead of a child.

Making WizardForm the parent but the custom page the owner, as you're doing, is also strange. I don't know what effect that has.

Greetings,

Martijn

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

To view this discussion visit https://groups.google.com/d/msgid/innosetup/afa6f947-b118-448c-8dae-64c6dc05d603n%40googlegroups.com.