Sorting order of fields: 1,..,9,10,11,12 and not 1,10,11,12,2,3,4,5...
A lightweight and easy-to-use password manager
Brought to you by:
dreichl
Menu
▾
▴
I have created an entry with 12 custom fields numbered from 1-12. But KeePass applies the followng sorting order: 1,10,11,12,2,3,4,5.... But the correct sorting order should be 1,2,..,9,10,11,12 (see screenshot).
Could this be changed? Thanks!
Last edit: Anonymous 2020-09-24
Why don't you make your numbers 01, 02 and so on ?
Because that would be a workaround, not a bugfix. All the file managers nowadays, for example Windows Explorer and macOS Finder, use the logical sort order 1,2,..,9,10,11,12. The old 1,10,11,12,2,3,4,5... is a remnant of the past when computer operating systems and apps were less fine tuned, less locigal/consistent and harder to use.
Last edit: Anonymous 2020-09-24
KeePass is not a file manager so this is no point here.
If you don't want that simple solution you have to live with the "unsorted" order.
Also thats not a bug because there is no description which says that fields are sorted.
If they would be sorted there would be problems in templates like Credit cards
as the layout is controlled by the squence of fields and not their name.
Last edit: Horst 2020-09-24
There is a point to my suggestion! The example is not about KeePass being a file manager, the example is about being locigally consistant.
Microsoft and many other major companies have understood that. That's why they code their file managers and other apps in such a way that they display the logical 1,2,..,9,10,11,12 order. (Early versions of Windows Explorer have sorted the old way 1,10,11,12,2,3,4,5..., but Microsoft and many other (major) companies have figured out that this is unlogical and have modified their apps to display the logical order 1,2,..,9,10,11,12).
Also, your second statement is not true in all regards. Because KeePass does indeed sort custom the fields alphabetically (and not in the order of time they were created.) That's why for example in the screenshot the custom field "Adresse" appears before the custom fields "E-Mail...". Even though the custom field "Adresse" was created later in time, after "E-Mail..." Your mentioned problem is not a real problem and can easily be sovled because users could name their custom fields (credit card related and whatsoever) in such a way that they have the user-preferred sorting order.
I expect KeePass uses the .NET sort functions. Short of writing new window display routines I'm not sure much can be done.
cheers, Paul
So .NET does not allow this sorting order: 1,2,..,9,10,11,12? I use a disk catalog software written in WPF/C# (.NET Core 5) and it is able to sort tihs way: 1,2,..,9,10,11,12. Also possible in earlier versions, see
Last edit: Anonymous 2020-09-24
Personally, I prefer "1,10,11,12,2,3,4,5...", and get annoyed at the programs that get excessively "helpful" by modifying this. At least this order is widely known and therefore predictable; with "helpful modifications", you can never be sure what you're going to get for the edge cases because everybody codes their own modifier routine differently.
There could be an on/off toggle in the KeePass options to switch between the two styles of sorting.
My impression is that a lot of people (possibly including Dominik) think there are too many options as it is - but feel free to file a new Feature Request.
I'll give it a shot... let's see what he thinks.