I currently use 2.18 to work around some bugs in 3.0, and it is possible
even with the difference in project file formats as there is enough
compatibility. Although lately the CRS translation has been broken when
opening a 3.0 project in 2.18 and I have been told there is no
guaranteed
Hi all
Have you started a country level QGIS user group in the last year? I will
shortly be putting out a call for nominations for new voting members and we
need to know about any new user groups that were formed in this year as under
our governance system we appoint a voting member from the
Hi Gary,
Which CMake version are you using? There is a flaw with CMake 3.9.0 thru
3.9.3 that affects automoc targets, which gave me similar errors:
https://gitlab.kitware.com/cmake/cmake/issues/17278
Works for me with CMake 3.9.4+, using Homebrew dependencies.
Larry Shaffer
Dakota Cartography
Hi,
On Mon, Dec 4, 2017 at 2:00 AM, Richard Duivenvoorde
wrote:
> On 04-12-17 01:01, Nathan Woodrow wrote:
> > Hey all,
> >
> > Just wanted to see how everyone would feel if I was thinking about
> > backporting the crash handler we have in QGIS 3 back into 2.18.
>
+ 1
A huge +1 from me - as a Windows user, it's frustrating not to be able to
investigate the occasional times PyQGIS causes a Windows minidump.
Tom
-
Buy Pie Spy: Adventures in British pastry 2010-11 on Amazon
--
Sent from: http://osgeo-org.1560.x6.nabble.com/QGIS-Developer-f4099106.html
+1
Luigi Pirelli
**
* LinkedIn: https://www.linkedin.com/in/luigipirelli
* Stackexchange: http://gis.stackexchange.com/users/19667/luigi-pirelli
* GitHub: https://github.com/luipir
* Mastering QGIS
Plugin opeNoise approval by zimbogisgeek.
The plugin version "[480] opeNoise 1.0" is now approved
Link: http://plugins.qgis.org/plugins/opeNoise/
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info:
Hi
+1 from me - it will be a good addition to the LTR!
Regards
Tim
> On 04 Dec 2017, at 02:01, Nathan Woodrow wrote:
>
> Hey all,
>
> Just wanted to see how everyone would feel if I was thinking about
> backporting the crash handler we have in QGIS 3 back into 2.18.
On 04-12-17 01:01, Nathan Woodrow wrote:
> Hey all,
>
> Just wanted to see how everyone would feel if I was thinking about
> backporting the crash handler we have in QGIS 3 back into 2.18.
I think it is a good idea...
As you say, 2.18 will be here for some time (especially for educational
and