Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improvements to projection widget #14464

Closed
qgib opened this issue Nov 17, 2011 · 18 comments
Closed

Improvements to projection widget #14464

qgib opened this issue Nov 17, 2011 · 18 comments
Labels
Bug Either a bug report, or a bug fix. Let's hope for the latter! GUI/UX Related to QGIS application GUI or User Experience
Milestone

Comments

@qgib
Copy link
Contributor

qgib commented Nov 17, 2011

Author Name: Paolo Cavallini (@pcav)
Original Redmine Issue: 4550
Affected QGIS version: master
Redmine category:gui
Assignee: Richard Duivenvoorde


I think the projection widget should be improved, by
** having the search filtering the projections rather than moving to the next matching (see e.g. in the plugin list)
** it would be good to have the search working in both fields (people often overlook the search field selector)
** the internal projection ID could be hidden (I do not see any use of it for the user)
** set the focus to the 'find' button as soon as you try to type something into the find-text input.
Now the user often type a code and then hit without result, because 'apply' apparently has focus: you really have to click the button
** better make a general find: just search over al fields, so we can remove the two dropdowns

Single tickets might be opened, but I think once we start cleaning up the interface it is a simple matter to do all.


@qgib
Copy link
Contributor Author

qgib commented Nov 18, 2011

Author Name: Richard Duivenvoorde (@rduivenvoorde)


  • done_ratio was changed from 0 to 50
  • assigned_to_id was configured as Richard Duivenvoorde

@qgib
Copy link
Contributor Author

qgib commented Nov 18, 2011

Author Name: Richard Duivenvoorde (@rduivenvoorde)


I've more or less implemented above: by using the a (over all columns).

I need some input for the dialogs. I've hidden the comboboxes and findbutton (programmatically) so all 'old' code is still in there.

In Version1 I just moved the filter/search part above the two crs blocks

In Version2 I moved both the filter AND the recently used crs block to the top.

Please some input about the preferred way.

I also have to look at the behaviour of for the wms dialog: apparently you should see all available crs's there?


  • 3556 was configured as version1.png
  • 3557 was configured as version2.png

@qgib
Copy link
Contributor Author

qgib commented Nov 21, 2011

Author Name: Richard Duivenvoorde (@rduivenvoorde)


version3 with some more space for both lists, and a title in top of the crs's of the world

maybe too high?


  • 3560 was configured as version3.png

@qgib
Copy link
Contributor Author

qgib commented Nov 22, 2011

Author Name: Richard Duivenvoorde (@rduivenvoorde)


ok, final one :-)

moved 'depricated' to below, hidden searchtools as space below 'crs of the world'


  • 3561 was configured as version4.png

@qgib
Copy link
Contributor Author

qgib commented Nov 22, 2011

Author Name: Hilmy Hashim (Hilmy Hashim)


Richard Duivenvoorde wrote:

ok, final one :-)

moved 'depricated' to below, hidden searchtools as space below 'crs of the world'

More space for the selected crs parameters please. The second line is always half hidden.

@qgib
Copy link
Contributor Author

qgib commented Nov 22, 2011

Author Name: Richard Duivenvoorde (@rduivenvoorde)


This has always been the case I think. There can actually (depending on the size of the dialog) be 3 or 4 lines of proj-parameters. But we also want to minimize the size of the dialog. Besides that, there is actually nothing you can do with those parameters (besides look at them...).

So: given we want to miminize the dialog: do you still want it to be bigger?

(by the way: the changes is already in master, so please have a look and try).

@qgib
Copy link
Contributor Author

qgib commented Nov 30, 2011

Author Name: Alister Hood (@AlisterH)


Hi guys. Maybe I should open another ticket... but this one hasn't been closed yet ;)

  • When adding a new layer, if the mouse cursor is over the window border or over the handle between the list of recent CRSs and the list of all CRSs, for some reason the cursor does not change to the arrow cursor which normally indicates resizing is possible.
    When changing the CRS of an existing layer, the mouse cursor does change.
    N.B. I am on Windows, if that matters.

  • If the user makes the window taller, the text panel at the top gets taller - but there is no need for this. Would it be possible to fix its size, so that all the additional height is used for the list of projections?

@qgib
Copy link
Contributor Author

qgib commented Nov 30, 2011

Author Name: Paolo Cavallini (@pcav)


Also, the box with the proj.4 string is often too small, and could be adjusted to its content.

@qgib
Copy link
Contributor Author

qgib commented Dec 16, 2011

Author Name: Giovanni Manghi (@gioman)


  • fixed_version_id was configured as Version 1.7.4

@qgib
Copy link
Contributor Author

qgib commented Dec 20, 2011

Author Name: Richard Duivenvoorde (@rduivenvoorde)


see this mailinglist thread:

http://lists.osgeo.org/pipermail/qgis-developer/2011-December/017380.html

The current implementation of the CRS selector is much nicer, but it has
a problem: the first item on the list of recent CRSs is always selected
automatically when the widget is opened, without the user could notice
it, or do anything about.

the behaviour is even a little stranger. If I open 'Specify CRS' from
the layerproperties, it will show me just 4 recent crs's (while there is
room for more), while it seems to select one of them (not neccesarily my
latest). But if I close and open the dialog again, it chooses the NEXT
crs from my 4 recents...

@qgib
Copy link
Contributor Author

qgib commented Dec 21, 2011

Author Name: Giovanni Manghi (@gioman)


Hi Richard,

it would be possible to show the "internal" ID column? It is pretty much important when working with custom CRSs.

@qgib
Copy link
Contributor Author

qgib commented Dec 21, 2011

Author Name: Giovanni Manghi (@gioman)


Giovanni Manghi wrote:

Hi Richard,

it would be possible to show the "internal" ID column? It is pretty much important when working with custom CRSs.

I see also that internal ID is not searchable with the filter.

@qgib
Copy link
Contributor Author

qgib commented Dec 21, 2011

Author Name: Richard Duivenvoorde (@rduivenvoorde)


The third point of this issue (see top) was:
"the internal projection ID could be hidden (I do not see any use of it for the user)"

But we can bring it back again, and we can also take it into the filter. No problem.

Personally I think it is REALLY an internal projection ID and you should not see or use it.

But: please let somebody decide. Both is no problem.

@qgib
Copy link
Contributor Author

qgib commented Dec 21, 2011

Author Name: Giovanni Manghi (@gioman)


Richard Duivenvoorde wrote:

The third point of this issue (see top) was:
"the internal projection ID could be hidden (I do not see any use of it for the user)"

But we can bring it back again, and we can also take it into the filter. No problem.

Personally I think it is REALLY an internal projection ID and you should not see or use it.

But: please let somebody decide. Both is no problem.

sorry richard, I didn't read carefully this ticket. I just noticed it and commented, but if others have suggested otherwise is ok for me. sorry again.

@qgib
Copy link
Contributor Author

qgib commented Dec 22, 2011

Author Name: Richard Duivenvoorde (@rduivenvoorde)


I think most/all point mentioned above are now fixed in this pull request

#76

If the request is honoured we should close this bug


  • crashes_corrupts_data was configured as 0
  • done_ratio was changed from 50 to 90
  • version was configured as master

@qgib
Copy link
Contributor Author

qgib commented Dec 22, 2011

Author Name: Jürgen Fischer (@jef-n)


applied in 5829fed


  • status_id was changed from Open to Closed
  • resolution was changed from to fixed

@qgib
Copy link
Contributor Author

qgib commented Dec 27, 2011

Author Name: Richard Duivenvoorde (@rduivenvoorde)


Giovanni found a bug in my implemenation... Busy fixing it.

(hope this will reopen this issue)


  • status_id was changed from Closed to Feedback

@qgib
Copy link
Contributor Author

qgib commented Jan 6, 2012

Author Name: Alexander Bruy (@alexbruy)


Pull request 77 applied in 9509999. Hope this is completely fix issue


  • status_id was changed from Feedback to Closed

@qgib qgib added Bug Either a bug report, or a bug fix. Let's hope for the latter! GUI/UX Related to QGIS application GUI or User Experience labels May 24, 2019
@qgib qgib added this to the Version 1.7.4 milestone May 24, 2019
@qgib qgib closed this as completed May 24, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Either a bug report, or a bug fix. Let's hope for the latter! GUI/UX Related to QGIS application GUI or User Experience
Projects
None yet
Development

No branches or pull requests

1 participant