Re: [QGIS-Developer] Drag and drop to PostGIS crash
On Tue, May 30, 2017 at 04:39:01PM +1000, Nyall Dawson wrote: > On 30 May 2017 at 16:30, Radim Blazek wrote: > > Hi, > > > > QGIS3 crashes when a vector is dragged and drop to PostGIS in browser > > in qgspostgresconn.cpp on > > > > // sharing connection between threads is not safe > > // See https://issues.qgis.org/issues/13141 > > Q_ASSERT( QApplication::instance()->thread() == > > QThread::currentThread() ); > > > > the issue mentioned above is about something different (loading items > > in thread) and it is marked as resolved. > > Works OK here if I remove that assert... can you test and confirm that > it's safe to remove? I don't know the history here... IIRC that comment was mine, and was there because the PostgreSQL connection pooler was not thread safe so using it from different thread might cause hard-to-debug issues. If this is confirmed then the fact you see things working OK is not really reassuring. For some reason I think https://github.com/qgis/QGIS/pull/2690 was also meant to improve that weird shared connection handling by deprecating some methods. --strk; ___ QGIS-Developer mailing list QGIS-Developer@lists.osgeo.org List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [QGIS-Developer] Drag and drop to PostGIS crash
On Tue, May 30, 2017 at 9:40 AM, Sandro Santilli wrote: > On Tue, May 30, 2017 at 04:39:01PM +1000, Nyall Dawson wrote: >> On 30 May 2017 at 16:30, Radim Blazek wrote: >> > Hi, >> > >> > QGIS3 crashes when a vector is dragged and drop to PostGIS in browser >> > in qgspostgresconn.cpp on >> > >> > // sharing connection between threads is not safe >> > // See https://issues.qgis.org/issues/13141 >> > Q_ASSERT( QApplication::instance()->thread() == >> > QThread::currentThread() ); >> > >> > the issue mentioned above is about something different (loading items >> > in thread) and it is marked as resolved. >> >> Works OK here if I remove that assert... can you test and confirm that >> it's safe to remove? I don't know the history here... > > IIRC that comment was mine, and was there because the PostgreSQL > connection pooler was not thread safe so using it from different > thread might cause hard-to-debug issues. If this is confirmed then > the fact you see things working OK is not really reassuring. > > For some reason I think https://github.com/qgis/QGIS/pull/2690 was > also meant to improve that weird shared connection handling by > deprecating some methods. Calling QgsPostgresConn::connectDb with shared=false should be OK, right? Radim ___ QGIS-Developer mailing list QGIS-Developer@lists.osgeo.org List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
[QGIS-Developer] Plugin [1250] AGT - Archaeological Geophysics Toolbox approval notification.
Plugin AGT - Archaeological Geophysics Toolbox approval by pcav. The plugin version "[1250] AGT - Archaeological Geophysics Toolbox 1.1" is now approved Link: http://plugins.qgis.org/plugins/AGT/ ___ QGIS-Developer mailing list QGIS-Developer@lists.osgeo.org List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [QGIS-Developer] Drag and drop to PostGIS crash
On Tue, May 30, 2017 at 09:55:49AM +0200, Radim Blazek wrote: > > Calling QgsPostgresConn::connectDb with shared=false should be OK, right? I guess, given the assertion was only added in the shared=true case.. --strk; ___ QGIS-Developer mailing list QGIS-Developer@lists.osgeo.org List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [QGIS-Developer] [Qgis-developer] Min Qt version
On Thu, May 25, 2017 at 10:53 AM, Nyall Dawson wrote: >> What min version of Qt are you able to compile with? We should update >> INSTALL. >> >> In INSTALL requirements it is also written: Qwt >= 5.0 & (< 6.1 with >> internal QwtPolar) >> but Qwt 6.0 does not compile with Qt >= 5.4: >> http://www.qtcentre.org/archive/index.php/t-63275.html >> Is it still true that Qwt must be < 6.1? I have compiled with 6.1.3 >> (but not tested related functionality). > > I can't help with minimum Qt version (it's either 5.4 or 5.5, but I > don't believe a firm decision has been made), but the minimum Qwt is > 6.1. In this case the INSTALL is incorrect and needs to be updated. I have updated INSTALL to: Qt >= 5.4.0 Qwt >= 6.1 Just for curiosity, question for C++ experts, how this can compile/work: QStringList lineParts = part.split( linePartRx, QString::SkipEmptyParts ); label = lineParts.mid( 5 ).join( ' ' ); if mid() returns QList which has no join()? Radim ___ QGIS-Developer mailing list QGIS-Developer@lists.osgeo.org List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [QGIS-Developer] [Qgis-developer] Min Qt version
QStringList has it [0] ? http://doc.qt.io/qt-5/qstringlist.html#join Le mar. 30 mai 2017 à 10:11, Radim Blazek a écrit : > On Thu, May 25, 2017 at 10:53 AM, Nyall Dawson > wrote: > >> What min version of Qt are you able to compile with? We should update > INSTALL. > >> > >> In INSTALL requirements it is also written: Qwt >= 5.0 & (< 6.1 with > >> internal QwtPolar) > >> but Qwt 6.0 does not compile with Qt >= 5.4: > >> http://www.qtcentre.org/archive/index.php/t-63275.html > >> Is it still true that Qwt must be < 6.1? I have compiled with 6.1.3 > >> (but not tested related functionality). > > > > I can't help with minimum Qt version (it's either 5.4 or 5.5, but I > > don't believe a firm decision has been made), but the minimum Qwt is > > 6.1. In this case the INSTALL is incorrect and needs to be updated. > > I have updated INSTALL to: > Qt >= 5.4.0 > Qwt >= 6.1 > > Just for curiosity, question for C++ experts, how this can compile/work: > QStringList lineParts = part.split( linePartRx, > QString::SkipEmptyParts ); > label = lineParts.mid( 5 ).join( ' ' ); > if mid() returns QList which has no join()? > > Radim > ___ QGIS-Developer mailing list QGIS-Developer@lists.osgeo.org List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [QGIS-Developer] Export layer with measures
On Mon, May 29, 2017 at 11:39 PM, Nyall Dawson >>>
QgsVectorFileWriter::ogrTypeFromWkbType( QgsWkbTypes::Type type )
>>> {
>>> type = QgsWkbTypes::dropM( type );
>>
>> It works without that line, can I remove it or there is any reason?
>
> I suspect that's probably a remnant from GDAL < 2.1. I can't see any
> reason to keep it for the newer gdal versions.
Min required is GDAL 2.0, I used:
+#if GDAL_VERSION_NUM < GDAL_COMPUTE_VERSION(2,1,0)
type = QgsWkbTypes::dropM( type );
+#endif
Radim
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [QGIS-Developer] [Qgis-developer] Min Qt version
Hi Radim On Tue, May 30, 2017 at 4:11 PM, Radim Blazek wrote: > On Thu, May 25, 2017 at 10:53 AM, Nyall Dawson wrote: >>> What min version of Qt are you able to compile with? We should update >>> INSTALL. >>> >>> In INSTALL requirements it is also written: Qwt >= 5.0 & (< 6.1 with >>> internal QwtPolar) >>> but Qwt 6.0 does not compile with Qt >= 5.4: >>> http://www.qtcentre.org/archive/index.php/t-63275.html >>> Is it still true that Qwt must be < 6.1? I have compiled with 6.1.3 >>> (but not tested related functionality). >> >> I can't help with minimum Qt version (it's either 5.4 or 5.5, but I >> don't believe a firm decision has been made), but the minimum Qwt is >> 6.1. In this case the INSTALL is incorrect and needs to be updated. > > I have updated INSTALL to: > Qt >= 5.4.0 > Qwt >= 6.1 > > Just for curiosity, question for C++ experts, how this can compile/work: > QStringList lineParts = part.split( linePartRx, QString::SkipEmptyParts ); > label = lineParts.mid( 5 ).join( ' ' ); > if mid() returns QList which has no join()? QStringList has a constructor taking const QList & as an argument - that is an implicit conversion constructor (it has one argument and it is not declared as "explicit"), so it allows C++ to silently convert QList to QStringList and call QStringList::join(). Cheers Martin ___ QGIS-Developer mailing list QGIS-Developer@lists.osgeo.org List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [QGIS-Developer] 2.18.9 - big thanks to Jürgen for the quick release!
Hi all, +1000 to thank Jürgen for his work. I think QGIS dev community should also find a way not to rely only on one person to wear this burden (if it is really the case). I have no clue if anyone else can help Jürgen ( or if it is necessary , or if Jürgen agree with this, or if it is already the case...), but I think we should be cautious. One dedicated and skillfull person as Jürgen is always the more effective way, but sharing burden and how-tos is also a good thing IMHO. Regards Michaël 2017-05-28 7:20 GMT+02:00 Chris Crook : > Absolutely want to second this comment. This level of commitment is what > makes QGIS great, and an invaluable tools for me in my work > > Thankyou Jürgen > > Chris > > From: QGIS-Developer [qgis-developer-boun...@lists.osgeo.org] On Behalf > Of Nyall Dawson [nyall.daw...@gmail.com] > Sent: 27 May 2017 12:38 > To: qgis-developer; qgis-...@lists.osgeo.org > Subject: [QGIS-Developer] 2.18.9 - big thanks to Jürgen for the quick > release! > > I'd really like to publicly extend my thanks to Jürgen for this prompt > release of 2.18.9, and for the work he's put in to quickly backport > fixes and squash critical bugs leading up to this. > > This makes the second point release in a row where Jürgen has been > required to push out rapid follow up releases, through no fault of his > own! > > Jürgen -- without your hard work as release manager and all the hours > you put in to packaging QGIS releases there's no way we'd have > achieved the success we enjoy today. Many many thanks for all the work > you've put in over the years in this thankless task! > > Nyall > ___ > QGIS-Developer mailing list > QGIS-Developer@lists.osgeo.org > List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer > Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer > > This message contains information, which may be in confidence and may be > subject to legal privilege. If you are not the intended recipient, you must > not peruse, use, disseminate, distribute or copy this message. If you have > received this message in error, please notify us immediately (Phone 0800 > 665 463 or i...@linz.govt.nz) and destroy the original message. LINZ > accepts no responsibility for changes to this email, or for any > attachments, after its transmission from LINZ. Thank You. > ___ > QGIS-Developer mailing list > QGIS-Developer@lists.osgeo.org > List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer > Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer > ___ QGIS-Developer mailing list QGIS-Developer@lists.osgeo.org List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
[QGIS-Developer] Plugin [1245] DRASTIC model approval notification.
Plugin DRASTIC model approval by pcav. The plugin version "[1245] DRASTIC model 0.1 Experimental" is now approved Link: http://plugins.qgis.org/plugins/DRASTIC/ ___ QGIS-Developer mailing list QGIS-Developer@lists.osgeo.org List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
[QGIS-Developer] Plugin [1246] go2mapillary approval notification.
Plugin go2mapillary approval by pcav. The plugin version "[1246] go2mapillary 1.1" is now approved Link: http://plugins.qgis.org/plugins/go2mapillary/ ___ QGIS-Developer mailing list QGIS-Developer@lists.osgeo.org List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [QGIS-Developer] [Qgis-developer] Min Qt version
On Tue, May 30, 2017 at 11:39 AM, Martin Dobias wrote:
>> Just for curiosity, question for C++ experts, how this can compile/work:
>> QStringList lineParts = part.split( linePartRx, QString::SkipEmptyParts
>> );
>> label = lineParts.mid( 5 ).join( ' ' );
>> if mid() returns QList which has no join()?
>
> QStringList has a constructor taking const QList & as an
> argument - that is an implicit conversion constructor (it has one
> argument and it is not declared as "explicit"), so it allows C++ to
> silently convert QList to QStringList and call
> QStringList::join().
Thanks for explanation. I should open my C++ book sometimes.
It is strange that compilation was failing with the same clang++
-std=c++11 with Qt 5.3 which has the same
inline QStringList(const QList &l) : QList(l) { }
Radim
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [QGIS-Developer] Drag and drop to PostGIS crash
On Tue, May 30, 2017 at 10:01 AM, Sandro Santilli wrote: >> Calling QgsPostgresConn::connectDb with shared=false should be OK, right? > > I guess, given the assertion was only added in the shared=true case.. It is called from many places where it is difficult to pass shared param. I have forced non shared in QgsPostgresConn::connectDb if it is not main thread. DD works within the browser now but not for layer with measures. DD from layer tree to postgres/browser imports the layer (without measures) but: - the layer is removed from layer tree - intended? - QGIS crashes sometimes One traceback below, it crashed when DD failed. I think that the problem is that it is trying to show an error message which can only be done on main thread? The code which is run from QgsTaskManager should never interact with GUI? Radim #0 0x7f844620f3c0 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /home/radim/Qt/5.8/gcc_64/lib/libQt5Core.so.5 (gdb) bt #0 0x7f844620f3c0 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /home/radim/Qt/5.8/gcc_64/lib/libQt5Core.so.5 #1 0x7f844625ea1e in QTimerInfoList::activateTimers() () from /home/radim/Qt/5.8/gcc_64/lib/libQt5Core.so.5 #2 0x7f844625f219 in ?? () from /home/radim/Qt/5.8/gcc_64/lib/libQt5Core.so.5 #3 0x7f843e5c9c5d in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f843e5c9f48 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f843e5c9ffc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #6 0x7f844625fcbf in QEventDispatcherGlib::processEvents(QFlags) () from /home/radim/Qt/5.8/gcc_64/lib/libQt5Core.so.5 #7 0x7f844620d9ca in QEventLoop::exec(QFlags) () from /home/radim/Qt/5.8/gcc_64/lib/libQt5Core.so.5 #8 0x7f844a1e8a07 in QDialog::exec() () from /home/radim/Qt/5.8/gcc_64/lib/libQt5Widgets.so.5 #9 0x7f844d8e9c50 in QgsMessageViewer::showMessage (this=0x3e77be0, blocking=true) at /home/radim/devel/qgis/src/gui/qgsmessageviewer.cpp:74 #10 0x7f844d8e9cbc in non-virtual thunk to QgsMessageViewer::showMessage(bool) () at /home/radim/devel/qgis/src/gui/qgsmessageviewer.cpp:81 #11 0x7f8419ec65d0 in QgsPGConnectionItem::handleDrop(QMimeData const*, QString const&)::$_5::operator()(int, QString const&) const (this=0x2c65230, error=2, errorMessage=...) at /home/radim/devel/qgis/src/providers/postgres/qgspostgresdataitems.cpp:241 #12 0x7f8419ec64ae in QtPrivate::FunctorCall, QtPrivate::List, void, QgsPGConnectionItem::handleDrop(QMimeData const*, QString const&)::$_5>::call(QgsPGConnectionItem::handleDrop(QMimeData const*, QString const&)::$_5&, void**) (f=..., arg=0x7ffcf04e7130) at /home/radim/Qt/5.8/gcc_64/include/QtCore/qobjectdefs_impl.h:137 #13 0x7f8419ec6471 in QtPrivate::Functor::call, void>(QgsPGConnectionItem::handleDrop(QMimeData const*, QString const&)::$_5&, void*, void**) (f=..., arg=0x7ffcf04e7130) at /home/radim/Qt/5.8/gcc_64/include/QtCore/qobjectdefs_impl.h:194 #14 0x7f8419ec6413 in QtPrivate::QFunctorSlotObject, void>::impl(int, QtPrivate::QSlotObjectBase*, QObject*, void**, bool*) (which=1, this_=0x2c65220, r=0x3cfc3e0, a=0x7ffcf04e7130, ret=0x0) at /home/radim/Qt/5.8/gcc_64/include/QtCore/qobject_impl.h:168 #15 0x7f8446238746 in QMetaObject::activate(QObject*, int, int, void**) () from /home/radim/Qt/5.8/gcc_64/lib/libQt5Core.so.5 #16 0x7f844bf0347f in QgsVectorLayerExporterTask::errorOccurred (this=0x43be440, _t1=2, _t2=...) at /home/radim/devel/qgis-build/src/core/moc_qgsvectorlayerexporter.cpp:147 #17 0x7f844bbb9b80 in QgsVectorLayerExporterTask::finished (this=0x43be440, result=false) at /home/radim/devel/qgis/src/core/qgsvectorlayerexporter.cpp:508 #18 0x7f844bad71e7 in QgsTaskManager::taskStatusChanged (this=0x23c7bc0, status=4) at /home/radim/devel/qgis/src/core/qgstaskmanager.cpp:653 ___ QGIS-Developer mailing list QGIS-Developer@lists.osgeo.org List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
[QGIS-Developer] Building QGIS 2.18 on OSX
Hi everybody, This is my first post here and I hope there's not already a post related to this, even thought I searched through the list a little. I have been trying to build QGIS 2.18 for about 3 weeks following a few step by steps I found but none of them gave me success. I'm on OSX 10.12. I first followed the official step by step from QGIS, and then, other ones using homebrew, but wasn't able to finish the build for the intended version. I do believe I have a polluted OS and libraries, but I invested around 6 hours cleaning it and my environments to try it all again, and still, no success. Mainly, I believe my issue is regarding Qt4, which is already deprecated and I'm not able to install it properly. I already tried the .dmg from official's qt website (which crashes) and some cartr and osgeo formulaes from homebrew and still no success. Somewhere along the configuration and build process I get errors regarding Qt4 or some of their python bindings libraries and even thought I did manage to fix some of them, the build was never able to finish. Do you guys believe it is still possible to build non-master versions of QGIS on OSX, and if so, what would be some kind of different approach in order to be able to achieve it? Kind regards, Helton Costa ___ QGIS-Developer mailing list QGIS-Developer@lists.osgeo.org List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [QGIS-Developer] Drag and drop to PostGIS crash
On 31 May 2017 at 03:07, Radim Blazek wrote: > DD works within the browser now but not for layer with measures. I guess this has never been implemented. Looking at QgsPostgresConn::postgisWkbType, it's only got support for a very limited range of WKB types (no curves, no m values, won't handle z types (only 25d types) ). I think it should work ok after that function is fixed. > DD from layer tree to postgres/browser imports the layer (without measures) > but: > - the layer is removed from layer tree - intended? Definitely not - I hit this too a week or so ago, and it's far from ideal! QgsDockBrowserTreeView::dragEnterEvent/dragMoveEvent/dropEvent has code which is supposed to force a copy action when dragging from the layer tree, but something's broken there. Any ideas Martin? > - QGIS crashes sometimes > > One traceback below, it crashed when DD failed. I think that the > problem is that it is trying to show an error message which can only > be done on main thread? > The code which is run from QgsTaskManager should never interact with GUI? That shouldn't be the case (unless there's a bug somewhere). It's true that tasks should never interact with the GUI in their run() implementation, but QgsTask::finished should only ever be called from the main thread and it should be safe to do GUI operations there. From your crash below it seems like it's crashing after QgsVectorLayerExporterTask::errorOccurred is emitted - but that's only ever done from QgsVectorLayerExporterTask::finished . Could you try putting a temporary assert in QgsVectorLayerExporterTask::finished to ensure that it's working as designed and being called from the main thread? Thanks! Nyall > > #0 0x7f844620f3c0 in QCoreApplication::notifyInternal2(QObject*, > QEvent*) () from /home/radim/Qt/5.8/gcc_64/lib/libQt5Core.so.5 > (gdb) bt > #0 0x7f844620f3c0 in QCoreApplication::notifyInternal2(QObject*, > QEvent*) () from /home/radim/Qt/5.8/gcc_64/lib/libQt5Core.so.5 > #1 0x7f844625ea1e in QTimerInfoList::activateTimers() () from > /home/radim/Qt/5.8/gcc_64/lib/libQt5Core.so.5 > #2 0x7f844625f219 in ?? () from > /home/radim/Qt/5.8/gcc_64/lib/libQt5Core.so.5 > #3 0x7f843e5c9c5d in g_main_context_dispatch () from > /lib/x86_64-linux-gnu/libglib-2.0.so.0 > #4 0x7f843e5c9f48 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 > #5 0x7f843e5c9ffc in g_main_context_iteration () from > /lib/x86_64-linux-gnu/libglib-2.0.so.0 > #6 0x7f844625fcbf in > QEventDispatcherGlib::processEvents(QFlags) > () >from /home/radim/Qt/5.8/gcc_64/lib/libQt5Core.so.5 > #7 0x7f844620d9ca in > QEventLoop::exec(QFlags) () from > /home/radim/Qt/5.8/gcc_64/lib/libQt5Core.so.5 > #8 0x7f844a1e8a07 in QDialog::exec() () from > /home/radim/Qt/5.8/gcc_64/lib/libQt5Widgets.so.5 > #9 0x7f844d8e9c50 in QgsMessageViewer::showMessage > (this=0x3e77be0, blocking=true) > at /home/radim/devel/qgis/src/gui/qgsmessageviewer.cpp:74 > #10 0x7f844d8e9cbc in non-virtual thunk to > QgsMessageViewer::showMessage(bool) () > at /home/radim/devel/qgis/src/gui/qgsmessageviewer.cpp:81 > #11 0x7f8419ec65d0 in QgsPGConnectionItem::handleDrop(QMimeData > const*, QString const&)::$_5::operator()(int, QString const&) const > (this=0x2c65230, error=2, errorMessage=...) at > /home/radim/devel/qgis/src/providers/postgres/qgspostgresdataitems.cpp:241 > #12 0x7f8419ec64ae in > QtPrivate::FunctorCall, > QtPrivate::List, void, > QgsPGConnectionItem::handleDrop(QMimeData const*, QString > const&)::$_5>::call(QgsPGConnectionItem::handleDrop(QMimeData const*, > QString const&)::$_5&, void**) (f=..., arg=0x7ffcf04e7130) at > /home/radim/Qt/5.8/gcc_64/include/QtCore/qobjectdefs_impl.h:137 > #13 0x7f8419ec6471 in > QtPrivate::Functor QString const&)::$_5, 2>::call, > void>(QgsPGConnectionItem::handleDrop(QMimeData const*, QString > const&)::$_5&, void*, void**) (f=..., > arg=0x7ffcf04e7130) at > /home/radim/Qt/5.8/gcc_64/include/QtCore/qobjectdefs_impl.h:194 > #14 0x7f8419ec6413 in > QtPrivate::QFunctorSlotObject const*, QString const&)::$_5, 2, QtPrivate::List, > void>::impl(int, QtPrivate::QSlotObjectBase*, QObject*, void**, bool*) > (which=1, this_=0x2c65220, > r=0x3cfc3e0, a=0x7ffcf04e7130, ret=0x0) at > /home/radim/Qt/5.8/gcc_64/include/QtCore/qobject_impl.h:168 > #15 0x7f8446238746 in QMetaObject::activate(QObject*, int, int, > void**) () from /home/radim/Qt/5.8/gcc_64/lib/libQt5Core.so.5 > #16 0x7f844bf0347f in QgsVectorLayerExporterTask::errorOccurred > (this=0x43be440, _t1=2, _t2=...) > at > /home/radim/devel/qgis-build/src/core/moc_qgsvectorlayerexporter.cpp:147 > #17 0x7f844bbb9b80 in QgsVectorLayerExporterTask::finished > (this=0x43be440, result=false) > at /home/radim/devel/qgis/src/core/qgsvectorlayerexporter.cpp:508 > #18 0x7f844bad71e7 in QgsTaskManager::taskStatusChanged > (this=0x23c7bc0, status=4) > at /home/radim/devel/qgis/src/core/qgstaskmanager.cpp:653 > __
Re: [QGIS-Developer] [Qgis-user] Split features tool behavior
Hey Andreas, I haven't experienced the invalid geometry as you describe, but I did find that my QGIS install had some issues. I have upgraded to 2.18.9 on Win10. If you have a sample of your data available, I would be happy to try to corroborate. James Sent from my iPhone > On May 29, 2017, at 06:16, Andreas Wicht wrote: > >> On 28 May 2017 at 14:43, James Wood wrote: >> On the digitizing toolbar, try "Split Parts" instead of "Split Features" on >> multipart polygons. > > Thank you for the hint, James. Somehow I always thought that this > function is only suitable for separating an existing part from a > feature (never used it though). > Yet, if you cut a polygon with the "Split Parts" tool, the output will > be an invalid geometry (I observed self-intersections). This as well > can not be the intended behavior. I could observe those errors in > simple scratch layers as well as in PostGIS layers. > > Has anybody else experienced this behavior? ___ QGIS-Developer mailing list QGIS-Developer@lists.osgeo.org List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
[QGIS-Developer] Plugin [1035] Lat Lon Tools approval notification.
Plugin Lat Lon Tools approval by pcav. The plugin version "[1035] Lat Lon Tools 0.9.1" is now approved Link: http://plugins.qgis.org/plugins/latlontools/ ___ QGIS-Developer mailing list QGIS-Developer@lists.osgeo.org List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
[QGIS-Developer] Plugin [1232] OSM Tools approval notification.
Plugin OSM Tools approval by pcav. The plugin version "[1232] OSM Tools 0.3" is now approved Link: http://plugins.qgis.org/plugins/OSMtools/ ___ QGIS-Developer mailing list QGIS-Developer@lists.osgeo.org List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
