Opened 16 years ago

Closed 11 years ago

#363 closed patch (fixed)

Allow "Enable on the fly projection" to be a default

Reported by: w5pny@… Owned by: timlinux
Priority: minor: annoyance Milestone: Version 1.7.0
Component: Projection Support Version: Trunk
Keywords: fly projection Cc: alexbruy
Must Fix for Release: No Platform: All
Platform Version: Awaiting user input: yes

Description

I find that I'd like "Enable on the fly projection" to be on with most of the uses I have in QGIS, so it would be much nicer to remove the check mark for this option when I need to, rather than having to check it for every new project I do. Please provide a way for the user to select which behavior should be the default.

Attachments (3)

otfr_by_default.diff (9.5 KB ) - added by alexbruy 11 years ago.
Proposed patch
projectDefaultCrs.diff (20.9 KB ) - added by borysiasty 11 years ago.
globalProjections.png (63.1 KB ) - added by borysiasty 11 years ago.
The ui from the patch projectDefaultCrs.diff - the strings are simplified, now could be prettified.

Download all attachments as: .zip

Change History (27)

comment:1 by anonymous, 16 years ago

Milestone: Version 0.9 Release
Version: 0.8

comment:2 by timlinux, 15 years ago

Awaiting user input: unset
Must Fix for Release: No
Owner: changed from gsherman to timlinux

comment:3 by pcav, 14 years ago

I think there are good reasons not to enable reprojection by defaults. I suggest to close this ticket.

comment:4 by w5pny, 14 years ago

Since the request was to provide an option so that a user could make enabling reprojection a default behavior, that would not mean it would be the default out of the box. What is an example of a good reason not to do this????

in reply to:  4 comment:5 by msieczka, 14 years ago

Awaiting user input: set
Priority: major: does not work as expectedminor: annoyance or enhancement

Replying to w5pny:

Since the request was to provide an option so that a user could make enabling reprojection a default behavior, that would not mean it would be the default out of the box. What is an example of a good reason not to do this????

Eg. digitisation with re-projection OTF is couple of times slower. Even plain rendering is slower too. In my work most of the times I don't need it enabled, and having to enable it from to time is a better option for me than having to disable it each time I start QGIS.

Can we close this ticket?

comment:6 by timlinux, 14 years ago

Resolution: wontfix
Status: newclosed

Yes I'm going to close this ticket for now. We can re-evaluate default behaviour in the options dialog at a later date.

comment:7 by springmeyer, 14 years ago

Hmm, I agree with the original poster that it would be very useful to allow the user to modify the default behavior of QGIS so that reprojection on the fly is enabled.

I also agree with all parties here that it should not be default behavior, but it should be an option to make it so.

comment:8 by timlinux, 14 years ago

Resolution: wontfix
Status: closedreopened

I'll leave the ticket open and add an option to the options dialog "Enable on the fly projection by default for new projects" or something along those lines. Note: Change wont be made for 0.11.0 release.

Regards

Tim

comment:9 by springmeyer, 14 years ago

Tim,

Sounds excellent.

comment:10 by pcav, 13 years ago

I still think this is not appropriate. OTFP is a computationally expensive option, so if an user selects it and forgets about it, he'll probably complain about a slow QGIS. Resetting it when needed is not painful, so I suggest to leave it as an option, not a default.

comment:11 by pcav, 13 years ago

Platform: DebianAll

in reply to:  11 comment:12 by w5pny, 13 years ago

Replying to pcav:

The request was to be able to SELECT whether or not OTFP is the default. QGIS should continue to be distributed with OTFP not the default, but users should be able to change that behavior if they choose. A user making that change presumably knows what he is doing. Some of us ONLY use OTFP and it is a real nuiscance on every new project to have to set it.

comment:13 by lutra, 13 years ago

Milestone: Version 1.0.3Version 1.2.0
Version: 0.8HEAD

comment:14 by pcav, 12 years ago

Milestone: Version 1.5.0Version 1.6.0

comment:15 by pcav, 12 years ago

Could we implement this option? Looks an easy fix, and may be useful for some users. To prevent the critiques put forward above, a warning should be enough.

comment:16 by borysiasty, 12 years ago

Please also remember about the default CRS. I believe we already have a gui for it - the 'defalut projection' in the Options dialog could be automagically set everytime a fresh project is created. Enabling OTFR without possibility to set the project default CRS will be half-useful only ;)

Another option is to implement project template(s). We would be able to put a default.qgs file to the ~/.qgis folder and set a default projection, OTFR state etc. In case of saving such project Qgis should display a warning and allow to either update the template or redirect to save as.

comment:17 by alexbruy, 11 years ago

Cc: alexbruy added

Here is patch that adds an option to enable OTFP by default and selector for default CRS for it.

by alexbruy, 11 years ago

Attachment: otfr_by_default.diff added

Proposed patch

comment:18 by alexbruy, 11 years ago

Type: enhancementpatch

comment:19 by timlinux, 11 years ago

Status: reopenednew

I'm testing the patch here and will apply it with a few tweaks.

Thanks

Tim

comment:20 by timlinux, 11 years ago

Resolution: fixed
Status: newclosed

Committed Alex's patch (with minor edit to UI labels) as r15344. Updated after that to show user friendly CRS name rather than proj4 string (r15345).

Thanks Alex!

Regards

Tim

comment:21 by borysiasty, 11 years ago

Great, but... yet more messy than was before ;-)

For two years I try to force the possibilty to define default project CRS and I'm always told I'm stupid, but now we're really close and finally I see a ray of hope for understanding! :DD

It's a really great step forward, that now I can select the default CRS for project, but... why ONLY when OTFR is enabled?

I mainly use my national CRS, so everytime when I start Qgis (or click "new project" to clear the workspace), I have to set the CRS. Now I have the alternative: I can turn off the OTFR instead.

Why not to make the CRS selector independent on OTFR? Like that: Use this CRS for new projects: [EPSG:4326] Use OTFR for new projects: [x]

This way we also close the #1355.

Furthermore, the "global default CRS" above is confusing. Some users could think that it is the CRS for projects. The textarea is huge, so we put strong accent on layer CRS and don't care about project CRS. This way we teach users to work with the project mindlessly set to the default 4326. So my second suggestion is to decrease the accent put on the layer CRS (it's not "default CRS" but "default layer CRS" and the epithet "global" is unnecessary)

What do you think?

by borysiasty, 11 years ago

Attachment: projectDefaultCrs.diff added

comment:22 by borysiasty, 11 years ago

Resolution: fixed
Status: closedreopened

There is my proposition attached. (by the way, I've updated the tabstops)

by borysiasty, 11 years ago

Attachment: globalProjections.png added

The ui from the patch projectDefaultCrs.diff - the strings are simplified, now could be prettified.

in reply to:  21 comment:23 by timlinux, 11 years ago

Replying to borysiasty:

Great, but... yet more messy than was before ;-)

For two years I try to force the possibilty to define default project CRS and I'm always told I'm stupid, but now we're really close and finally I see a ray of hope for understanding! :DD

:-)

It's a really great step forward, that now I can select the default CRS for project, but... why ONLY when OTFR is enabled?

I mainly use my national CRS, so everytime when I start Qgis (or click "new project" to clear the workspace), I have to set the CRS. Now I have the alternative: I can turn off the OTFR instead.

Why not to make the CRS selector independent on OTFR? Like that: Use this CRS for new projects: [EPSG:4326] Use OTFR for new projects: [x]

This way we also close the #1355.

Furthermore, the "global default CRS" above is confusing. Some users could think that it is the CRS for projects. The textarea is huge, so we put strong accent on layer CRS and don't care about project CRS. This way we teach users to work with the project mindlessly set to the default 4326. So my second suggestion is to decrease the accent put on the layer CRS (it's not "default CRS" but "default layer CRS" and the epithet "global" is unnecessary)

What do you think?

I agree with your suggestions. Unfortunately I only saw them after r15360. Could you generate a fresh patch against trunk? I will apply it then.

Regards

Tim

comment:24 by borysiasty, 11 years ago

Resolution: fixed
Status: reopenedclosed

Applied in r15374

Note: See TracTickets for help on using tickets.