Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
[processing] If SAGA/OTB exist as bundled app, do not allow manual co…
…nfiguration
- Loading branch information
Showing
5 changed files
with
91 additions
and
73 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
3d15239
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi Victor, I didn't tested yet his patch, does this means that on Windows we cannot choose anymore (manually) to use SAGA 2.0.0 or 2.10? thanks!
3d15239
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi Victor, removing the possibility to choose what SAGA installation to use (on Windows) was on purpose?
3d15239
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, the idea is that, if you are using a QGIS that comes with a packaged SAGA, it should use that one, just like it uses a given version of GDAL or any other library. If you are an advanced user, you can tweak it and replace that folder or edit the QSettings directly, but in the Processing options you will not see an option for that. There is no need for any configuration, since it comes preconfigured.
If there is no packaged SAGA, then you must configure it.
What do you think of this?
3d15239
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi Victor,
I think is ok, simplify things is good and power users can use the workaround to change SAGA to be used. The problem is that on Linux there is the option to use/not use SAGA 2..0.8 (so use SAGA 2.10) while on Windows there isn't. So at this moment in Windows a power user can only use the bundled SAGA (2.0.8) that has a few modules bugged a few of them that have been already fixed/added as specific 2.10 modules. Cheers!
3d15239
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi Victor,
If what Giovanni refers is true, it seems a throwback, not being able to use a newer version of SAGA.
You can not leave this option as it is on Linux?
Thanks Victor!