Re: [Qgis-developer] Processing broken in 2.14?

2016-07-01 Thread Paolo Cavallini
Il 27/06/2016 10:46, Paolo Cavallini ha scritto: > Il 27/06/2016 10:30, Jürgen E. Fischer ha scritto: >> Hi Paolo, >> >> On Mon, 27. Jun 2016 at 09:26:49 +0300, Paolo Cavallini wrote: >>> using repo http://qgis.org/debian-nightly-release Processing is broken >>> with [0]. Any solution? >> >>

Re: [Qgis-developer] [Qgis-psc] Redmine -> Github tests

2016-07-01 Thread Nathan Woodrow
+1 from me also. Nice work. On Sat, Jul 2, 2016 at 9:38 AM, Nyall Dawson wrote: > On 28 June 2016 at 19:31, Richard Duivenvoorde > wrote: > > Hi Lists (cross posting to have both community, psc and developers), > > > > Still busy ways to migrate

Re: [Qgis-developer] [Qgis-psc] Redmine -> Github tests

2016-07-01 Thread Nyall Dawson
On 28 June 2016 at 19:31, Richard Duivenvoorde wrote: > Hi Lists (cross posting to have both community, psc and developers), > > Still busy ways to migrate from Redmine to Github possibilities, we play > with some options. Wanted to sent some ideas to the lists of current

Re: [Qgis-developer] setting QgsMapCanvas size, for testing map tools

2016-07-01 Thread Sandro Santilli
On Fri, Jul 01, 2016 at 06:47:16PM +0200, Martin Dobias wrote: > I think what you are up to is not to find out scale(), but actually > mapUnitsPerPixel(). Scale in QGIS is calculated as ( extent_width / ( > canvas_width * dpi) ) with some extra conversions involved, see > QgsScaleCalculator

Re: [Qgis-developer] setting QgsMapCanvas size, for testing map tools

2016-07-01 Thread Martin Dobias
Hi Tom On Fri, Jul 1, 2016 at 5:25 PM, Tom Chadwin wrote: > Hi Martin > > > Martin Dobias wrote > iface.mapCanvas().geometry() >> PyQt4.QtCore.QRect(0, 0, 879, 390) > iface.mapCanvas().viewport().geometry() >> PyQt4.QtCore.QRect(3, 3, 873, 384) > > Ah, OK! I

Re: [Qgis-developer] setting QgsMapCanvas size, for testing map tools

2016-07-01 Thread Martin Dobias
Hi Sandro On Fri, Jul 1, 2016 at 6:07 PM, Sandro Santilli wrote: > On Fri, Jul 01, 2016 at 05:58:57PM +0200, Sandro Santilli wrote: >> On Thu, Jun 30, 2016 at 10:14:34PM +0100, Barry Rowlingson wrote: >> > Maybe I've missed something here, but doesn't the canvas resize method >> >

[Qgis-developer] Plugin [332] geoUmbriaSUIT approval notification.

2016-07-01 Thread noreply
Plugin geoUmbriaSUIT approval by pcav. The plugin version "[332] geoUmbriaSUIT 2.6.8" is now approved Link: http://plugins.qgis.org/plugins/geoUmbriaSUIT/ ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org List info:

[Qgis-developer] Plugin [412] Qgis2threejs approval notification.

2016-07-01 Thread noreply
Plugin Qgis2threejs approval by pcav. The plugin version "[412] Qgis2threejs 1.4.1" is now approved Link: http://plugins.qgis.org/plugins/Qgis2threejs/ ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org List info:

[Qgis-developer] Plugin [1000] Qdraw approval notification.

2016-07-01 Thread noreply
Plugin Qdraw approval by pcav. The plugin version "[1000] Qdraw 1.3 Experimental" is now approved Link: http://plugins.qgis.org/plugins/qdraw/ ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org List info:

Re: [Qgis-developer] setting QgsMapCanvas size, for testing map tools

2016-07-01 Thread Sandro Santilli
On Fri, Jul 01, 2016 at 05:58:57PM +0200, Sandro Santilli wrote: > On Thu, Jun 30, 2016 at 10:14:34PM +0100, Barry Rowlingson wrote: > > Maybe I've missed something here, but doesn't the canvas resize method > > set the canvas pixel size? This behaves as expected when run > > standalone from a

[Qgis-developer] exporting QgsMapToolNodeTool, for testing

2016-07-01 Thread Sandro Santilli
Attempts to add a test for QgsMapToolNodeTool result in failures due to the class not being exported. Is there a policy about what to do in these cases ? Should I just export the class or is there some other test-oriented trick ? --strk; () Free GIS & Flash consultant/developer /\

Re: [Qgis-developer] setting QgsMapCanvas size, for testing map tools

2016-07-01 Thread Sandro Santilli
On Thu, Jun 30, 2016 at 10:14:34PM +0100, Barry Rowlingson wrote: > Maybe I've missed something here, but doesn't the canvas resize method > set the canvas pixel size? This behaves as expected when run > standalone from a python prompt. It does ! Thanks for the pointer. --strk;

Re: [Qgis-developer] setting QgsMapCanvas size, for testing map tools

2016-07-01 Thread Tom Chadwin
Hi Martin Martin Dobias wrote iface.mapCanvas().geometry() > PyQt4.QtCore.QRect(0, 0, 879, 390) iface.mapCanvas().viewport().geometry() > PyQt4.QtCore.QRect(3, 3, 873, 384) Ah, OK! I didn't know anything about a canvas frame. So, without doing setFrameStyle(), does canvas.extent()

Re: [Qgis-developer] setting QgsMapCanvas size, for testing map tools

2016-07-01 Thread Martin Dobias
Hi Tom! On Fri, Jul 1, 2016 at 1:08 PM, Tom Chadwin wrote: > Barry Rowlingson wrote >> Maybe I've missed something here, but doesn't the canvas resize method >> set the canvas pixel size? This behaves as expected when run >> standalone from a python prompt. >> >> from

Re: [Qgis-developer] setting QgsMapCanvas size, for testing map tools

2016-07-01 Thread Tom Chadwin
Barry Rowlingson wrote > Maybe I've missed something here, but doesn't the canvas resize method > set the canvas pixel size? This behaves as expected when run > standalone from a python prompt. > > from qgis.core import * > from qgis.gui import * > app = QgsApplication([],True) > canvas =

Re: [Qgis-developer] Missing next() method in Python 3 QgsFeatureIterator in master

2016-07-01 Thread Matthias Kuhn
On 07/01/2016 12:34 PM, Alessandro Pasotti wrote: > Thanks! > > I thought that the RefactoringTool: was taking care of that. I guess you are referring to -DPORT_PLUGINS=ON (which is enabled on travis/py3). > Isn't the 2to3 run automatically on the test python files too? No. Actually it would

Re: [Qgis-developer] Compiling QGIS debian rules test time out

2016-07-01 Thread matteo
Hi Matthias, I see that in debian/rules webkit is disabled for some distribution ifneq (,$(findstring $(DISTRIBUTION),"sid stretch xenial")) CMAKE_OPTS += -DWITH_QTWEBKIT=FALSE I'm on xenial right now.. but same thing happens on a debian stretch machine.. anyway it should be

Re: [Qgis-developer] Missing next() method in Python 3 QgsFeatureIterator in master

2016-07-01 Thread Alessandro Pasotti
Thanks! I thought that the RefactoringTool: was taking care of that. Isn't the 2to3 run automatically on the test python files too? In my case the error was not directly in a test but in a file imported by a test: offlineditingtestbase.py is that the reason why it was not refactored?

Re: [Qgis-developer] Compiling QGIS debian rules test time out

2016-07-01 Thread Matthias Kuhn
Hi Matteo, Is webkit installed? Matthias On 07/01/2016 12:26 PM, matteo wrote: > Hi devs, > > I'm compiling QGIS master on a Ubuntu 16.04 machine (fresh installation) > with the debian rules.. > > after the make running there are some test made, some of them reaches > the timeout (1500 sec)..

[Qgis-developer] Compiling QGIS debian rules test time out

2016-07-01 Thread matteo
Hi devs, I'm compiling QGIS master on a Ubuntu 16.04 machine (fresh installation) with the debian rules.. after the make running there are some test made, some of them reaches the timeout (1500 sec).. is that behavior normal? in this way it takes a a huge time to compile QGIS.. is it

Re: [Qgis-developer] Missing next() method in Python 3 QgsFeatureIterator in master

2016-07-01 Thread Matthias Kuhn
Hi Alessandro On 07/01/2016 11:59 AM, Alessandro Pasotti wrote: > Hi, > > I'm trying to adapt a test to Py3/Qt5 and I get this odd error: > > AttributeError: 'QgsFeatureIterator' object has no attribute 'next' ./scripts/2to3 is your friend http://stackoverflow.com/a/12274637/2319028

[Qgis-developer] Missing next() method in Python 3 QgsFeatureIterator in master

2016-07-01 Thread Alessandro Pasotti
Hi, I'm trying to adapt a test to Py3/Qt5 and I get this odd error: AttributeError: 'QgsFeatureIterator' object has no attribute 'next' The C++-like call works fine: fit=layer.dataProvider().getFeatures(request) f=QgsFeature() fit.nextFeature(f) True the layer is a test layer: