Version: HEAD (using KDE KDE 3.5.1) Installed from: Compiled From Sources OS: Linux The View String Values dialog will often be used to display the metadata associated with a file. In many cases it is the ordering of the metatdata within the file that is important and not the alphabetical order of the metadata strings. Thus, it would be nice if there was a way to prevent the dialog from automatically sorting entries alphabetically and just having it display entries based on the order in which they were added.
I think that the View Strings dialog should probably be left as it is, in order to be consistent with the other View... dialogs. I also don't think this dialog will be essentially "View Metadata". I can easily foresee having non-string metadata in the near future (I already have it in my test datasource). If the order of the metadata is important, you can either use the "Meta Data" context-menu option in the data manager or just prepend "1-", "2-", "3-", ... to the names of the metadata objects in the data source. Do you have an example of a case where the order is important?
The information stored in a FITS file header. -----Original Message----- From: owner@bugs.kde.org [mailto:owner@bugs.kde.org]On Behalf Of Eli Fidler Sent: February 8, 2007 12:43 PM To: arwalker@sumusltd.com Subject: [Bug 141415] View String Values should not automatically sort entries ------- You are receiving this mail because: ------- You reported the bug, or are watching the reporter. http://bugs.kde.org/show_bug.cgi?id=141415 ------- Additional Comments From eli staikos net 2007-02-08 21:43 ------- I think that the View Strings dialog should probably be left as it is, in order to be consistent with the other View... dialogs. I also don't think this dialog will be essentially "View Metadata". I can easily foresee having non-string metadata in the near future (I already have it in my test datasource). If the order of the metadata is important, you can either use the "Meta Data" context-menu option in the data manager or just prepend "1-", "2-", "3-", ... to the names of the metadata objects in the data source. Do you have an example of a case where the order is important?
Metadata is stored in an unordered data structure. Preserving order for something that is unordered doesn't even make sense, and even then, thsi can be done as an option or as a separate dialog class.
The previous comment seems a little contradictory. I read this as saying that metadata is unordered and so it doesn't make sense to order it, but it could be orderd as an option. As a counter-example FITS metadata is inherently ordered. People who are familiar with FITS would expect to see the metadata presented in the same order as it is given in the FITS file. If we could achieve this via an option or separate dialog class why mark this bug report as a WONTFIX?