QGIS 3.0 seems to be a good moment/opportunity to terminate ftools and
replace the menu items to be shortcuts to processing algorithms.
M
On 22 Oct 2015 19:59, "Victor Olaya" wrote:
> >
> > * Why is the processing toolbox not an option for your users? (Do you
> > require
Yep. I think the user-friendliness of ftools are that a/ algorithms are
offered in a simple and accessible menu items, and b/ the menu item icons
_greatly_ ease the understanding of what algorithms do.
Both can be added to processing.
On 22 Oct 2015 20:26, "Matthias Kuhn"
It'd still be good to know why you want the recent project disabled on
startup.
On 11 Nov 2015 22:12, "Matthias Kuhn" wrote:
> Sorry, too fast.
>
> Yes, Settings -> Options -> General -> Open Project On Launch
>
> On 11/11/2015 04:07 PM, Matthias Kuhn wrote:
>
> No, why?
>
>
Arg I meant to say feature parity between QGIS with qt4 and QGIS with qt5.
Darn smartphones.
On 14 Oct 2015 20:20, "Mathieu Pellerin" <nirvn.a...@gmail.com> wrote:
> I really like the idea of making one of the focus of the next dev cycle to
> be qt5. Even if 2.14 is still
I really like the idea of making one of the focus of the next dev cycle to
be qt5. Even if 2.14 is still compiled against 2.14 by default, it'd be
great to attempt to reach user experience parity between 2.14 & 2.15 on the
major platforms QGIS is shipped on.
Having faced the need to compiled and
Nyall,
Great initiative! The sooner a plan can be agreed upon, the better.
Coincidentally to your QEP proposal, I came up with an alternative timeline
idea over the last few days that would avoid skipping a release cycle but
still give us enough time to complete the port to Qt5.
Basically, we
+1 for keeping settings across svg image change
On 10 Oct 2015 18:21, "Nyall Dawson" wrote:
> On 10 October 2015 at 21:02, Nyall Dawson wrote:
> > Hi all,
> >
> > I'm currently working on fixing some issues with svg symbol rendering.
> > I'm
Nyall,
Thanks for addressing this serious long-standing situation with the svg
markers.
For default colors, I think a black outline with a white fill is the most
effective way to preview svg markers that allow users to set both the fill
and border color. Alternatives (black fill & black border
The SVG fill issue was raised >11 months ago here:
http://hub.qgis.org/issues/11522
It only affects QGIS on 64-bit platform (all OSes).
M
On Tue, Sep 15, 2015 at 2:30 PM, Andreas Neumann
wrote:
> Hi Paolo,
>
> It seems like there is no valid file path selected pointing to
ll renders this as black (which I doubt it does),
> but the symbol definition is broken. That doesn't even require a developer
> to fix - any user can do that.
>
> I don't know who changed all these default fills to white?
>
> I'll just add this as a note to the bug description.
&g
Good news!
On 15 Sep 2015 3:45 pm, "Andreas Neumann" <a.neum...@carto.net> wrote:
> Hi,
>
> On 15.09.2015 10:32, Mathieu Pellerin wrote:
>
>>
>> If you change it to black, does it shows properly under 64 bit? Ie have
>> you tried modifying
any user can do that.
>>
>> I don't know who changed all these default fills to white?
>>
>> I'll just add this as a note to the bug description.
>>
>> Andreas
>>
>> On 15.09.2015 09:33, Mathieu Pellerin wrote:
>>
>> The SVG fill issue was raised
At the risk of stating the obvious, selecting multiple nodes (to move or
delete those) has to come back. I do lots of digitizing and shipping 2.12
in its current state would be a very significant regression.
M
On 14 Sep 2015 12:13 pm, "Denis Rouzaud" wrote:
>
>
> On
That'd be a big -1 for me. I use the current OSM tool shipped by default on
a monthly basis.
On 28 Sep 2015 22:55, "Anita Graser" wrote:
> Hi,
>
> I would like to suggest removing the Openstreetmap tool from Vector menu
> for the upcoming release. Reason: It does not work.
Greetings,
(Note: it's the first time I'm trying to compile QGIS using Qt5, so the
problem might be the user here ;) )
Using the current master (what will become 2.12), I fail to successfully
compile a build using Qt5 libraries. The make process crashes when trying
to compile
..@opengis.ch> wrote:
> Hi Mathieu,
>
> On 10/04/2015 03:55 AM, Mathieu Pellerin wrote:
>
> Greetings,
>
> (Note: it's the first time I'm trying to compile QGIS using Qt5, so the
> problem might be the user here ;) )
>
> Using the current master (what will become 2
015 09:53 AM, Mathieu Pellerin wrote:
>
> Larry, Matthias, is there an easy fix that can be applied so 2.12 can ship
> and be qt5-compatible?
>
> Can you check this and report back:
>
> https://github.com/qgis/QGIS/pull/2347
>
> Oh btw, ubuntu now has qt5 packages for sci
I confirm the PR fixes the compilation error (the build is still in the
making, but the auth source files successfully compiled).
Matthias, re QWT, looking into it some more, ubuntu has QWT _6.x_ builds
against Qt5, can I use version 6.x with QGIS?
___
Greetings,
Long story short, QGIS compiled against Qt4 (which is what the official
version does) doesn't support proper Burmese script ordering under linux.
This is due to Qt4 (not actively developed anymore) using an old library to
shape unicode scripts.
QGIS compiled against Qt5 fixes all
I should have added that Qt4 doesn't have rendering issues because it
shapes text using the windows uniscribe library.
On 10 Dec 2015 15:25, "Mathieu Pellerin" <nirvn.a...@gmail.com> wrote:
> Greetings,
>
> Long story short, QGIS compiled against Qt4 (which is what th
t; available?
> I'm happy to try it.
>
> Many thanks & best regards
>
> On Thu, Dec 10, 2015 at 2:56 PM, Mathieu Pellerin <nirvn.a...@gmail.com>
> wrote:
>
>> I should have added that Qt4 doesn't have rendering issues because it
>> shapes text using the w
ey both have issue.
>
> I'll try building from source code.
>
> On Thu, Dec 10, 2015 at 5:29 PM, Mathieu Pellerin <nirvn.a...@gmail.com>
> wrote:
>
>> I should have read your email more carefully, you quite clearly state
>> that the rendering is broken on w
QGIS' expression engine has two string functions – substr() and strpos() –
using two distinct character count standards. The substr() character count
begins with 1, as per the equivalent postgresql string function. The
strpos() character count however begins with 0, as per Qt / python's
equivalent
Sorry, the expression should have been
substr('1234;1234',*1*,strpos('1234;1234',';')),
which in QGIS returns '123'.
On Thu, Nov 19, 2015 at 1:33 PM, Mathieu Pellerin <nirvn.a...@gmail.com>
wrote:
> QGIS' expression engine has two string functions – substr() and strpos() –
> using
Thanks Jürgen.
I realized too late my expression example was wrong, but glad the bigger
point raised was understood :)
On Thu, Nov 19, 2015 at 4:40 PM, Jürgen E. <j...@norbit.de> wrote:
> Hi Mathieu,
>
> On Thu, 19. Nov 2015 at 13:33:20 +0700, Mathieu Pellerin wrote:
>
+100 to stick with current behaviour. My canvas extent very rarely reflects
desired extend and scale of my composer layouts
That said, for your use case, maybe you want to implement a [x] keep extend
and scale synchronised with canvas. Off by default :)
On 11 Jun 2016 18:52, "Nathan Woodrow"
+1 too, for removing openlayers and looking into putting efforts to come up
with a native TMS driver.
Suggestion: instead of just removing openlayers from the plugin repository,
could we work with the author (if he's reachable and willing) for him to
publish a new plugin update stating that a/
Well, first of all, there is officially no such thing as a "community
version" (you can google qgis.org's main domain and documentation, you
won't find a single mention or use of that term).
There's also precedents in the open source world (MySQL comes to mind here)
where a legal entity does a
Im not a huge fan of the "community version" terminology.
QGIS has an official version, found on qgis.org, and a number of flavors
such as boundless :)
On 19 Jun 2016 15:48, "Alessandro Pasotti" wrote:
> It depends on what you mean with "fork", it is a fork in github sense
One more argument in support of moving to Qt5 that goes beyond "newer is
better", thanks for sharing.
On 14 Jan 2016 04:54, "Nyall Dawson" wrote:
> Here's some good news coming from the Qt camp -
>
>
Ramon,
This has been fixed by this commit (
https://github.com/qgis/QGIS/commit/8435fee4a434a4c30b96aa62d09dd345bb2577d4
). Give the nightly a few days to pick that commit.
Math
On Tue, Jan 19, 2016 at 2:02 PM, Ramon Andiñach
wrote:
> Hi,
> I've a relatively recent
Greetings,
It occurred to me that saving a vector layer containing DateTime fields to
an ESRI Shapefile format transforms the DateTime field into a Date field,
leading to the loss of the time data [1]. As far as I understand, this is
not a regression, just something that got onto my radar in the
Can the tag be placed at the end of the commit string or does it have to be
at the beginning?
On 17 Feb 2016 20:16, "Richard Duivenvoorde" wrote:
>
> Hi Devs and Community,
>
> As requested here:
>
>
>
Paolo, do you have additional SVG directories added in your app settings?
On 12 Apr 2016 13:34, "Paolo Cavallini" wrote:
> Il 07/04/2016 19:48, Paolo Cavallini ha scritto:
>
> > I promise I stop throwing new issues for today :)
> > Another old issue resurfacing: Layer
I'd also be careful at removing the toolbar.
I mostly rely on file based vectors & rasters, and I _love_ that the open
vector and open raster buttons are separated and each one remembers a
different last-used folder.
IMO there's a difference btween UI shortcuts (ie the buttons) and the
Anita,
Nyall is looking into this I believe.
M
On Thu, Jul 28, 2016 at 3:34 PM, Anita Graser <anitagra...@gmx.at> wrote:
>
>
> On Thu, Jul 28, 2016 at 10:01 AM, Mathieu Pellerin <nirvn.a...@gmail.com>
> wrote:
>
>> The problem with moving the [ edit ] b
gt; On Thu, Jul 28, 2016 at 5:32 AM, Mathieu Pellerin <nirvn.a...@gmail.com>
> wrote:
>
>> Hey Anita,
>>
>> Having worked on reducing the width of the rendering UIs in the last dev
>> cycle, I'm familiar with the issue raised here :)
>>
>>
Hey Anita,
Having worked on reducing the width of the rendering UIs in the last dev
cycle, I'm familiar with the issue raised here :)
Basically, the singleband pseudocolor renderer's minimum width is
determined (ATM) by the "Color [ramp]" row. More specifically, if you have
a color ramp with a
Here's what I described above, in a screenshot:
http://i.imgur.com/ifVoMus.png
M
On Thu, Jul 28, 2016 at 10:32 AM, Mathieu Pellerin <nirvn.a...@gmail.com>
wrote:
> Hey Anita,
>
> Having worked on reducing the width of the rendering UIs in the last dev
> cycle, I'm familiar wit
I'm -1 on removing polygon outline by default. In many datasets (think
administrative boundaries, cadastral polygons, etc.), polygons share
boundaries and the outline is important.
On the other hand, I'm not against improving things by default :) IMHO, we
could greatly improve default coloring by
+1 from me.
On Tue, Feb 7, 2017 at 3:52 PM, Nyall Dawson wrote:
> Hi all,
>
> Following up on one of the points raised by John Hawkison (author of
> the famous "my first weekend with QGIS" email), I'd like to raise
> discussion about renaming all use of outline/border
I've never used the browser much, I can't say I would miss it if it's
retired.
The one thing I'd miss a bit is its capability at quickly previewing
datasets. I'm wondering if this could be somehow integrated into the QGIS'
browser dock (maybe now made possible following the major layer registry /
Hey Christophe,
I won't answer your question directly I'm afraid, but there might be a
better-practice / compatibility improvement you can do to your icons.
Question first: are the background O\D elements text objects, or paths? If
the answer is text objects, you'd be better transform those into
Hmm, I'm -0 on this. I frequently use it to stop an ongoing rendering
process of large dataset(s). I realize it might be misusing that checkbox
as a stop ongoing rendering (vs. no rendering) but it's evidence it remains
useful.
That said if your open to ideas, it could go away if it's replaced by
Tim,
There's an extra bonus to monochrome + highlight color icon set: it is
much, much easier for people and groups (such as Gandesh) to customize
icons to their needs. Ie, if a group wants to create an "accent colour"
icon set, it'll be much easier to do so using a monochrome set to begin
with.
Please don't change the default behavior for 3-band rasters to min/max;
while it does make in many scenarios for 1-band rasters (DEM, precipitation
value, vegetation index, etc.), this is a terrible default value for most -
if not all - satellite imagery products (i.e. Sentinel-2, LANDSAT-{5,7,8},
It'd be nice to move the "Snapping options" menu item to be located into
the Project menu (below or above the "Project properties" item). It doesn't
make much sense to have it located where it is ATM.
M
On Fri, Sep 2, 2016 at 6:30 PM, Denis Rouzaud
wrote:
> Hi all,
>
>
+1 on flatpak / snap package offering, in addition to the current
system-libraries-based solution.
On Tue, Sep 6, 2016 at 1:49 PM, Matthias Kuhn wrote:
> On 09/06/2016 08:41 AM, Marco Bernasocchi wrote:
> > What about setting 5.7 as required minimum for qt?
>
> If you
Greetings,
While testing QGIS compiled against Qt5 5.6.1 (the version that will be
offered in Ubuntu's next release in a month or so), I ran into a rounding
issue, whereas the round() expression engine function simply fails to round
values to the stated number of decimals.
As seen in this
seems to be prefered:
> https://lists.osgeo.org/pipermail/qgis-developer/2016-August/044127.html
>
> Denis
>
>
>
> On 09/05/2016 04:39 AM, Mathieu Pellerin wrote:
>
> Greetings,
>
> While testing QGIS compiled against Qt5 5.6.1 (the version that will be
> offere
Nyall,
IMO, this item (QgsComposerLabel - approach 1. Switch to the basic
QTextDocument support) should be applied, irrespective of the QWebView
situation. I have never expected to get full-fledged html support when
checking the render as HTML, especially since we have an HTML element
alongside
Yep. The probem has to do with make install copying python files from the
source tree not the output directory (therefore not benefiting from 2to3)
On Sep 18, 2016 6:57 PM, "Richard Duivenvoorde" <rdmaili...@duif.net> wrote:
> On 18-09-16 13:24, Mathieu Pellerin wrote:
&
This error means that your python files have not passed through 2to3. Make
sure PORT_PLUGINS flag is turned on.
Also right now, the make script only runs 2to3 against the python code
inside the output directory, it does *not* do so for the python code copied
to your install location during "make
For the UI side of things, I'd also like to see {QuickMapServices,
OpenLayers} updating its code so that - on QGIS >= 2.18 - layers are served
as native TMS support. That'd make pre-existing users of those plugins able
to continue using the same UI as before, while benefiting from Martin's
Unless we have a feature parity with the current openstreetmap tool
(offered through vector -> openstreetmap), please do not drop it. One
useful feature that isn't available through OGR (or QuickOSM last time I
trieD) is the exporting of individual tags as fields (versus only creating
a few fields
Richard.
This commit,
https://github.com/qgis/QGIS/commit/59583e97deef732f6884a54b518fc34225fd6012
, fixed a 9-day-old regression which had QGIS constantly use CPU.
Math
On Sun, Sep 11, 2016 at 8:39 PM, Richard Duivenvoorde
wrote:
>
> Hi, are we the only ones?
>
> It's a
There's an open PR that handles this issue here
https://github.com/qgis/QGIS/pull/3271
On Sep 28, 2016 13:46, "Richard Duivenvoorde" wrote:
> On 27-09-16 22:41, C Hamilton wrote:
> > Several individuals have mentioned the problem with the Invert not
> > working in 2.16.2
t;
> Matthias
>
> On 11/07/2016 12:26 PM, Mathieu Pellerin wrote:
> > We should indicate in the function help that strpos is regexp based.
> >
> >
> > On Nov 7, 2016 6:23 PM, "Matthias Kuhn" <matth...@opengis.ch
> > <mailto:matth...@opengi
Or we could upgrade regex_match() to return an offset instead of a binary
false / true.
On Nov 7, 2016 7:17 PM, "Matthias Kuhn" <matth...@opengis.ch> wrote:
I haven't found any existing functionality. regexp_pos?
On 11/07/2016 01:12 PM, Mathieu Pellerin wrote:
> I ll tak
We should indicate in the function help that strpos is regexp based.
On Nov 7, 2016 6:23 PM, "Matthias Kuhn" wrote:
> Hi,
>
> strpos is based on regexp, a '.' matches any character.
> To let the engine treat a . as such you need to prefix it with a
> double-backslash.
>
>
Nice. Glad this is moving forward.
Will this facilitate an eventual (not part of your proposal/work)
multi-map-frame environment? Alvaro might have good considerations to offer
on that front.
On Oct 24, 2016 2:01 PM, "Nathan Woodrow" wrote:
> Nice!. This is very welcome.
Stephen,
Your feature enhancement request has been heard, and as soon as this PR (
https://github.com/qgis/QGIS/pull/3851) is merged will be reality :).
Math
On Thu, Dec 1, 2016 at 9:52 PM, Howard, Stephen wrote:
> I tried to request the following feature enhancement some
Processing and db manager works under QGIS. What are the error messages you
get? I d suspect missing Python 3 modules/packages being problem here.
On Dec 13, 2016 21:51, "Andreas Neumann" wrote:
> Hi,
>
> I compiled and installed QGIS 3 - which worked fine. But at start of
Paola,
Thanks for testing. To answer to your notes:
* Good point on the "edit color ramp..." menu shortcut, I'll fix that
* >1 week ago, I revamped the default symbols, we could also revamp the
saved color ramps (and highlight a few excellent ones via favorites)
* I'm a definite -1 for changing
* -1 for QGIS development to go back to the "wait until ready" mode which
delayed QGIS 2.0 way too long
* +0.5 to have a serious discussion around a possible (fixed in time)
extension :)
Let's not forget that while of us on the dev mailing list run on home-made
or nightly builds, which tents to
Victor,
I was looking into this; it'd be nice for the "build vector layer"
algorithm would support/show geometryless layers in the parametermultiinput
panel. AFAIK, geometryless layers aren't (yet? :) ) supported by the
parametermultiinput.
Math
On Mon, Dec 5, 2016 at 2:51 PM, Victor Olaya
As well all agreed on need to rename the new color ramp categories, let me
put forward new names and ordering:
*Current:*
Gradient
Random
ColorBrewer
Preset colors
cpt-city
*Proposed:*
Gradient (stays the same)
Palette (instead of Preset colors)
Presets: cpt-city (instead of
Tom,
While Nyall's right to point out further API disruption on the horizon,
your exercise isn't in vain since the plugin adjustments you've figured out
will still be needed when porting season will open.
If you have time, you should write a blog post somewhere to detail this
experience of
Alex, there is one aspect where gdaltools plugin still surpasses
processing, namely the possibility of creating virtual rasters from
multiple files without having to load those in QGIS to begin with.
If that could be dealt with, I wouldn't look back to the plugin in a
hundred years :)
On Dec 23,
Tim,
-1 to use OSM-based XYZ tile server that doesn't update its dataset on a
regular basis (+/- weekly). While there are nicer styles that OSM's default
one, one of the fundamental dynamic of OSM is the ability to update / add
spatial data and see those updates reflected on tiles immediately. We
Tim,
Great to see the new logo prominently featured on the 1st page.
BTW, you might want to update your signature to make use of the new logo
too.
Math
On Tue, Apr 4, 2017 at 4:42 PM, Tim Sutton wrote:
> Hi All
>
> Thanks for your patience waiting for the grant proposals to be
Nyall,
I'm -1 if it means removing the add spatialite layer UI; otherwise, if UI
isn't impacted, there's definitively a rational to go ahead and use OGR
(and fix any discovered issue within the OGR library, benefiting the wider
ecosystem).
M
On Mon, Mar 13, 2017 at 8:28 AM, Nyall Dawson
Big +1 too. I always found the current behavior (show all of nothing is
selected) slightly counter-intuitive.
On Tue, Mar 7, 2017 at 11:28 AM, Nyall Dawson
wrote:
> Hi all,
>
> I'd like to raise discussion about changing the behaviour of the "show
> selected features"
Andreas,
I think you're looking for: lpad("my_number",n - length("my_number"),0)
Math
On Wed, Jul 12, 2017 at 3:02 PM, Neumann, Andreas
wrote:
> Hi,
>
> Is there a way in a QGIS expression to format numbers with leading zeros
> up to n places before the decimal point?
Would that negatively impact on models? Assuming here that the attribute
input was able to interact with model string outputs.
On Jul 13, 2017 13:11, "Alexander Bruy" wrote:
> As part of the ongoing Processing upgrade and cleanup we should take
> the opportunity to get
g. Zonal Statistics,
> old basic statistics, etc
>
> 2017-07-13 9:16 GMT+03:00 Alexander Bruy <alexander.b...@gmail.com>:
> > Module will be broken anyway
> > (https://github.com/qgis/QGIS-Enhancement-Proposals/issues/95)
> > so I see nothing bad here.
> &g
This PR (https://github.com/qgis/QGIS/pull/4792) adds variance to
QgsZonalStatistics, and remove the duplicate processing zonal statistics
algorithm on the basis of a general consensus in this mail tread and more
importantly its author, Alexander Bruy, agreeing.
Thanks for the time spent
FYI, I coincidentally spotted this nice commit (
https://github.com/nextgis/quickmapservices/commit/9ae9efd6bf2a162762262672bd93c9958cc822d1)
pushed to QuickMapServices' repository. This will make it possible to add
native XYZ layers via the QuickMapServices and therefore benefit from all
of is
+1, I'm a regular user of that alg & your proposal makes sense. It'll be
useful to have the reduced single to multi geom type within models.
On Jun 27, 2017 6:28 AM, "Nyall Dawson" wrote:
> Hi all,
>
> As you may be aware, I've been working on rebuilding the backend of
>
As part of the ongoing upgrade and cleanup done by the Nyall, we should
take the opportunity to get rid of one of the overlapping "Zonal
Statistics" and "Zonal Statistics (QGIS)" algorithms. The latter relies on
QGIS' QgsZonalStatistics.
Yesterday, I've resurrected the "Zonal Statistics (QGIS)"
, Nyall Dawson <nyall.daw...@gmail.com>
wrote:
> On 28 June 2017 at 12:19, Mathieu Pellerin <nirvn.a...@gmail.com> wrote:
> > As part of the ongoing upgrade and cleanup done by the Nyall, we should
> take
> > the opportunity to get rid of one of the overlapping "
You can also build your VRT using QGIS' processing toolbox.
On Oct 5, 2017 7:26 PM, "Régis Haubourg" wrote:
> GDAL is probably installed on your system, you need it for QGIS :)
>
> something like this should do the trick in a linux bash or from the
> osgeo4w embedded
Martin,
I was a pretty heavy user of this feature/plugin until a few months ago
when it stopped working under master. I moved to loading OSM through the
OGR provider (customized via osmconf.ini) and never looked back. I would
love for QGIS to regain some sort of native OSM data import, maybe
Andreas,
The regression has now been fixed (see
https://github.com/qgis/QGIS/commit/51170aec0ce0a2acfbb6805dc962dbf691bba356
).
Math
On Tue, Aug 29, 2017 at 1:14 PM, Neumann, Andreas
wrote:
> Hi,
>
> We are starting to use QGIS 3 in production because we need some of the
Off the top of my head, what I remember: the way zoomed in resampling
occurs isn't compatible with reprojected rasters. It's visible on the main
canvas as soon as your project's CRS != raster's CRS. I *think* zoomed out
resampling didn't suffer from the same issue.
On Mon, Nov 13, 2017 at 10:17
You could potentially use a model to save refactor fields settings. That
said, there's currently a problem (see issue
https://issues.qgis.org/issues/17421) preventing this algorithm from being
used in a model.
M
On Thu, Nov 23, 2017 at 3:01 PM, Andreas Neumann
wrote:
> Hi,
+1 to all four PRs, especially the dynamic number value for processing one
which I've tested quite a lot in the last 48 hours and couldn't detect any
problem.
On Nov 28, 2017 6:39 AM, "Nyall Dawson" wrote:
> On 27 November 2017 at 08:32, Tim Sutton
There's a chance this commit (
https://github.com/qgis/QGIS/commit/f5702abae9dfeae8a73c335871375076132435de)
fixes your issue. Let me know.
On Thu, Nov 30, 2017 at 6:10 AM, Andreas Neumann
wrote:
> Hi Nyall,
>
> Unfortunately - turning off custom widgets in ccmake and
I find the project home node brilliant, but I've not used it so far (the
way I structure my data isn't compatible with this concept).
That said, testing it this morning, the behavior was not was I was
expecting. IMHO, this node should essentially act as a symlink, and
maintain the sub-directory
Sorry all, just ignore this message. Human broken, not the machine, once
again.
That'll teach me to write emails prior to intake of caffeine.
On Thu, Dec 14, 2017 at 9:09 AM, Mathieu Pellerin <nirvn.a...@gmail.com>
wrote:
> I find the project home node brilliant, but I've not used
Hmm we just jumped from discussing feature freeze exception to delaying
release, is that correct?
Personally, I'm big +1 for feature freeze exceptions-only *if* release date
remains achievable. If not, it seems there is a consensus on adding
additional time to this dev cycle, which remains
of all the
> crashes I often experience (and are often hard to reproduce and report).
>
> Andreas
>
> On 2017-11-06 13:17, Mathieu Pellerin wrote:
>
> Hmm we just jumped from discussing feature freeze exception to delaying
> release, is that correct?
>
> Personally,
The global use only selected features option is gone (yay) in favor of a
checkbox which can be activated on a per-use basis. I believe iterating
through selected features only requires a vector source input.
On Dec 11, 2017 20:57, "Andreas Neumann" wrote:
> Hi,
>
> In QGIS
del I also loose
> the whole context of widgets and relations, because it is a new virgin
> layer then with no link to the original layer configuration (widgets,
> relations) - right?
>
> Thanks for your reply,
>
> Andreas
>
> On 2017-12-11 15:15, Mathieu Pellerin wrote:
&
Right click on the color ramp button, you'll find an "invert ramp" menu
item.
On Wed, Jun 6, 2018, 07:35 C Hamilton wrote:
> In QGIS 2 when you apply a pseudocolor color ramp to a DEM there was an
> Invert color ramp check box. I cannot find it in QGIS 3.0.3. Am I missing
> something or has it
ng in Funchal
> (second half of February).
>
> As an example I still get error messages about the authentication manager
> not able to open password files or reading/storing information about
> passwords. Seems pretty serious to me - we should not ship in such a state.
>
> Andreas
&g
Let that person with authority also lock in the release date.
Very last day of this month, Jan 31? While Feb 8 isn't that far, it'd still
be great to deliver our product by the end of this month. Either way we
need to settle on a date.
M
On Jan 9, 2018 05:27, "Nyall Dawson"
rgen E. Fischer" <j...@norbit.de> wrote:
> Hi Matthias,
>
> On Tue, 09. Jan 2018 at 12:31:32 +0100, Matthias Kuhn wrote:
> > On 01/09/2018 11:21 AM, Mathieu Pellerin wrote:
> > > > Also for the bug fixing, lets give it a full month
> > >
&
Denis,
Actually, all of the settings in the snapping config dialog are
project-specific and do not persist across projects. The application-wide
snapping settings are found in the options dialog (under the digitizing
tab).
Math
On Mon, Jan 15, 2018 at 8:45 PM, Denis Rouzaud
Matteo,
This PR (https://github.com/qgis/QGIS/pull/6170) should fix this regresion.
Math
On Thu, Jan 25, 2018 at 3:48 PM, matteo wrote:
> Hi all,
>
> I really like the new buttons in the Processing panel, a small change
> with a lot of benefits for the users.
>
>
101 - 200 of 273 matches
Mail list logo