FMXInno - Windows Fluent Design Installer UI for Inno

[BLACKFIRE69]

Just forget about the previous builds (May 19, etc.) because they had some issues. 'FMXForm.Show' didn't work properly, 'Translucent' objects didn't function, and 'BeginHaltProc' was broken, etc.

This update addresses those issues.




FMXInno - Final Release [2024-May-21]

* Integrated all the updates so far.
* Made some improvements and fixed bugs.
* Added new properties to classes.
* Updated Fluent API.

* Improved 'SetActiveThemeModeAwareness':
  -- It now supports all the forms except 'NormalForm' and 'ClassicForm'.

  > Fluent: ChangeFluentTheme (Dark/Light)
  > FluentColor: ChangeFluentColor
  > FluentBlendedColor: ChangeBlendedColor
  > BlankForm: ChangeBlankFormColor

* Optimized for higher DPI.
* Ensured FMXForm and MsgForms are shown in the desktop center.

* The package now includes InnoSetup v6.0.5 + ResTools IDE instead of InnoSetup v5.6.1:
  -- Make sure to use 'EmptyWizardForm' to resize the setup, especially for InnoSetup 6+.

* All basic tests were done with InnoSetup v6.3.0 Dev:
  -- To ensure FMXInno works with the latest updates of InnoSetup.

* Compiled in RadStudio 12.1 + Patch 01.

Originally Posted by Fak Eid

PS: Please also add GetSelectedDiskName (to get the name of the selected drive) on FDiskList.

A new property, 'GetSelectedDiskName', is available under 'FDiskList'.


The first post has been updated.


.

[Tihiy_Don]

Please add the Cursor method for the FColorButton component.

[Fak Eid]

Originally Posted by Fak Eid

A false screen pops-up for a few second and disappears every time the Setup.exe file is run. This was not happening in the 14th May or older version.

This issue is still happening in FMXInno [21-May] for all types of forms, at all resolutions and in both Inno Setup version, that is, 6.3.0 and 5.6.0

[Tihiy_Don]

I also have this problem, a white square appears briefly on blankform. There is no such problem with imageform.

[BLACKFIRE69]

Originally Posted by Fak Eid

This issue is still happening in FMXInno [21-May] for all types of forms, at all resolutions and in both Inno Setup version, that is, 6.3.0 and 5.6.0

Windows gets new updates regularly, and i've upgraded to the newest version of RadStudio, so anything could be affect this. this is the best optimization that i can do on my part. if it doesn't work, then i can't do anything about it.

check the attachment.

Originally Posted by Tihiy_Don

Please add the Cursor method for the FColorButton component.

Added the 'cursor' property for custom blueprints.



InnoSetup 6.3.0 Dev:

* Compiled with the latest source code (2024-May-26).

* Added missing help files.

* Corrected custom syntax highlighting.
  -- In the previous build, i might have done something wrong. this build will fix it.

[Fak Eid]

I still need help with this
Earlier to read AppName from .ini file we used to:

#define AppName ReadIni(SourcePath + "Game\Installer.ini", "Installer", "Name", "")

[Setup]
AppName={#AppName}

Is it possible to do it using the new FNewINI command like:

[Setup]
AppName=ANewInI.ReadString('Installer', 'Name', '')

[BLACKFIRE69]

Originally Posted by Fak Eid

I still need help with this
Earlier to read AppName from .ini file we used to:

#define AppName ReadIni(SourcePath + "Game\Installer.ini", "Installer", "Name", "")

[Setup]
AppName={#AppName}

Is it possible to do it using the new FNewINI command like:

[Setup]
AppName=ANewInI.ReadString('Installer', 'Name', '')

this tool is the CLI version of 'FNewINI' and can be used for preprocessing and automating everything at compile-time.

in the attachment, you'll find a simple example of how to read and configure the setup with the following INI file.



.

[Fak Eid]

Hi @Blackfire,

It is good that we now have a preprocessor for Read INI, but personally I think that we only need that to pass {#AppName} and {#DirName} at the compile time during the setup creation process. Rest everything can be handled without preprocessor. The FNewINI is written well enough. Please consider an example I shared above for Icons creation. It is easy to read, has a common procedure for all AppExe, less code, has ability to add more parameters in future and doesn't use preprocessor. You can definitely enhance and add to FMXInno (if you feel)

If I have to use the preprocessor only, I'd rather use the older reliable method. But, thank you so much for the enhancements.

I'd be posting more on Redist installation handling and Data extraction handling. I'm coding and testing on them.

[audiofeel]

Originally Posted by Fak Eid

Hi @Blackfire,

It is good that we now have a preprocessor for Read INI, but personally I think that we only need that to pass {#AppName} and {#DirName} at the compile time during the setup creation process. Rest everything can be handled without preprocessor. The FNewINI is written well enough. Please consider an example I shared above for Icons creation. It is easy to read, has a common procedure for all AppExe, less code, has ability to add more parameters in future and doesn't use preprocessor. You can definitely enhance and add to FMXInno (if you feel)

If I have to use the preprocessor only, I'd rather use the older reliable method. But, thank you so much for the enhancements.

I'd be posting more on Redist installation handling and Data extraction handling. I'm coding and testing on them.

the proposed version of @blackfire69 is good because an ordinary user no longer needs to manually create a checkbox and set the text and its coordinates to it, just make changes to the ini file and the checkbox will appear and the necessary archive will be searched for unpacking.

[Fak Eid]

Originally Posted by audiofeel

the proposed version of @blackfire69 is good because an ordinary user no longer needs to manually create a checkbox and set the text and its coordinates to it, just make changes to the ini file and the checkbox will appear and the necessary archive will be searched for unpacking.

I've an almost complete version of code where the user doesn't need to write any code at all for creating selective components. It's in my 'Random_Gamertags' Repack.

I've almost completed changes and currently testing this with new FNewINI

[audiofeel]

Originally Posted by Fak Eid

I've an almost complete version of code where the user doesn't need to write any code at all for selective components. It's in my 'Random_Gamertags' Repack.

I've almost completed changes and currently testing this with new FNewINI

Well, it will be very useful

[Fak Eid]

Hi @Blackfire,

Not sure if you remember I asked how can I have just 1 character space instead of Tab Space for FCombineText, and you mentioned it can be done using 0 or -1, -2, etc. The problem is, it is not working for Smaller Font Size like 12-15. The two texts are not on same height and the gap is unusual. On Larger Font Size, like 16, it is working as expected. Can you help?

SectionText[1].FCreate(SectionContent[1].Handle, 500, 15, 'Developers :', INI_DEVELOPERS, -1, False);
SectionText[1].Text1Setting('{#FontName}', 12, {#FontColor}, False);
SectionText[1].Text2Setting('{#FontName}', 12, {#SelectedFontColor}, False);

SectionText[2].FCreate(SectionContent[1].Handle, 500, 35, 'Genre :', INI_GENRE, -1, False);
SectionText[2].Text1Setting('{#FontName}', 12, {#FontColor}, False);
SectionText[2].Text2Setting('{#FontName}', 12, {#SelectedFontColor}, False);

[hitman797]

Originally Posted by Fak Eid

Hi @Blackfire,

Not sure if you remember I asked how can I have just 1 character space instead of Tab Space for FCombineText, and you mentioned it can be done using 0 or -1, -2, etc. The problem is, it is not working for Smaller Font Size like 12-15. The two texts are not on same height and the gap is unusual. On Larger Font Size, like 16, it is working as expected. Can you help?

SectionText[1].FCreate(SectionContent[1].Handle, 500, 15, 'Developers :', INI_DEVELOPERS, -1, False);
SectionText[1].Text1Setting('{#FontName}', 12, {#FontColor}, False);
SectionText[1].Text2Setting('{#FontName}', 12, {#SelectedFontColor}, False);

SectionText[2].FCreate(SectionContent[1].Handle, 500, 35, 'Genre :', INI_GENRE, -1, False);
SectionText[2].Text1Setting('{#FontName}', 12, {#FontColor}, False);
SectionText[2].Text2Setting('{#FontName}', 12, {#SelectedFontColor}, False);

    TTextAlign = (txCenter, txLeading, txTrailing); 
    procedure Text1HorzAlign(HAlign: TTextAlign);
    procedure Text2HorzAlign(HAlign: TTextAlign);

[Fak Eid]

Originally Posted by hitman797

    TTextAlign = (txCenter, txLeading, txTrailing); 
    procedure Text1HorzAlign(HAlign: TTextAlign);
    procedure Text2HorzAlign(HAlign: TTextAlign);

Hi @hitman @Blackfire

Thank you. I tried and have to manually align the text for this. However, in Smaller Font Size (like 12-15), the two text still doesn't seem to be aligned height-wise. Any fix for it?

  SectionText[1].FCreate(SectionContent[1].Handle, 500, 15, 'Developers :', INI_DEVELOPERS, -1, False);
  SectionText[1].Text1Setting('{#FontName}', 12, {#FontColor}, False);
  SectionText[1].Text2Setting('{#FontName}', 12, {#SelectedFontColor}, False);
  SectionText[1].Text1HorzAlign(txTrailing);
  SectionText[1].Text2HorzAlign(txTrailing);

  SectionText[2].FCreate(SectionContent[1].Handle, 505, 35, 'Genre :', INI_GENRE, -1, False);
  SectionText[2].Text1Setting('{#FontName}', 12, {#FontColor}, False);
  SectionText[2].Text2Setting('{#FontName}', 12, {#SelectedFontColor}, False);
  SectionText[2].Text1HorzAlign(txTrailing);
  SectionText[2].Text2HorzAlign(txTrailing);

  SectionText[3].FCreate(SectionContent[1].Handle, 500, 55, 'Release Date :', INI_RELEASE_DATE, -1, False);
  SectionText[3].Text1Setting('{#FontName}', 12, {#FontColor}, False);
  SectionText[3].Text2Setting('{#FontName}', 12, {#SelectedFontColor}, False);
  SectionText[3].Text1HorzAlign(txTrailing);
  SectionText[3].Text2HorzAlign(txTrailing);

Another issue: InstallFMXFont sometimes hangs the launch of Setup.exe during Runtime.

[Tihiy_Don]

Originally Posted by Fak Eid

Another issue: InstallFMXFont sometimes hangs the launch of Setup.exe during Runtime.

HI. Use new method:

function InitializeSetup: Boolean;
begin
  AddFontResource2(ExtractAndLoad('{#MyFont1}'));
  FMXInnoInit;
  Result:= True;
end;

procedure DeinitializeSetup();
begin
  RemoveFontResource2(ExpandConstant('{tmp}\{#MyFont1}'));
  ISArcExCleanUp;
  FMXInnoShutDown;
end;

Now you do not need to specify InstallFMXFont in the FMXDesigning procedure