Steema Central

Delphi version: Seattle
TTeeGrid version: VCL & FMX Registered version-1.05
Multidevice Application (FMX)
Platform: WIN32

I have attached your demo (Unit_Custom_Sorting.pas/fmx) with an added column of type integer so that you can reproduce the behavior.

The following happens, if you click on any of the three columns everything works as expected.

The unexpected behavior occurs when in the new column "id" the focus is placed in some cell of that column and click on the header of the column "id", to change the order.

At that time the width of all columns grows to a size that does not fit in the grid and the grid becomes unmanageable.

This behavior I have only observed in columns that contain numbers. that's why I added the id column as integer.

PD:
I also attached an example in TEE_GRID.zip and Lib_GridEx, with TVirtualFDDatasetData a descendant of TVirtualDBData, to facilitate the ordering of a TFDDataSet (The demo.xml file is not included, if you wish, request it and send it to you in separate mail.)

Good afternoon Yeray,

I have been able to observe that in certain occasions in the call to Tee.GridData.DB.TVirtualDBData.AutoWidth (), it resulted: = APainter.TextWidth ('0') * tmpL; returns unexpectedly high values (eg 199990,15625) and therefore the grid is not able to display the columns correctly.

This happens, when doing tests, I change TeeGrid.Data to assign another datasource, and coincidentally the focus is in a numeric cell.
It also occurs when the sort is enabled and the column button is pressed and the focus is in a numeric cell.

The first time TeeGrid.Data is assigned, the data is displayed correctly.

I suspect that the problem may have to do with the alignment on the right.

Saludos

I attached images of the appearance before and after the problem.

Hello,

REH Outsourcing wrote:I have attached your demo (Unit_Custom_Sorting.pas/fmx) with an added column of type integer so that you can reproduce the behavior.

The following happens, if you click on any of the three columns everything works as expected.

The unexpected behavior occurs when in the new column "id" the focus is placed in some cell of that column and click on the header of the column "id", to change the order.

At that time the width of all columns grows to a size that does not fit in the grid and the grid becomes unmanageable.

This behavior I have only observed in columns that contain numbers. that's why I added the id column as integer.

I can reproduce this problem with Seattle, but not with Berlin/Tokyo:

Good morning Yeray,

I confirm that the problem is specific to FMX:WIN32 Seattle, when compiling the demonstration project in Tokyo it works correctly.
It is evident that in Seattle there must be some kind of problem, which causes the width of columns to change.

I attach the simplified test project plus the data.

Additionally I observe the following:
.- When TTeeGrid.Editing.AlwaysVisible, the editor is shown but it is not editable, when it is false, it can be edited without problems. (FMX:WIN32: Seattle & Tokyo)
.- TTeeGrid.Editing.Editing.EnterKey = NextCell, is not taken into account, after pressing Enter, the newly edited cell loses focus, but the focus does not go to the next cell, or to any other (FMX:WIN32 Seattle & Tokyo)

Hello,

REH Outsourcing wrote:I confirm that the problem is specific to FMX:WIN32 Seattle, when compiling the demonstration project in Tokyo it works correctly.
It is evident that in Seattle there must be some kind of problem, which causes the width of columns to change.

The only workaround I can think on right now is to set the "id" column to be aligned to the Left, in Seattle:

Thanks Yeray, at the moment that workaround serves me.

You can see an alternative solution, in this post, "Problem with the order when you have to scroll with a column"

olá sou novo por aqui, gostaria de saber se a um meio de ordenar as colunas sem precisar de código.

Hello,

olá sou novo por aqui, gostaria de saber se a um meio de ordenar as colunas sem precisar de código.

There's no editor option to sort columns for the moment so I'm afraid the only way to achieve it with code.