Opened 16 years ago
Last modified 13 years ago
#1320 new enhancement
Projection Selector dialog changes for uniformity and clarity
Reported by: | smizuno | Owned by: | timlinux |
---|---|---|---|
Priority: | major: does not work as expected | Milestone: | Version 1.7.0 |
Component: | GUI | Version: | Trunk |
Keywords: | Cc: | otto.dassau@… | |
Must Fix for Release: | No | Platform: | All |
Platform Version: | Awaiting user input: | no |
Description
- the title of the Projection Selector dialogs that appear on layer load and for change CRS in layer properties should be "Select Coordinate Reference System" or something like that in keeping with the recent change to the use of coordinate reference system nomenclature.
- the title of said dialog should include the layer name or datasource, at least on layer load when no CRS is found. This is because multiple layers may be loaded at one time and the load order or even that some do have a CRS detected leads to confusion as to which layer needs a CRS assigned.
- the text (Define this layer's projection...) that appears on some of the dialogs explaining what the dialog is about refers to Projection. This should be changed to Coordinate Reference System as it is the current usage.
- for vector layers, including GPS layers, the Projection Selector dialog presented from the layer properties, change CRS, should not have the text about defining the layer projection because one wasn't found. The text is somewhat misleading since one should have been set at layer load. The change CRS dialog for raster layer properties does not have this text, so vector layers should be the same.
Change History (6)
comment:1 by , 16 years ago
Owner: | changed from | to
---|
comment:2 by , 16 years ago
Cc: | added |
---|
Hi
I agree these are probably worth fixing - but you would need to get the OK from the community team folks to break the GUI freeze for this since it will impact their work. Otherwise we should wait for QGIS 1.1.
Otto can you sound out the manual folks on this?
Regards
Tim
comment:3 by , 16 years ago
it is ok for the community team. We adapt the changes in the manual - no problem.
regards,
Otto
comment:4 by , 14 years ago
What is the current state of this ticket? We are now changing the GUI in many palces, so it would seem the right time to apply this (or reject it).
comment:5 by , 14 years ago
Milestone: | Version 1.0.3 → Version 1.6.0 |
---|
comment:6 by , 13 years ago
Must Fix for Release: | Yes → No |
---|
Note:
See TracTickets
for help on using tickets.
Is this to late to update, Tim?