It also allows you to change fontsNo effect when I change the font. I see in your code that you change the font of the form, but all controls on the form have ParentFont set to false. What do you want to achieve with that? Why don't you change the font of the grid directly?
[...] as well as increasing the widths of the columns up to 125% of the original.It looks as if the changes are much smaller than specified. In your code you calculate the width of the longest colum cell and apply the percent increase to it. But the grid does more: it adds the value of "varCellPadding" before and after the text as margin, and it adds one GridLineWidth; in a default system (at 96ppI) these are 2*3+1 = 7 pixels. Due to this offset I do not change the overall column width with the requested percentage. Let's put this offset into accout with the example of the Digits column. After AutoSize its width is 91. Subtracting the offset by varCellPadding and GridLineWidth, I get 84 pixels text width. Applying a percentag of - say - 20% adds 16 pixels to 100 -- and this is exactly what your label is displaying. So, what is the problem?
It turns out that the AutoColumnSizing already increases the calculated amount by a few percent.Yes, it increases the pure text width by the varCellPadding and GridLineWidth offset, but this is a constant offset, not a constant percentage!
No effect when I change the font. I see in your code that you change the font of the form, but all controls on the form have ParentFont set to false. What do you want to achieve with that? Why don't you change the font of the grid directly?
It looks as if the changes are much smaller than specified. ... So, what is the problem?
Decades ago in the MS-DOS days, I was an avid user of UCSD Pascal and later of Modula-2.
Going back to my standard Win10 development system which runs at 96ppi and looking at the same code position I see that this already has been fixed in Laz trunk.