-
-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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
Comments
Author Name: Richard Duivenvoorde (@rduivenvoorde)
|
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?
|
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?
|
Author Name: Richard Duivenvoorde (@rduivenvoorde) ok, final one :-) moved 'depricated' to below, hidden searchtools as space below 'crs of the world'
|
Author Name: Hilmy Hashim (Hilmy Hashim) Richard Duivenvoorde wrote:
More space for the selected crs parameters please. The second line is always half hidden. |
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). |
Author Name: Alister Hood (@AlisterH) Hi guys. Maybe I should open another ticket... but this one hasn't been closed yet ;)
|
Author Name: Paolo Cavallini (@pcav) Also, the box with the proj.4 string is often too small, and could be adjusted to its content. |
Author Name: Giovanni Manghi (@gioman)
|
Author Name: Richard Duivenvoorde (@rduivenvoorde) see this mailinglist thread: http://lists.osgeo.org/pipermail/qgis-developer/2011-December/017380.html
the behaviour is even a little stranger. If I open 'Specify CRS' from |
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. |
Author Name: Giovanni Manghi (@gioman) Giovanni Manghi wrote:
I see also that internal ID is not searchable with the filter. |
Author Name: Richard Duivenvoorde (@rduivenvoorde) The third point of this issue (see top) was: 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. |
Author Name: Giovanni Manghi (@gioman) Richard Duivenvoorde wrote:
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. |
Author Name: Richard Duivenvoorde (@rduivenvoorde) I think most/all point mentioned above are now fixed in this pull request If the request is honoured we should close this bug
|
Author Name: Richard Duivenvoorde (@rduivenvoorde) Giovanni found a bug in my implemenation... Busy fixing it. (hope this will reopen this issue)
|
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.
The text was updated successfully, but these errors were encountered: