FMXInno - Windows Fluent Design Installer UI for Inno

[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

[audiofeel]

Originally Posted by hitman797

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

in my opinion, we lack this..

    procedure Text1VertAlign(VAlign: TTextAlign);
    procedure Text2VertAlign(VAlign: TTextAlign);

[Fak Eid]

Originally Posted by Tihiy_Don

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

I knew about AddFontResource2. I thought 'InstallFMXFont' was the newest thing. Sorry, I can't keep track of updates.

Originally Posted by audiofeel

in my opinion, we lack this..

    procedure Text1VertAlign(VAlign: TTextAlign);
    procedure Text2VertAlign(VAlign: TTextAlign);

Yes, i believe or whatever fixes this issue on smaller fonts. One of my FMX Installer is completely dependent on the use of it and I've to wait longer just to get this fixed. Although, it is working for larger font size like 16+.

[BLACKFIRE69]

FMXInno - Final Release [2024-June-10]


What's new:

* Merged Runtime-Scripts into this build.

* 'FNewINI' updated.

- Now you can create a 'FNewINI' from a string.

  InIStr := '[SecM]'      +#13#10+
            'Key1=Val01'  +#13#10+
            'Key2=Val02'  +#13#10+
            ''            +#13#10+
            '[SecM\SecA]' +#13#10+
            'KeyA=ValA'   +#13#10+
            'KeyB=ValB';

  ANewINI.FcreateFromString(InIStr);

* Minor bug fixes and improvements.
* And it's recommended to use the latest version of InnoSetup v6.3.0.


The first post has been updated.


If you expect the following features, let me know:

1. PDF Viewer (*.pdf).
2. Markdown Viewer (*.md).
3. HTML Viewer (*.html).

---------------------------------------------------------------------------------------------------------------------

@Fak Eid,

* FCombineText/vertical mismatch:

- You have to use the Offset Y value to fix the vertical mismatch. (FCombineText.OffsetYText2(DY))
- Also, I removed the properties 'Text1HorzAlign' and 'Text2HorzAlign' from 'FCombineText'.

Example:

const
  c_max0 = 14;
  Pttrn  = 4; // 1, 2, 3 or 4.

procedure FMXDesigning;
var i, j, k, c_max: Integer;
begin
  ...
  if (c_max0 mod 2) = 0 then c_max := c_max0 else c_max := c_max0 - 1;

  { ACombineText }
  for i := 1 to c_max do begin
    if i <= (c_max div 2) then begin
      case Pttrn of
        1: j:=-1*(i-1);
        2: j:=-1*((c_max div 2)-i);
        3: j:=-1*Round(Abs((((c_max div 2) div 2)+1)-i));
        4: if i<=(((c_max div 2) div 2)+1) then j:=-1*(i-1) else j:=-1*((c_max div 2)-i);
        else j:=-1*(i-1);
      end;
      k:=0;
    end else begin
      case Pttrn of
        1: j:=(i-((c_max div 2)+1));
        2: j:=(c_max-i);
        3: j:=Round(Abs(((c_max+(c_max div 2)+1) div 2)-i));
        4: if i<=((c_max+(c_max div 2)+1) div 2) then j:=(i-((c_max div 2)+1)) else j:=(c_max-i);
        else j:=(i-((c_max div 2)+1));
      end;
      k:=20;
    end;
    ACombineText[i].FCreate(FMXForm.Handle,60,120+((i-1)*15)+k,'The Module Name:','FMXInno.dll',j,False);
    ACombineText[i].Text1Setting('Segoe UI', 10, ALBlack, False);
    ACombineText[i].Text2Setting('Segoe UI', 13, ALRed, False);
    ACombineText[i].Text1ShadowSetting(ALBlack, 0.2, 0.2);
    ACombineText[i].Text2ShadowSetting(ALRed, 0.1, 0.6);
    ACombineText[i].OffsetYText2(-1.5);
  end;
  ...
end;

---------------------------------------------------------------------------------------------------------------------

@audiofeel,

* 'DrawFrame' has been updated for FFluentStartBrowse and FFluentDirBrowse.

* Setup-exiting issue for 'FOSInfo' with Windows 11 24H2 insider builds.

- In insider builds, Microsoft is pushing hard and has disabled (not deprecated) some useful features by default. This may be the reason for that.
- Once 24H2 is released, I'll update everything to be compatible with the new release.
- I don't release any fixes for beta versions, but for now, I made some modifications in this build which, if detected, may make 'FOSInfo' work with 24H2.

(I deleted the virtual machine with Win11 24H2 installed, so I couldn't test it.)

* MInI updated.

- Previous code examples may not work with the new MInI.exe.
- Now it will accept parameters in any of the following formats:

    1. /Sec=Player    || --Sec=Player      || /s=Player    || -s=Player
    2. /Sec="Player"  || --Sec="Player"    || /s="Player"  || -s="Player"
    3. /Sec='Player'  || --Sec='Player'    || /s='Player'  || -s='Player'

    4. /Sec:Player    || --Sec:Player      || /s:Player    || -s:Player
    5. /Sec:"Player"  || --Sec:"Player"    || /s:"Player"  || -s:"Player"
    6. /Sec:'Player'  || --Sec:'Player'    || /s:'Player'  || -s:'Player'

    7. /Sec Player    || --Sec Player      || /s Player    || -s Player
    8. /Sec "Player"  || --Sec "Player"    || /s "Player"  || -s "Player"
    9. /Sec 'Player'  || --Sec 'Player'    || /s 'Player'  || -s 'Player'

- Added a new function called 'CalcTotalDiskSizeByte' which calculates the total size of disks in bytes.

For that, the INI file should look like this:

[Datas]

[Datas\Data1]
File={src}\data1.bf
Size=1245

[Datas\Data2]
File={src}\data2.bf
Size=2356

[Datas\Data3]
File={src}\data3.bf
Size=4578

USAGE:   MInI.exe CalcTotalDiskSizeByte /MainSec=Datas /Key=Size

[Setup]
...
ExtraDiskSpaceRequired={#ReadMInI('CalcTotalDiskSizeByte', '/MainSec=Datas /Key=Size')}
...

- Updated Example.iss file to retrieve disk sizes and component-disk sizes at compile time.

Now everything is automated, so there's nothing to do manually.




.