XYplorer Beta Club

When you invoke the dialog that displays your "Current List Columns" including widths via the new Column Layouts button, all the widths shown are different than what is returned via setcolumns or normal save column layout files, which seems bizarre, at first I thought this was because of the new /g switch, but now I think it's possible all the widths displayed are shown in graphics aware values, instead of just showing adjusted values for the necessary columns.

Below is the return values using FRESH, both are of the exact same columns, so it seems confusing having these be different, is it expected to be like this?

via new Column Layouts Button: via setcolumns(), columnlayout() or alternate GUI methods;

It's complicated.

I decided to have all metrics related to the Column Layouts button to be DPI-aware. I.e. they are stored (and for consistency also displayed, as you noted) with the pixels they would have in 100% screen resolution. Then when applied to the list those numbers are converted to the actual screen resolution. This is to ensure that your layouts work (and "work" means that there is enough space to show the column contents) the same in different screen resolutions. To further complicate things it proved to be necessary to additionally increase the numbers by a factor of 1.1 because fonts do not scale continuously but in discrete jumps.

So, for example, when the Name is nominally stored as "300" pixels wide and you apply this in 125% screen resolution, you get 300 * 1.25 * 1.1 = 413 pixels effective column width.

The scripting commands on the other hand return the true current state DPI-unawarely. So text setcolumns(,2); would give you the 413 pixels the Name column currently has.

* * *

I see that it is confusing, but I don't see a way to make it better. Or should Ctrl+Click on the Column Layouts button menu items return the true pixel values? Maybe yes, because it would make the returns usable for scripting and it would match what you actually see/measure on screen, so it would certainly be less confusing.

PS: The above would only work for clicks on "Update...". So that would probably lead to further confusion. Instead I will add Ctrl+Shift+Click as a way to show the true pixel values of the current columns. After all, this is a pretty much hidden nerd functionality anyway.