Andiamo dritti al punto È ufficiale, QField per QGIS 1.0 è stato rilasciato! Scaricalo subito dal Playstore (qfield.org/get) o da GitHub Siamo incredibilmente soddisfatti e orgogliosi di aver appena rilasciato un tale gioiello e siamo convinti che, grazie a tutte le sue caratteristiche e a scelte progettuali consapevoli, QField renderà Read more
Do you want to win a QField jump-start package worth 550€? We are launching the #MyQField challenge. Follow us on Twitter and show us how you use @QFieldForQGIS by tagging your tweets with #MyQField and #dataisoutside. The tweet with most likes and retweets by 24.4.19 wins the training! Rules You Read more
We are really happy to announce the fifth and (hopefully) last 1.0 release candidate in QField’s history! This means that QField 1.0 is closer than ever. Get it while it’s hot on the Playstore (https://qfield.org/get) or on GitHub Thanks to all the feedback by the fantastic community we were able Read more
We are really happy to announce the release a new great milestone in QField’s history, QField 1.0 Release Candidate 3! (Yes, you might have got a glimpse of the broken RC2 if you where very attentive) Thanks to the great feedback we received since releasing RC1 we were able to Read more
It was a long and winding road but we are very excited to announce the General availability of QField 1.0 Release Candidate 1.
We ask you to help us test as much as possible this Release Candidate so that we can iron out as many bugs as possible before the final release of QField 1.0.
It was a long and winding road but we are very excited to announce the General availability of QField 1.0 Release Candidate 1.
We ask you to help us test as much as possible this Release Candidate so that we can iron out as many bugs as possible before the final release of QField 1.0.
While porting a plugin to QGIS3 I decided to also move all it’s threading infrastructure to QgsTasks. Here three possible variants to implement this.the first uses the static method QgsTask.fromFunction and is simpler to use. A great quick solution. If you want need control you can look at the second Read more
The Release of QGIS 3.0 was a great success and with the first LTR (3.4) scheduled for release this fall, it is now the perfect time to port your plugins to the new API. QGIS 3.0 is the first major release since September 2013 when QGIS 2.0 was released. During Read more
Lately I’ve been spending time porting a bigger plugin from QGIS 2.8 to 3 while maintaining 2.8 compatibility. You can find it at https://github.com/opengisch/qgis2compat/ and https://plugins.qgis.org/plugins/qgis2compat/ One code to rule them all. My target was to have to edit the source code as little as possible to simulate a lazy Read more
Just for the sake of documenting things, when running qgis 2to3 on a plugin I encountered a tricky situation regarding signals. MYQGISDIR/scripts/2to3 -f signals -w my/plugin/path The original code: extra_arg = “my test argument” QObject.connect( action, SIGNAL( “triggered()”), lambda extra_arg=my_arg: show_extra_arg(extra_arg)) def do_load_project(extra_arg): print extra_arg # “my test argument” The Read more