[Qgis-developer] Setting snapping settings via Python

Hi, Is there a way to set the snapping settings for a layer via Python? I would like to turn on snapping with a specified tolerance automatically when a user begins editing within a plugin. There is a question on gis.stackexchange, but it hasn't been answered.

Re: [Qgis-developer] Setting snapping settings via Python

This old thread might also help: http://osgeo-org.1560.x6.nabble.com/getting-QgsMapCanvasSnapper-to-work-td4147067.html -- View this message in context: http://osgeo-org.1560.x6.nabble.com/Setting-snapping-settings-via-Python-tp5246362p5246373.html Sent from the Quantum GIS - Developer

Re: [Qgis-developer] Setting snapping settings via Python

Is it http://qgis.org/api/classQgsSnapper.html? -- View this message in context: http://osgeo-org.1560.x6.nabble.com/Setting-snapping-settings-via-Python-tp5246362p5246371.html Sent from the Quantum GIS - Developer mailing list archive at Nabble.com.

Re: [Qgis-developer] Help us plan for QGIS 3.0

Hi, On 01/19/2016 11:48 AM, Hugo Mercier wrote: > Just an idea: what about a 2.16 being an LTR rather than the 2.14 ? That would address some of the concerns brought up. I like the idea. Best -- Matthias Kuhn OPENGIS.ch - https://www.opengis.ch Spatial • (Q)GIS • PostGIS • Open Source

Re: [Qgis-developer] Version <=1.9 project bug reports?

+1 Luigi Pirelli ** * Boundless QGIS Support/Development: lpirelli AT boundlessgeo DOT com * LinkedIn: https://www.linkedin.com/in/luigipirelli * Stackexchange:

Re: [Qgis-developer] Help us plan for QGIS 3.0

> Just an idea: what about a 2.16 being an LTR rather than the 2.14 ?  Counter-argument. This breaks the only newly established LTR release cycle which is cited as very attractive to corporate users. -- View this message in context:

Re: [Qgis-developer] Help us plan for QGIS 3.0

Il 20/01/2016 08:55, Hugo Mercier ha scritto: > Yes, I think there are still some open questions around some of these > QEPs. I still need a little bit of time to clean them all and call for a > vote. I'll try to do it soon. Looking forward to it, thanks. Any other major plans? What is the state

Re: [Qgis-developer] Help us plan for QGIS 3.0

On 20/01/2016 08:52, Hugo Mercier wrote: > > On my list I have : > > - a new symbol layer to draw straight and curved arrows on line layers, > as it's done by the "Arrows" plugin > - allow to pin diagrams > - some new drawing tools in the composer (polygons, lines) > I also have an "unmerged"

[Qgis-developer] Call for Presentations and Workshops. 2nd Int. QGIS Conference, May 2016

The Call for Papers and Workshops for the 2nd International QGIS User and Developer Conference, is already open! The Local Organizing Committee of the 2nd International QGIS User and Developer Conference, is pleased to announce the call for Presentations and Workshops for the 2016 Conference

Re: [Qgis-developer] Qt4->Qt5 timeline: WebKit and WebEngine in Fedora

Hi all, FYI this was just sent out for the upcoming Fedora version. == Detailed Description == QtWebEngine is the new web engine by the Qt project based on Chromium, effectively replacing QtWebKit, though it is not a drop-in replacement. QtWebEngine will be available in Fedora as an additional

Re: [Qgis-developer] Help us plan for QGIS 3.0

But as a FINAL 2.x release it would make sense to be a LTR, wouldn't it. To give time before moving to 3.x. *Worth Lutz* On 1/20/2016 4:28 AM, Tom Chadwin wrote: Just an idea: what about a 2.16 being an LTR rather than the 2.14 ? Counter-argument. This breaks the only newly established LTR

Re: [Qgis-developer] Can :class: :mod: :func: be removed from python cookbook?

2016-01-20 14:25 GMT+01:00 Richard Duivenvoorde : > (sorry for cross posting) > > Hi Devs and Python cookbook writers, > > As you may know if you follow community list, we have a travis build now > for QGIS documentation (and python cookbook then). > > To make Travis fail, I

Re: [Qgis-developer] Help us plan for QGIS 3.0

Il 20/01/2016 14:05, Worth Lutz ha scritto: > But as a FINAL 2.x release it would make sense to be a LTR, wouldn't > it. To give time before moving to 3.x. Yes, that was my idea, thanks for clarifying. All the best. -- Paolo Cavallini - www.faunalia.eu QGIS & PostGIS courses:

[Qgis-developer] Can :class: :mod: :func: be removed from python cookbook?

(sorry for cross posting) Hi Devs and Python cookbook writers, As you may know if you follow community list, we have a travis build now for QGIS documentation (and python cookbook then). To make Travis fail, I build the docs with an option that warning become errors, thereby making it clear for

Re: [Qgis-developer] Can :class: :mod: :func: be removed from python cookbook?

Hi Richard On Wed, Jan 20, 2016 at 2:25 PM, Richard Duivenvoorde wrote: > > So: is it ok for you if I just delete all this :class: stuff? So it will > never be possible anymore to make that a reference to api. > > I will leave the backquotes, so it will at least be made

Re: [Qgis-developer] Can :class: :mod: :func: be removed from python cookbook?

Hi Richard, It should be straightforward to extend sphinx to add whole domains (py:class, py:mod, py:func) to the ignore list or add wildcard support. https://github.com/sphinx-doc/sphinx/issues/537 https://github.com/sphinx-doc/sphinx/commit/f5ecd62d05fa5502795e31ac5cc8778c570269cd Matthias

Re: [Qgis-developer] Can :class: :mod: :func: be removed from python cookbook?

On 20-01-16 14:36, Matthias Kuhn wrote: > Hi Richard, > > It should be straightforward to extend sphinx to add whole domains > (py:class, py:mod, py:func) to the ignore list or add wildcard support. > > https://github.com/sphinx-doc/sphinx/issues/537 > >

Re: [Qgis-developer] Can :class: :mod: :func: be removed from python cookbook?

On 01/20/2016 03:19 PM, Richard Duivenvoorde wrote: > On 20-01-16 14:36, Matthias Kuhn wrote: >> Hi Richard, >> >> It should be straightforward to extend sphinx to add whole domains >> (py:class, py:mod, py:func) to the ignore list or add wildcard support. >> >>