Extreme slow-down in Windows FMX app UI since upgrading to 12.1

[Cristian Peța 121]

Using arrRect.SetBounds() you avoid a call to AlignObjects because TControl.SetBounds is checking some things before a call to AlignObjects

Avoid setting TPosition.X

Edited yesterday at 01:32 PM by Cristian Peța

[domus 2]

1 minute ago, Cristian Peța said:

Avoid setting TPosition.X

No kidding!  

[Patrick PREMARTIN 141]

4 hours ago, Cristian Peța said:

Using arrRect.SetBounds() you avoid a call to AlignObjects because TControl.SetBounds is checking some things before a call to AlignObjects

Avoid setting TPosition.X

Thanks @Cristian Peța

I've updated my sample project on https://embt.atlassian.net/servicedesk/customer/portal/1/RSS-3711

Hope they found a way to optimize this for 13.

[Cristian Peța 121]

Just wanted to try a fix in FMX.Forms and I found it already there but commented 🤔.

First two lines will exit and AlignObjects() will not be called if used Form.BeginUpdate. The Realign will be done anyway after Form.EndUpdate.

procedure TCustomForm.Realign;
begin
//  if FDisableAlign or (FUpdating > 0) then
//    Exit;
... more code
  if FCanvas <> nil then
  begin
    AlignObjects(Self, Padding, FCanvas.Width, FCanvas.Height, FLastWidth, FLastHeight, FDisableAlign);
    RecalcControlsUpdateRect;
    InvalidateRect(ClientRect);
  end;
end;

 

[domus 2]

Now, that's odd. As if someone forgot to uncomment before release...

[Cristian Peța 121]

I updated the report https://embt.atlassian.net/servicedesk/customer/portal/1/RSS-3711