Re: [Qgis-user] [Qgis-developer] Any working GRASS in QGIS available? - Processing Bug?

2015-08-12 Thread Andrew
Sure thing. Open the .qgis2/python/plugins/processing/algs/grass7/ folder and open the Grass7Algorithm.py file in a text editor. You can see the changes that you'll need to make on GitHub: https://github.com/qgis/QGIS/commit/2a14ffd281d0a0e99a0a899622a29ca0efdb0852 It is just a couple small chan

Re: [Qgis-user] [Qgis-developer] Any working GRASS in QGIS available? - Processing Bug?

2015-08-11 Thread Bernd Vogelgesang
Hi Andrew Am 06.08.2015, 19:20 Uhr, schrieb Andrew : Victor, I edited the version of the processing plugin that i have installed (QGIS 2.8.3, processing 2.10.1) with the changes you made and >now GRASS7 tools work as they should, thanks! Andrew Could you maybe describe a little bit wh

Re: [Qgis-user] [Qgis-developer] Any working GRASS in QGIS available? - Processing Bug?

2015-08-06 Thread Andrew
Victor, I edited the version of the processing plugin that i have installed (QGIS 2.8.3, processing 2.10.1) with the changes you made and now GRASS7 tools work as they should, thanks! Andrew On Thu, Aug 6, 2015 at 5:59 AM, Victor Olaya wrote: > A quick (but very relevant) note about GRASS7: >

Re: [Qgis-user] [Qgis-developer] Any working GRASS in QGIS available? - Processing Bug?

2015-08-06 Thread Victor Olaya
A quick (but very relevant) note about GRASS7: It seems that, in one of the latest changes, I unintentionally left out a code line where GRASS was actually being called. I was getting a bit crazy wondering where the error might be and why GRASS7 was not working in the latest releaseand finally

Re: [Qgis-user] [Qgis-developer] Any working GRASS in QGIS available? - Processing Bug?

2015-08-02 Thread Bernd Vogelgesang
Hi Alex Am 03.08.2015, 01:20 Uhr, schrieb Alex Mandel : Ah but we're closer to finding a solution with all those details. It may be fixable in Processing, which can be pushed to the plugin repo for update any time. Passing this along to devs who might have enough information now. Thanks, Alex