This is a follow-up for T7227: Kleopatra: Ensure columns are wide enough when they are made visible. The column sizes should be limited to a reasonable value when resizing them to their content. The user should still be able to make the columns wider.
This should likely be backported for VSD 3.3 since it complements other changes with column size handling.
| rLIBKLEO Libkleo | |||
| rLIBKLEOd771de8a8405 Limit width of columns when resized to contents | |||
| rLIBKLEO1a924df0225e Limit width of columns when resized to contents | |||
| rLIBKLEOdbc3651bb1f8 Limit width of columns when resized to contents | |||
| rKLEOPATRA Kleopatra | |||
| rKLEOPATRA221df1479dc4 Limit width of columns when resized to contents | |||
| rKLEOPATRA8dd75523fcb0 Limit width of columns when resized to contents | |||
| rKLEOPATRA4e570632e9c9 Limit width of columns when resized to contents | |||
| rKLEOPATRA29723e92360f Limit width of columns when resized to contents | |||
tested with gpg4win-Beta50:
Works for adding the tag column with a very long tag which is then restricted to width 400.
But the name column is restricted to 260. I guess because "name" is a visible-by-default column you handle it differently on purpose?
Yes, for historical reasons (i.e. we haven't changed this) the width of the name and email columns always defaults to 260.
I assume we do not want to unify this (yet)? But if we want to, we should make another ticket for this anyway.