QGIS » QGIS Application

I see at least gdal and grass here, current master.

I had a look into this, seems pretty easy to fix this line:

https://github.com/qgis/QGIS/blob/master/python/plugins/processing/core/GeoAlgorithm.py#L141

helpUrl = 'http://docs.qgis.org/{}/en/docs/user_manual/processing_algs/{}/{}/{}.html'.format(qgsVersion, providerName, safeGroupName, safeAlgName)

into

helpUrl = 'http://docs.qgis.org/{}/en/docs/user_manual/processing_algs/{}/{}.html#{}'.format(qgsVersion, providerName, safeGroupName, safeAlgName)

BUT: the safeAlgName is already 'cleaned', so there are no '-' in it anymore, while the anchors in the html file contain '-'

EG: using the line above, you will get the following url:

http://docs.qgis.org/testing/en/docs/user_manual/processing_algs/qgis/vector_general_tools.html#orientedminimumboundingbox

while the anchor in current html files are like:

http://docs.qgis.org/testing/en/docs/user_manual/processing_algs/qgis/vector_general_tools.html#oriented-minimum-bounding-box

so EITHER we have to have a look into the 'cleaning'-up of the url-components
OR we change the helpfiles to have anchors like #orientedminimumboundingbox

Paolo Cavallini wrote:

I see at least gdal and grass hel here, current master.

Hi Paolo,

you say 'hel' you mean 'hell', like it is not working for you?

Because for me grass7 is (with or without my 'patch') still working ok.

GDAL is alway pointing to the same url (ogr2ogr).

I think there was a discussion already about where to point for help to for these external algorithm's isn't it?

Typo, now corrected, sorry.

Anita, I had seen that too, following is an email from me to alex and victor, (we are talking about
https://github.com/qgis/QGIS/blob/master/python/plugins/processing/gui/AlgorithmDialogBase.py#L80 here)

Ok, it has something to do with the anchor loading in a non visible
webview tab.

If I add this
self.tabWidget.setCurrentIndex(2)·
above the line:
self.txtHelp.load(algHelp)

Then it just works....
But that means that the dialog always opens with the help, which is not
what we want off course...

So another hack would be to reload(!) the url when a user hits the help
tab. Tried that but that is ugly...

So third hack is to do 'lazy loading' of the help, that is only load the url
when the user hits the help tab.
Below some code which does that. Not sure if people are ok with that,
because that means it takes some seconds to fetch the help after going to the help...

But to me this would be ok

...
        # load algorithm help if available
        isText, algHelp = self.alg.help()
        if algHelp is not None:
            algHelp = algHelp if isText else QUrl(algHelp)
        else:
            algHelp = self.tr('<h2>Sorry, no help is available for this '
                              'algorithm.</h2>')
        try:
            if isText:
                self.txtHelp.setHtml(algHelp)
            else:
        # connect pressing tab to loadHelp func
                self.tabWidget.currentChanged.connect(self.loadHelp)
        # msg to user
                self.txtHelp.setHtml(self.tr('<h2>Getting help...</h2>'))
        # save QUrl for help
                self.algHelp = algHelp
        except:
            self.txtHelp.setHtml(
                self.tr('<h2>Could not open help file  </h2>'))

        self.showDebug = ProcessingConfig.getSetting(
            ProcessingConfig.SHOW_DEBUG_IN_DIALOG)

    def loadHelp(self, i):
    # only when the help tab is activated load the url
        if i == 2:
            self.txtHelp.load(self.algHelp)

Victor Olaya wrote:

can you provide more detail?

I am not able to reproduce it here

I just open any QGIS algorithm in the Processing toolbox and went to its Help tab. Nothing special.

Moreover, the code in the changeset that I added does not modify the URL of the help file or the way the page is loaded, it just adds the scrolling mechanism. It seems to me that the server for some reason was responding with that and changed the URL when displaying the message.

BTW, could the scrolling fix be backported to 2.8?

What do you get if you revert to a version before that changeset?

Thanks!

I've never succeeded building QGIS myself (on Win7 to 10) so I just use osgeo4w but I can't find how I can revert to a nightly build older than yesterday's. Any idea?

I can't reproduce the issue either (using OSGeo4W nightly). Are you sure you have the latest Processing version? Check the plugin manager. For me it says:

Installed version: 2.10.99 (in C:\\OSGEO4~1\\apps\\qgis-dev\\.\\python\\plugins\\processing)
Available version: 2.10.2 (in Offizielles QGIS-Erweiterungsrepositorium)

The Processing version i had in LTR was 2.6 (if I'm not wrong) so I update it to 2.10.2. New version was saved in \\.qgis2 folder, meaning that reopening qgis master (or any other release) fetches the processing version in \\.qgis2 and not the one in \\osgeo\\app folder.
I suppose I just have to copy/paste the 2.10.2 folder in ltr and delete it from \\.qgis2 and all will be ok but I'm wondering if there's not an issue with Processing updating.

Since it's a core plugin, shipped in app folder, shouldn't updating be made over the shipped version instead of creating a new folder in \\.qgis2?
Am I missing something or should I open a ticket for this (if there isn't)?

@Harrissou fyi: processing is a core plugin, so when you install a version of QGIS the plugin is included in the QGIS-standard plugins folder. But when you update your plugins, and there is a newer version, the plugin is downloaded and put in your PERSONAL plugin folder.

If all is ok, the plugins in your peronsal folder should shadow the ones in the standard(installation) plugin folder, so you should not see/use the 'older' one.

IF there is still something wrong there (2.6 is old, and there have been issues with this in history), and you can give a clear way to describe, please create a new issue for this.

Richard Duivenvoorde wrote:

@Harrissou fyi: processing is a core plugin, so when you install a version of QGIS the plugin is included in the QGIS-standard plugins folder. But when you update your plugins, and there is a newer version, the plugin is downloaded and put in your PERSONAL plugin folder.

If all is ok, the plugins in your peronsal folder should shadow the ones in the standard(installation) plugin folder, so you should not see/use the 'older' one.

This is what I understood, what I said and what I'm complaining about (it doesn't just shadow older's). see #13685