FMXInno - Windows Fluent Design Installer UI for Inno

[BLACKFIRE69]

Originally Posted by BLACKFIRE69

FMXInno: Cumulative Update - [2024-Mar-15]


What's New:

* Merged FMXInno Dev into this.
* Updated ISArcEx to the latest version.
* Made some improvements and bug fixes.
* This update addresses most of the previous issues.
* Added Radiant Shapes.
* Introduced new properties to classes.
* WinTitleBar will now display the application icon by default.
* Not compressed by default.
  - No Exe compressor or file reduction tricks were used.
* Implemented new functions.

FMXInno - Final Release [2024-Mar-20]


What's new:

* This update will extend from FMXInno Dev [2023-Mar-15].

- Make sure to refer to the last previous changelog to check out the new changes.

* Added a new Fluent Form (FluentBlendedColor).

- This is also a standard Fluent Form, but this new form will blend with the Windows colors (Accent or Desktop Image) along with standard Fluent colors.
- The reason for this new form is for Fluent forms to have a more realistic and modern look.
- Supports both Dark/Light modes and custom color mode.
- Also supports some possible customizations.
- Check out the screenshots to see the differences between standard Fluent forms at standard opacity level (Opacity = 0.56).

* Added built-in SVG image support.

- Rendering engine: Image32

* Windows title bar is now more customizable.

- Custom Application Icon instead of the default one.
- Titlebar Color.
- Button Colors.
- Titlebar Background Effects, and so on.

* SKIA and Blend2D are now optional.

- SKIA and Blend2D are optional from now on because they require external dependencies (sk4d.dll, blend2d_win32.dll).
- You can still have them, but you have to download them manually.

* Added Image32 - 2D Graphic Library.

- Image32 will take the place of SKIA and Blend2d from now on, especially because it does not require external dependencies and has average performance compared to SKIA and Direct2D.
- Image32 is not enabled by default for public use; for now, it's for my personal use only (because i'm pretty sure no one will use it directly in their projects. )
- More info about Image32: Image32 is a 2D graphics library

* Added new properties for classes.

* More bug fixes and improvements.

* Plugin folder has been cleaned up.

- Removed unwanted plugins from the directory.
- Re-compiled all the plugins to make sure everything is up to date.

* All the examples have been revised.

- Now the default compression will be 'lzma2/ultra64'.

* Also, added new examples.

* Extended support for Windows 11 24H2.

function FCreateFluentBlendedColor(WParent: HWND; DarkTheme, NoBorder: Boolean;
  Opacity: Single; BrightnessPct: Byte; BlendColorMode: TBlendColorMode): HWND;

function FCreateFluentBlendedColorEx(WParent: HWND; DarkTheme, NoBorder: Boolean;
  Opacity: Single; BrightnessPct: Byte; BlendColorMode: TBlendColorMode;
  BlendColorLvl: Integer): HWND;

function FCreateFluentBlendedColorEx2(WParent: HWND; VCLColor: TColor;
  DarkTheme, NoBorder: Boolean; Opacity: Single; BrightnessPct: Byte;
  BlendColorLvl: Integer): HWND;

Note: The first post has been updated; check it out.



.

[BLACKFIRE69]

FMXInno: Minor Update for [Mar-20]

* Added two methods to the UWP class that select a specific UWP tile.

* Now supports FluentBlendedColor option in other forms as well (CustomForm, Dir/Start Form).

* Added missing method 'SetApplicationIconFromFXStream' to the 'FWinTitleBar' class.

UWP Tile Selection:

procedure TileSelect(ATile: LongInt);
procedure TileSelectEx(ATile: LongInt; MouseOverColor: TAlphaColor);

Example:

UWPTiles.TileSelect(Tile[5]);
UWPTiles.TileSelectEx(Tile[5], ALRed);

How to update:

1. Download the latest update from the first post.
2. Replace the 'FMXInno.dll' and 'FMXInnoHandle.iss' with the provided ones.

.

[BLACKFIRE69]

FMXInno: Minor Update - [2024-Mar-27]

* Added the FColorComboBox class.
* Prevented forms from being resized.
* Added the following new functions:

function IsValidVCLColor(const AColor: TColor): Boolean;
function IsValidFMXColor(const AColor: TAlphaColor): Boolean;

function IsLightFMXColor(const AColor: TAlphaColor): Boolean;
function IsLightVCLColor(const AColor: TColor): Boolean;

IsLightFMXColor:

> in some cases, 'IsLightFMXColor' is useful for determining the font colors based on the background color or background image color. here's how it can be used:

procedure ClrBxOnChange(Sender: TObject);
var
  CtrlClr: TAlphaColor;
begin
  CtrlClr := AClrBx.GetColor;

  if IsLightFMXColor(CtrlClr) then
    AText.Color(ALBlack)
  else
    AText.Color(ALWhite);

  ARect.FillColor(CtrlClr);
end;

Extra:

function DesktopImgExist: Boolean;

function GetDesktopImgColorFMX: TAlphaColor;
function GetDesktopSolidColorFMX: TAlphaColor;

function GetImgColorFMX(const Image: UnicodeString): TAlphaColor;
function GetImgPartColorFMX(const Image: UnicodeString; 
  const PixelX, PixelY, PixelW, PixelH: Single): TAlphaColor;

How to update:

1. Download the latest update from the first post.
2. Replace the 'FMXInno.dll' and 'FMXInnoHandle.iss' with the provided ones.

.

[BLACKFIRE69]

FMXInno - Windows 8

even though i'm not a fan of Windows 8 like many others, i do like the background color transition during its installation. what are your thoughts?

.

[audiofeel]

Originally Posted by BLACKFIRE69

FMXInno - Windows 8
.

@BLACKFIRE69
In this regard, I would like to know. How to implement a full-screen installer? Something like this (I don't remember the exact command) is "WindowVisible". Well, that is, it starts in full screen, it can be closed by "Alt+F4" (By the way, in my opinion, it does not work on FMXInno now). How to implement this correctly and what type of form is better to apply, I would like to see your answer. Most likely, in the future there will be questions like "how to implement both the size of the interfaces and their coordinates with a change in resolution"?

[Jahan1373]

Originally Posted by Fak Eid

Hi audiofeel,

Well, please refer the files. To reproduce the issue:
1. The required files in the Output are obviously missing. So, start the installer normally and navigate to Installation tab. It will show you some error like: Required Files Missing.

2. Try to close it and quit the installer. It doesn't happen. Hard close using Task Manager.

3. Now, open the installer again and try to quit at any point of time. It doesn't close.

Let me know if you're able to refer this link:
https://www.mediafire.com/file/ohrzl...dated.zip/file

I know there can be some issue with my code. But, if you can help me, I'll learn from you

Link dwnlad

[BLACKFIRE69]

FMXInno - Final Release [2024-Apr-29]


* What's New:

* This update focuses on quality improvements, stability enhancements, and minimizing memory leaks.

-- Features like FMXInno Copilot, Widgets, and certain modern features have been postponed to avoid adding bloatware to FMXInno.
-- However, you can test them out on FMXInno-Dev, and I'll provide updates on their availability in the future.

* Introduced a new Error Handling Mechanism.

-- Previous versions of FMXInno lacked proper error handling because I prioritized adding new features and improvements over it.
-- With this update, I've enhanced the stability of FMXInno,
-- Ensuring that the new error handling significantly benefits you by preventing installer crashes and access violation errors.

* Compiled with the latest version of RadStudio (RadStudio Athens 12.1 - 04/Apr/2024).

-- This ensures that everything is up-to-date.
-- Providing high-quality performance and rendering.
-- High-DPI support.
-- Complete compatibility with Windows 11.
-- Increased Windows API availability.
-- And improved coding efficiency.

* Fixed HTMLText and added support for opacity.

-- Previously, HTMLText had issues with opacity, which have now been resolved.

* Fixed WebView2 to ensure proper setup closure.

-- Updated WebView2 to the latest version and made necessary improvements.

Example: 

procedure DeinitializeSetup();
begin
  AWebView.Stop;
  AWebView.Shutdown;
  FMXInnoShutDown;
end;

* Improved SKIA for high performance.

-- SKIA relies on the GPU and minimally affects the CPU, making it suitable for use in your installer.

* Although SKIA and Blend2D are kept separate from the standard FMXInno for now, both versions are provided in the attachment.

-- In the future, they will need to be downloaded separately.

* The Image32 Engine remains unavailable for public use.

-- As many FMXInno users may not be familiar with it.

* Various improvements and bug fixes.

-- No software is without issues, so we continue to address them with each update.

* Updated the '_InstallerGenerator' app.

-- Now includes a built-in Inno Script Editor + Compiler.

* Ready to use with the upcoming InnoSetup v6.3.0.

* Added a new example for setup language selection.

Note: The first post has been updated; check it out.



.

[Tihiy_Don]

Good afternoon! Some users, on any systems, have a problem when the installer process hangs in the processes and the form does not open. It occurs extremely rarely, in about 5-10 percent of users. I hope this issue has been fixed in this version. I tried to change different types of forms, the result is the same.

[BLACKFIRE69]

Originally Posted by Tihiy_Don

Good afternoon! Some users, on any systems, have a problem when the installer process hangs in the processes and the form does not open. It occurs extremely rarely, in about 5-10 percent of users. I hope this issue has been fixed in this version. I tried to change different types of forms, the result is the same.

users sometimes report this issue, but until now, i couldn't come up with a better solution.

let's dive a little deeper into this. in FMXInno, all the forms (FluentForm, BlankForm, ImageForm, etc.) are based on a single form called 'TFMXFluentF', which is a modified Firemonkey TForm specifically used for FMXInno. i think this could be the main reason for all of this. So, that's how i came up with this new idea.

i've introduced a new form called 'ClassicForm' into FMXInno. so, what is the 'ClassicForm'? Is it another blank form or something else? actually not, it's an original Firemonkey TForm which is exactly the same as the one Mr. Jiva Newstone used in 'ISFMXFW'.

First of all, let's check out the key differences between FMXInno's TFMXFluentF and ISFMXFW's TForm:

- FMXInno's TFMXFluentF:
  1. This replaces the WizardForm when creating.
  2. It has more control over this.
  3. It can have Fluent effects on this.

- ISFMXFW's TForm:
  1. This is parented to the WizardForm, nothing is replaced.
  2. It has limited controls.
  3. Fluent effects cannot be used on this.

so, how is the 'Classic' form gonna fix this issue? my idea is to have two modes for the same installer as a backup using 'Classic' forms. to do so, we can use command-line parameters in case the setup is unable to run with the 'TFMXFluentF'. we can easily do that using a batch file, and the following simple example will show you how to do that.

var
  IsClassicMode: Boolean;

function InitializeSetup(): Boolean;
begin
  IsClassicMode := CmdLineParamExist('/Classic');

  FMXInnoInit;
  Result := True;
end;

procedure InitializeWizard();
begin
  EmptyWizardForm(True, 640, 480);

  // Music ...

  FMXDesigning;
  FMXForm.Show;

  if IsClassicMode then
    pTaskbarPreview(True) // or pTaskbarPreviewEx(WizardForm.Handle, True);
  else
    pTaskbarPreviewEx(FMXForm.HandleHWND, True);
end;

procedure FMXDesigning;
begin
  { FMX Form }
  if IsClassicMode then
    FMXForm.FCreateClassicForm(WizardForm.Handle, ALMoneyGreen, '')
  else
    FMXForm.FCreateFluent(WizardForm.Handle, False, False, 0.56, 0);

  FMXForm.SetCursor(ExtractAndLoad('Dark.cur'));
  ...
end;

Bat File:

@echo off
cd /d "%~dp0"

start "" "_Setup1.exe" /Classic

in this way, you can try the classic mode if the installer is unable to run with modern forms. (because of the classic form, FMXInno may support old OS like Windows 7. i'm not sure because i don't have any virtual machine or bare metal right now to test it out.)

there're some facts you should notice when using the classic forms:

1. EmptyWizardForm - the 'Buttons' parameter should always be 'True'.
   eg: EmptyWizardForm(True, 640, 480);

2. pTaskbarPreviewEx - the 'hwnd' parameter should always be 'WizardForm.Handle'.
   eg: pTaskbarPreviewEx(WizardForm.Handle, True);

in the attachment, i've included two examples: a simple example and the Modern FitGirl Installer example with both Normal and Classic modes. run the batch files to see the differences. the following screenshot will show you the Modern FitGirl installer in both normal and classic mode. (remember, classic forms are always borderless rectangle forms, and we cannot control the border style.)

also, the first post has been updated with the new update.


.

[Tihiy_Don]

Thank you - this is exactly what I need, I will try to implement the installer on it and test it on users. Unfortunately, I also could not identify any consistency with this problem, it sometimes occurs on windows 11, 10 and 7. Someone solved this problem by rebooting the operating system, but others did not. I also sent you a message on krinkels related to unpacking the archives, please read it as you have free time.

[Fak Eid]

Hi @Blackfire69,

Can you please help me with following additions/workaround to FMX Libraries as I require them on a Project I'm working in:

1. Can we fetch the drive's name (Picture 1)?

2. Functionality to have sharp corners on FCustomFluentWindow?
Edit: Audiofeel helped with this. Thank you

InstallPage.FCreateBlankForm(FMXForm.HandleHWND, HTMLColorStrToFMXColor('#25282f'), '');

InstallPage.Show;
SetWin11FormCorners(InstallPage.ParentHandleHWND, ctw11Sharp);

3. Functionality to have FImgSlideShow or FFormImgSlide inside FRectangle (not HWND)

4. A variable on ProgressCallback to fetch the total disk size extracted in case of multiple disks. I tried doing (Installation % * Size) div 100 but it is just workaround. (Picture 2 & 3 for reference)

5. In some cases, the CpuUsage.Name gives value seperated by Tabs. Any way to remove that? Like:
Processor: { Tab Space } AMD Ryzen 9

6. How to right align a FLabel/FText? It is not working or an example please.
Edit: Audiofeel helped with this. Thank you

ALabel.FCreate(PageContent[3].Handle, '57.2 GB');
ALabel.SetBounds(500, 165, 70, 20);
ALabel.FontSetting('{#FontName}', 11, {#SelectedFontColor});
ALabel.FontStyle([fsBold]);
ALabel.TextSetting(False, txTrailing, txCenter);

7. FCombineText: if have 0 Tab space must get the width of Text 1 and Text 2 should start after some space

With the new FMXInno, so many error messages keep popping up. Can you please have a toggle to turn them off or bypass?

[BLACKFIRE69]

FMXInno Cumulative Update - [2024 May 11]

* Improvements in the code.
* Cleaned up the code a bit and removed duplications.
* More stable.

* This build could be more efficient than the previous one.
  - Ensured compatibility with Windows 11 24H2.

* Added a new class to deal with INI files.
  - Now you can handle even complex INI files more easily.
  - Check the example in the attachment.

* Added a new class for All-in-One array.
  - Now you can have multiple data types in one array.
  - Supports 11+ data types by default.
  - More data types will be added upon request.
  - Easy to manipulate.
  - Check the example in the attachment.

* Updated FLogicalDrives class.
  - Added a new property called 'Disk Name'.
  - Check out the 'Example_LogicalDrives.iss'.

* Updated FXStream.
  - FXPckr can hold InnoSetup's encrypted password.
  - Updated encryption.
  - Fixed minor bugs related to FCreateFXStream.
  - This version doesn't support previous versions.

* Updated FCheckboxTree class.
  - Now, the OnChange events of checkboxes are handled automatically by the FMXInno internally.
  - To override it and have manual OnChange events, you have to call 'OverrideDefaultOnChangeEvent'.
    eg: Pg4ChkbxTree.OverrideDefaultOnChangeEvent;

* Updated WebView2 class.

* Updated license agreement.

================================================== =================

>> FMXInno hangs on Taskbar <<

Now we've evidence that the main cause of this issue is the custom font. Generally, I use the following three functions to install custom fonts into the installer:

1. InstallFMXFont
2. DeleteFMXFont
3. InvalidateFMXFont

Instead of using these three functions, try the following functions for custom fonts for now:

1. AddFontResource2
2. RemoveFontResource2

I've updated the examples, so you can check them out to see how to use these functions.

Thanks to @Tihiy_Don for conducting some tests on this.



The first post has been updated.



.

[ScOOt3r]

Thanks @Blackfire69 this fixes my issue of the same thing to.. works Great!

ScOOt3r

[audiofeel]

Originally Posted by Fak Eid

Hi @Blackfire69,
3. Functionality to have FImgSlideShow or FFormImgSlide inside FRectangle (not HWND)

there's nothing to display on top of it anyway

Originally Posted by Fak Eid

Hi @Blackfire69,
6. How to right align a FLabel/FText? It is not working or an example please.

in this example, the length of the text is 210 and it will always be pressed to the end, that is, from the right

  WaterMark.FCreate(WizardLayer.Handle);
  WaterMark.Text(FMXInnoBuildDate);
  WaterMark.SetBounds(730, 468, 210, 20);
  WaterMark.FontSetting('{#FontName}', 12, FMXColorSetOpacity({#FontColor2}, 0.1));
  WaterMark.FontStyle([fsBold]);
  WaterMark.TextSetting(False, txTrailing, txLeading);

Originally Posted by Fak Eid

Hi @Blackfire69,
With the new FMXInno, so many error messages keep popping up. Can you please have a toggle to turn them off or bypass?

I think it's better for us to catch errors than for users not to ?

[BLACKFIRE69]

Originally Posted by Fak Eid

With the new FMXInno, so many error messages keep popping up. Can you please have a toggle to turn them off or bypass?

Originally Posted by audiofeel

I think it's better for us to catch errors than for users not to ?

• The new error handler is a little bit tougher because effective error management is key to reducing runtime errors, especially. This approach forces you to explicitly handle errors and null values, making your code clearer and safer.
  
  
• The new error handler provides more informative error messages tailored to specific situations, making it very convenient to deal with.
  
  
• Why didn't previous versions display these error messages? Because they lacked an error handler altogether, thus allowing any errors to go unnoticed and potentially causing issues.

The error handler will remain active; I won't permit bypassing it.



.