Andreas,
I've dealt with two sources of such warnings today, one which caused one
warning on every canvas redraw (the north arrow decoration), the other
caused many warnings upon (re-)drawing the content of the overview panel.
One of the few remaining sources of warnings is with the WMS/XYZ
I share those concerns too.
The integration with parts of QGIS is sub-optimal. For e.g., the added (and
always visible) menu bar in the attribute form. I'm not sure is should be
there at all, and if so, certainly not when the layer's edit mode is OFF.
IMHO, I'd disable/remove less-than-optimal
+1 to set a release date for the last week of January. That'll give us 2
weeks of freeze period (assuming the vote turns out not to extend the soft
freeze) which can be used to focus on fixes only. The soft freeze period
saw a nice set of fixes too, which was nice.
On Tue, Jan 2, 2018 at 4:48
I'm -1 to label 3.0 a "beta" product. I'd argue that in many respects, 3.0
is a more stable and reliable product than 2.18.
On Wed, Jan 3, 2018 at 10:14 AM, Bernd Vogelgesang wrote:
> Am 02.01.2018, 23:39 Uhr, schrieb Nyall Dawson :
>
>
>
>>> I
That is, have your plugin set that setting to false upon loading. I wasn't
suggesting to switch the overall default to false.
On Sat, Sep 8, 2018, 16:08 Mathieu Pellerin wrote:
> Chris,
>
> There is:
>
> QgsSettings().value( QStringLiteral( "askToSaveMemoryLayers" ),
Chris,
There is:
QgsSettings().value( QStringLiteral( "askToSaveMemoryLayers" ), true,
QgsSettings::App )
Switch that to false, that'll disable the warning.
I was wondering how long it'd take for the memory layer saver plugin to
switch that off ;)
On Sat, Sep 8, 2018, 13:15 Chris Crook
Nyall, thanks for having raised this (and fixed that horrific regression).
Jürgen, thanks for that extra flexibility, much appreciated.
On Thu, Nov 1, 2018, 8:08 PM Jürgen E. Fischer wrote:
> Hi,
>
> On Thu, 01. Nov 2018 at 21:47:06 +1000, Nyall Dawson wrote:
> > > I meant 2018-11-02.
That's rather unfortunate, but most probably needed. The issue raised,
20262, affects WMS(T), XYZ, WFS, etc. layers.
On top of - and very much due to - the gravity of the bug itself, 3.4 is
flagged as LTR, and it'd be most appropriate to insure that people jumping
onto this new LTR aren't left
Absolutely. It was the right move to not add that as part of backported
browser panel fixes for emergency 3.4.1, but it should ultimately be in the
LTR to fix a feature gone missing regression.
On Tue, Nov 6, 2018, 6:54 AM Nyall Dawson wrote:
> Hi list,
>
> I'm looking for thoughts on whether
Can these failures be reproduced locally if one repeatedly tests those
cases?
On Mon, Sep 3, 2018, 07:02 Nyall Dawson wrote:
> On Sat, 1 Sep 2018 at 20:37, Richard Duivenvoorde
> wrote:
>
> > And myself I also have the feeling that WFS is less stable
>
> This is my experience too, which is why
Jumping in the discussion to offer thoughts on the bigger picture here:
while we have a few dozen regressions filed against 3.4 LTR, it's also true
that 3.4 LTR has _countless_ fixes and refinements - not referring to new
features here - when compared to 2.18 which adds a big amount of positive
in
Regarding on-screen navigation, it'd be good to think of an implementation
that would work for both 2D as well as 3D map canvases when conceptualizing
the way ahead (I'm not suggesting you implement this as part of this GSoC
plan, just seeding the idea as it might shape way you move forward). It'd
I would really like to understand (i.e. get an explanation) from the OSM
admins as to why a user agent that explicitly identifies itself as QGIS
like we have now is not enough for them before moving forward.
Being a web admin/developer myself, I can hardly find a reason why that's
not enough.
Unless the standalone install executable file has been re-uploaded with the
missing EXIV2.DLL dependency, I can confirm this is an issue here on
windows 10 using the 64-bit standalone installer.
Math
On Mon, Feb 25, 2019 at 1:41 PM Lene Fischer wrote:
> Made a re-re installation again this
Thanks for the reminder Nyall, I'd totally forgotten about this.
On Sat, Feb 23, 2019, 8:24 AM Nyall Dawson wrote:
> Hi all,
>
> Just a heads up: now that 3.4 is officially the LTR, I've enabled
> github branch protection on the branch. This means all commits to the
> branch must now:
> 1. Go
For the record, this toolbar is already hidden by default.
Some people like the one-button unified dialog, some prefer the individual
provider buttons. I don't see why we'd want / what we'd gain to remove this
hidden-by-default toolbar.
On Sun, Mar 17, 2019, 7:14 PM Richard Duivenvoorde
wrote:
Could we take it a step at a time and proceed with adding the changelog bit
to the plugin.xml file first? The fixed UX will probably provide additional
motivation for authors.
On Mon, Mar 11, 2019, 6:56 PM Paolo Cavallini wrote:
> this would also be nice for users.
> thanks.
>
> On 11/03/19
Greetings,
While applying a couple of commits to QGIS' plugin manager, I would like to
fix a long-standing UX issue with it, namely that plugins that show a newer
version available do _not_ show the latest changelog but rather the
changelog of the currently installed plugin version.
It'd much
;
>
>
> On Sat, Mar 9, 2019 at 11:38 AM Mathieu Pellerin
> wrote:
>
>> Greetings,
>>
>> While applying a couple of commits to QGIS' plugin manager, I would like
>> to fix a long-standing UX issue with it, namely that plugins that show a
>> new
Nice progress.
I feel it'd be really important to figure out a way to creating some
floating controls here, the current approach eats so much space it'll
likely be unusable with docked 3d maps.
On Sat, Jun 8, 2019, 18:40 Tim Sutton wrote:
> Hi Ismail
>
>
> Looking great! I was wondering:
For the record, sending unencrypted data over a local network isn't safe as
soon as WIFI is part of said local network.
On Mon, Jun 17, 2019, 17:02 Martin Dobias wrote:
> Hi Matthias
>
> On Mon, Jun 17, 2019 at 8:48 AM Matthias Kuhn wrote:
> >
> > The documentation currently promises "massive
This is such an instructive reply it should be added to stackexchange
straight away! :)
On Mon, May 20, 2019, 07:37 Nyall Dawson wrote:
> On Mon, 20 May 2019 at 01:21, Anita Graser wrote:
> >
> > Hi,
> >
> > I'd like to add an example of an aggregate expression to my recent
> PyQGIS 101
FYI, for the last ~24 hours, travis builds fail to submit test results to
our cdash instance (https://dash.orfeo-toolbox.org/index.php?project=QGIS).
The website itself appears to be down most of the time too.
Known issue?
___
QGIS-Developer mailing
Nice screencast. Are billboards able to handle alpha/opacity channel for a
given raster?
On Mon, Jul 15, 2019, 20:10 Ismail Sunni wrote:
> Hi Tim,
>
> Hehe, yeah, I am the one who missed it. I put it in my billboard
> repository now:
>
Matthias, you're raising a good point on the 2.0 vs 3.4 (I'd argue 2.18 vs
3.4 too). Sometimes we tend to get so "passionate" about specific bugs that
impact our own workflows that we end up not seeing the forest for the
trees. 3.4 LTS is overall a much, much more solid product than 2.18 was and
Calvin,
A fair amount of crashers and stability issues have been resolved in 3.8.1,
which'll be out in a few days. Give that a try.
If you still find it unstable, actionable information describing crashes
and issues are needed (since you're a plugin dev, I'm sure that's familiar
to you ;) ). If
While discussing this further with Nathan, disabling the crash reporter
might not be the right solution as it'd most likely bring the OS crash
dialog anyways.
We'd need for the crash reporter to detect specific traces and silently
fail when it detects a useless / harmless trace.
There's also the
Jurgen, would we be able to include the debug symbols for the build on the
> normal installers for once release cycle while this is still an issue? That
> would be super handy to catch this and other issues that come up.
>
> On Thu, Jul 18, 2019 at 4:44 PM Mathieu Pellerin
> wr
Just checked, 5.12.5 was released a few days ago, nice!
https://www.qt.io/blog/qt-5.12.5-released
On Thu, Sep 26, 2019, 07:39 Mathieu Pellerin wrote:
> FYI, 5.12.4 (and 5.13.1 I believe) has an issue that breaks CSS-based
> themes (night mapping, blend of gray).
>
> A fix has be
FYI, 5.12.4 (and 5.13.1 I believe) has an issue that breaks CSS-based
themes (night mapping, blend of gray).
A fix has been committed and will be available in 5.12.5.
On Thu, Sep 26, 2019, 06:31 Nyall Dawson wrote:
> Hi Jürgen,
>
> Is there any plans on the horizon for updating the Qt build in
Question regarding download count: if I merely upgrade a plugin, does the
download to upgrade the plugin counts as an overall download?
We could have a refined popularity count if we'd find a way to come up with
an active users count (which shouldn't be that difficult to implement, info
could be
Add to what was said (which I don't disagree with per say). I think it's
important to note that this GDAL3/PROJ6 transition was always going to be
rocky (whether we applied it to 3.4 LTR or delayed it of 4 months when 3.10
LTR will replace 3.4.
One reason being most core developers are on linux
The consorted efforts this past week across three open source projects (!)
to fix serious regressions following one of the first "mainstream" exposure
of next gen gdal3/proj6 codebase through QGIS has been heartening to
witness. Congrats to all involved!
Do we have a new release date set for
n this would be a good opportunity to do an
> ad-hoc investment into Jürgen (given that he has some of his precious time
> left to actually work on this and that he does not completely disagree with
> me).
>
> Best regards
>
> Matthias
> On 11/28/19 1:47 AM, Nathan Woodrow wr
+1 to end 3.4 cycle a few months early too.
On Thu, Nov 28, 2019, 05:57 Nathan Woodrow wrote:
> +1 on dropping support early as the risk is large on breaking the users
> experience with a LTR
>
> On Thu., 28 Nov. 2019, 8:55 am Even Rouault,
> wrote:
>
>> > I think the issues are deeper then
Ouch! ;) yes, 2020.
On Thu, Nov 28, 2019, 16:57 Jürgen E. Fischer wrote:
> Hi Mathieu,
>
> On Thu, 28. Nov 2019 at 15:36:39 +0700, Mathieu Pellerin wrote:
> > For the record, according to schedule, 3.4 reaches its end of life on
> > February 21st, 2010.
>
> 2020?
&
I'm also -0 to branch off early, as I think it's a missed opportunity to
get core devs to stick to soon-to-be-released 3.10 for as long as possible
(and therefore oh-so slightly increase the chance of core devs stumbling on
a bug he/she can fix prior to release :) ) .
On Mon, Oct 14, 2019 at 4:02
Having helped out chasing down some of these CRS and transformation issues
under GDAL3/PROJ6, I too feel *very* uncomfortable shipping the next QGIS
point release with anything lesser than GDAL3 and PROJ6 master as of
yesterday.
To be clear, QGIS had plenty to fix itself, and that’s been taken
Great news, best way to open 2020 :)
On Thu, Dec 19, 2019, 14:14 Kristian Evers wrote:
>
>
> On 19 Dec 2019, at 03:37, Mathieu Pellerin wrote:
>
> Having helped out chasing down some of these CRS and transformation issues
> under GDAL3/PROJ6, I too feel *very* uncomfortable
FYI, the qgis-dev package is currently broken, reporting it can't start
because proj_7_0.dll is missing. I think some dll referencing needs
updating (proj recently renamed its forthcoming branch to 6.3, and I can
see a proj_6_3.dll floating around).
___
Fantastic, thank you.
On Fri, Jan 24, 2020, 15:48 Anita Graser wrote:
> I can do it.
>
> Regards,
> Anita
>
> On Fri, Jan 24, 2020 at 12:15 AM Mathieu Pellerin
> wrote:
>
>> Jürgen, thanks for the successful re-release of 3.10.2.
>>
>> Paolo, Anita, w
gt;>
>>> Hi all,
>>>
>>> Thanks Mathieu. Should it be 3.10.2 or 3.10.3? Asking because those who
>>> have already downloaded the broken 3.10.2 may not think to update.
>>>
>>> Regards,
>>> Harrissou
>>>
>>> Le me
Here's a nice Sunday news: Ubuntu 20.04 (ETA end of April) will ship with
gdal 3 (at the moment 3.0.3, hopefully will be 3.0.4 by release day to fix
a nasty bug) and proj 6.3.
This can likely increase the number of QGIS core devs using this next gen
pair of libraries, which would undeniably help
Bas,
Thanks for the update, and big thanks for the efforts you've put into this
over the years.
I've updated my system too, no big regression, nice to live in the future
:)
On Mon, Feb 3, 2020, 19:17 Sebastiaan Couwenberg wrote:
> On 2/2/20 9:52 AM, Mathieu Pellerin wrote:
> > Here
It's wise of you not to have your department jump on a .0 release. All
known (ie reported through filing) protection issues have been resolved.
That said, you should also take on the task of stress testing the latest
version against your department's workflows and datasets. Unreported issues
are
Jürgen, thanks for the successful re-release of 3.10.2.
Paolo, Anita, who is in a position to publish the drafted post on the blog?
On Thu, Jan 23, 2020, 10:59 Mathieu Pellerin wrote:
> +1 to that plan. We're 33% done already since the blocking PR has been
> merged.
>
> On Wed,
Nice, Ubuntu 20.04 (LTR) shipping with gdal 3.0.4 and proj 6.3.1 is really
sweet.
Any plan to update QGIS to 3.10? 3.4 reaches it's end of life in the coming
few days.
Math
On Tue, Feb 18, 2020 at 4:57 PM Bas Couwenberg wrote:
> On 2020-02-18 10:45, Denis Rouzaud wrote:
> > Is this correct
Bas Couwenberg wrote:
> On 2020-02-18 11:00, Mathieu Pellerin wrote:
> > Any plan to update QGIS to 3.10? 3.4 reaches it's end of life in the
> > coming
> > few days.
>
> Yes, but this will probably be too late for focal, as recently discussed
> on th
are very happy that QGIS 3.10 is now in shape to replace 3.4
> as LTR in a month time.
>
> Bests
> Matthias
>
>
> On 1/22/20 10:58 AM, Mathieu Pellerin wrote:
>
> Paolo, here's the draft blog post:
>
> *Public Service Announcement: Update to the latest point rele
.
Happy mapping!
[1] https://north-road.com/2019/09/03/qgis-3-10-loves-geopdf/
[2] https://gdalbarn.com/
On Tue, Jan 21, 2020 at 9:56 AM Paolo Cavallini
wrote:
> Fully agreed. Mathieu, would you like to write it?
> Thanks.
>
> On 21 January 2020 06:39:08 GMT+04:00, Mathieu Pellerin
d the broken 3.10.2 may not think to update.
>
> Regards,
> Harrissou
>
> Le mer. 22 janv. 2020 à 11:05, Mathieu Pellerin a
> écrit :
>
>> Matthias,
>>
>> Good idea.
>>
>> Math
>>
>> On Wed, Jan 22, 2020 at 5:02 PM Matthias
Sure, I can draft something by the end of the day.
On Tue, Jan 21, 2020 at 9:56 AM Paolo Cavallini
wrote:
> Fully agreed. Mathieu, would you like to write it?
> Thanks.
>
> On 21 January 2020 06:39:08 GMT+04:00, Mathieu Pellerin <
> nirvn.a...@gmail.com> wrote:
>>
+100 on all that's been said here.
Also, once 3.10.2 is updated to include the updated packages &
above-referred fix, I'd suggest writing a QGIS.org blog post to inform
users of the worthiness of updating to 3.10.2(.2) *ASAP*, and expand a bit
on why 3.10.0/.1 were such rough releases. We can
+1
If in doing so we could unlock resampling for reprojected rasters, woupidou.
On Thu, Apr 16, 2020, 04:46 Martin Dobias wrote:
> Hi all
>
> With the recent addition of contour renderer of rasters I have
> realized there are artifacts coming to the renderer from the earlier
> stages (the
Denis,
Thanks for all the work improving and fixing this.
Math
On Tue, Aug 25, 2020 at 3:12 PM Denis Rouzaud
wrote:
> Hi,
>
> Sorry, I am somehow responsible for the failure of the recent Docker
> images on master (release branches were apparently not affected).
>
> The images were apparently
What a sad milestone.
On Tue, Jan 12, 2021, 21:57 Tim Sutton wrote:
> Hi All
>
> In case you missed it, it seem the hammer has dropped on the Qt closing
> off their LTS versions now:
>
> https://lists.qt-project.org/pipermail/development/2021-January/040798.html
>
>
>
> Regards
>
> Tim
>
> --
>
a formal request seeking permission from OSMF to go
ahead and merge these features. Would it be possible for you, as chair of
the QGIS.org association, to send an email to the OSMF/Nominatim folks on
this?
Best,
Mathieu Pellerin
[1] https://github.com/qgis/QGIS/pull/40669
Andreas, it should be fixed as of this commit (
https://github.com/qgis/QGIS/commit/c4306e18e85145c43331fc871bfb2691dcd55505)
merged earlier today.
On Thu, Nov 12, 2020 at 4:09 PM Andreas Neumann wrote:
> This is self-compiled, on Ubuntu-Linux 18.04 (Kubuntu).
>
> Thanks,
>
> Andreas
>
> On
The fix was committed hours ago :)
On Thu, Nov 12, 2020 at 4:23 PM Andreas Neumann wrote:
> Hi,
>
> Thank you Jürgen and Mathieu for your replies!
>
> Hm - but my build is from "yesterday". and the issues you mention had been
> committed about 2 weeks ago?
>
> Anyway - I am currently
Woupidou! Super excited about this.
On Tue, May 18, 2021, 4:50 PM Martin Dobias wrote:
> Good news everyone,
>
> this year we will have Francesco Bursi working on his summer of code
> project to introduce on-the-fly raster calculator to QGIS! Please join me
> in welcoming him to our amazing
Add the following to the list of serious issue:
- raster URIs using /vsi{zip,curl,etc.}/ won't load anymore:
https://github.com/qgis/QGIS/pull/41888 (fix PR open)
+1 to have an early .1 release.
On Sat, Feb 27, 2021 at 2:15 PM Nyall Dawson wrote:
> So. 3.18.0 is unfortunately proving to
Big interest on my side too (and I'm sure countless more).
I always thought ESA's SNAP had a winning formula with their virtual raster
bands, glad we can make any move in that direction.
Math
On Tue, Apr 13, 2021, 20:57 Matthias Kuhn wrote:
> Hi Francesco,
>
> This is a great initiative,
-1 on non secure feed, opens the door wide open for injection attacks.
It would be nice to have some form of automated reminder so we avoid these
unfortunate lapses as much as possible though :)
On Wed, Aug 11, 2021 at 5:25 PM Nyall Dawson wrote:
> Hi all,
>
> Can someone renew the certificate
If packaging a brand new release is "faster" and "simpler" than updating
our website, there's something to improve there ;-P
We should have a clear procedure to allow for designated person(s) to be
able to swiftly revert a release on the website (manual edits if need be).
On Tue, Nov 16, 2021 at
Big supportive +1 on looking back at what happened during this last month
with the LTR, draw some lessons and take remedial actions.
Most urgently: we _absolutely_ need to stop advertising 3.16.13 LTR on the
website and fallback to 3.16.11 for now; can someone with access to the
website do that
Right, we still need to kill the MSI installer, which is the one people
will hit first.
On Tue, Nov 16, 2021 at 2:30 PM Andrea Giudiceandrea
wrote:
> Il 16/11/2021 08:27, Mathieu Pellerin ha scritto:
> > If packaging a brand new release is "faster" and "simpler"
Whether we release a new point release or not, we should definitely release
a public service announcement on our social media accounts.
On Fri, Nov 5, 2021, 07:25 Jürgen E. Fischer wrote:
> Hi Nyall,
>
> On Fri, 05. Nov 2021 at 08:28:33 +1000, Nyall Dawson wrote:
> > > We also then need to push
caring about the
> context of the string, which ends up in very strange and nonsense.
>
> Thanks for your opinions
>
> Alex
>
> Mathieu Pellerin escreveu no dia quinta,
> 24/03/2022 à(s) 11:39:
>
>> Could we not have some means to attach a quality value to each language
&g
lled
> into code base. The issue here is that pt_PT has issues with the quality of
> the translated strings.
>
> Regards,
> Harrissou
>
> Le jeu. 24 mars 2022 à 12:39, Mathieu Pellerin via QGIS-Developer <
> qgis-developer@lists.osgeo.org> a écrit :
>
>> Could we no
Could we not have some means to attach a quality value to each language (eg
at the very least % translated), and only force English on poorly
translated languages? I feel forcing English by default would be a
disservice to the part of the community that spends hours to translate QGIS.
On Thu, Mar
Oh, by the way, we'll need to adapt Find{Qca,QWT,etc}.cmake to behave
nicely on systems where both qt5 and qt6 libraries are installed. Atm it'll
randomly pick one or the other.
We can make use of BUILD_WITH_QT6 there.
On Sat, Aug 20, 2022, 15:22 Mathieu Pellerin wrote:
> Richard,
>
Richard,
FYI, I've been able to compile QGIS against Qt6 (6.2.4) on Ubuntu 22.04.
Few notes:
- We're lucky, Ubuntu 22.04 has a Qt6 keychain package, you should use this
one, that reduces the nb of libs to compile to 3
- As Matthias suggested, I'd install the libraries
- The QCA_INCLUDE_DIR has to
Same here, I'd appreciate a day
On Sun, Feb 25, 2024, 03:24 Nyall Dawson via QGIS-Developer <
qgis-developer@lists.osgeo.org> wrote:
>
>
> On Sat, 24 Feb 2024, 12:41 am Richard Duivenvoorde via QGIS-Developer, <
> qgis-developer@lists.osgeo.org> wrote:
>
>> Hi Devs,
>>
>> As release 3.36
201 - 273 of 273 matches
Mail list logo