Feature request #5560

add option for field display order in identify window

Added by Regis Haubourg almost 5 years ago. Updated over 1 year ago.

Status:Closed Start Date:05/09/2012
Priority:Low Due date:
Assigned to:- % Done:

0%

Category:GUI
Target version:Future Release - Nice to have
Platform: Resolution:fixed/implemented
Platform version: Pull Request or Patch supplied:No
Status info: Tag:

Description

Identify window displays fields using alphabetic order. Sometimes it's great, sometimes it's confusing since feature form uses table order, (and other GIS too).
Adding a general option to allow user to choose field order for both identify and feature form would be nice.

History

Updated by Hugo Mercier almost 5 years ago

Right the two forms are a bit heterogeneous. Items in the "identify" window can be sorted by name or by value, but cannot be sorted by table ID, since there is no such column. However :
  1. The feature form (ordered by table id) can be displayed from the identify window through the "View feature form" action
  2. We might consider adding sorting behaviour on the feature form (from the layer properties), since for now it is static

Updated by Regis Haubourg almost 5 years ago

Thanks,
I don't understand why table id can't be used in identify window, since it is possible in field tab (layers properties) and feature form.

1. I just finished 4 Qgis training courses, and every student is confused by the use of the feature form for simple interrogation. I really start to think it is the perfect tool for edition, but not for read only work. What do you think of it?
2. I prefer a general option coming along with 'open feature form if a single feature is identified'. It is a user preference I guesse and not a layer parameter. Do you agree with that?

Updated by Hugo Mercier almost 5 years ago

Ok, I am not really for the addition of a new user preference to circumvent bad window ergonomics.
If the information is well displayed (and sortable) inside the identify form, we can forget the "View feature form".
We now have to figure out a way to make this window fit into the identify form for each item selected.

Updated by Pirmin Kalberer over 4 years ago

  • Target version changed from Version 2.0.0 to Future Release - Nice to have

Updated by Regis Haubourg about 4 years ago

Hi,
could we imagine that field id is used to order identify results at start, and then let user click on column header to sort alphabetically fields. Drawback, it's impossible to return to native datasource field order unless closing identify windo and reopening it. That looks acceptable to me. Any other idea?

Updated by Antonio Locandro almost 3 years ago

Can the identify results display the fields in the order they are in the table? It's very confusing to have the fields order in some way in the table (which I suspect many take the time to order in a particular way for some reason) and then using the identify results window the fields are in another order.

By the way if its alphabetical for some reason it order first capitalized fields and starts again with lower case

Updated by Médéric RIBREUX over 1 year ago

  • Status changed from Open to Feedback

Regis Haubourg wrote:

Hi, could we imagine that field id is used to order identify results at start, and then let user click on column header to sort alphabetically fields. Drawback, it's impossible to return to native datasource field order unless closing identify windo and reopening it. That looks acceptable to me. Any other idea?

Hello, bug triage...

in QGIS 2.13 master (probably in QGIS 2.12.1) the behavior of the identify results is as you described:

  • when identifying multiple results, fields are sorted with the field id.
  • you can change this order by sorting the "Feature" column: fields are now sorted alphabetically (or reversed alphabetically).
  • to return to the field id sort, you have to re-identify the features.

Could we close this feature request ?

Updated by Regis Haubourg over 1 year ago

Yep, I had not been focusing on that part. It is solved.

Updated by Regis Haubourg over 1 year ago

Hi, I don't have rights to close tickets. Can anyone close this one?

Updated by Giovanni Manghi over 1 year ago

  • Status changed from Feedback to Closed
  • Resolution set to fixed/implemented

Also available in: Atom