On 28.07.2020 22:15, Alessandro Pasotti wrote:
Hi,
Seems pretty bad, please file a ticket.
Thanks, Alessandro!
Done: https://github.com/qgis/QGIS/issues/38018
Anita
On Tue, Jul 28, 2020, 21:45 Anita Graser mailto:anitagra...@gmx.at>> wrote:
Hi,
There seems to be a performance
Hi Even,
Thanks for confirming this.
Andreas
Am 28.07.20 um 18:23 schrieb Even Rouault:
On mardi 28 juillet 2020 17:06:05 CEST Andreas Neumann wrote:
> Thanks for sharing this discussion.
>
> So when you load an old project in QGIS master, the average method would
> be replaced with
Hi,
Seems pretty bad, please file a ticket.
On Tue, Jul 28, 2020, 21:45 Anita Graser wrote:
> Hi,
>
> There seems to be a performance regression concerning "Show selected
> features" in the attribute table of recent QGIS versions. (See also
>
Hi,
There seems to be a performance regression concerning "Show selected
features" in the attribute table of recent QGIS versions. (See also
https://twitter.com/DrChrisGeoSci/status/1288120808951312389)
I've tested this with the Natural Earth dataset ne_10m_populated_places
layer. The
On mardi 28 juillet 2020 17:06:05 CEST Andreas Neumann wrote:
> Thanks for sharing this discussion.
>
> So when you load an old project in QGIS master, the average method would
> be replaced with bilinear now?
>
> Is "bilinear" the closest method to the previous "average"?
This is just a label
Thanks for sharing this discussion.
So when you load an old project in QGIS master, the average method would
be replaced with bilinear now?
Is "bilinear" the closest method to the previous "average"?
On 2020-07-28 16:55, uclaros wrote:
You can have a look at the discussion at
You can have a look at the discussion at
https://github.com/qgis/QGIS/pull/37044
--
Sent from: http://osgeo-org.1560.x6.nabble.com/QGIS-Developer-f4099106.html
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info:
Hi,
In QGIS master, when symbolizing raster layers, the "average" resampling
method disappeared and is now replaced by nearest, bilinear and cubic
alternatives.
Anyone knows why "average" disappeared?
Here a screenshot of 3.10:
and here from master:
Could we get the "average" method
And in the SVG param primer, you can see examples of adjustable text in
elements (e.g. buttons, icons, etc.):
https://www.w3.org/TR/SVGParamPrimer/#Examples
Given that we already have the param mechanism in QGIS, it would fell
natural to extend it to text as well.
And - if we really want
Hi Régis,
In general - you are right - but the problem with standards it that they
are often ignored. Browser developer companies (like Google) basically
ignore 80% of the W3C standards and just implement what they want. I was
involved with SVG standardization a decade ago - and I have to say
Hi,
I think we should better follow the standard for internationalizing instead
of progressively making a proprietary format.
See https://www.w3.org/TR/SVGTiny12/i18n.html
Cheers!
Le mar. 28 juil. 2020 à 09:57, Andreas Neumann a
écrit :
> Hi all,
>
> I am only loosely following this discussion.
Hi all,
I am only loosely following this discussion.
But about the internationalization: couldn't we use the same param -
mechanism we already have for fill-color, stroke-color, opacity, etc.
and extend it to the content of elements?
That would solve internationalization and would also be
On 28-07-2020 02:44, Nyall Dawson wrote:
Oh, also they'd need to be "parameterised", so that users can set the
fill/stroke color, opacity and stroke width from within QGIS.
I've made some quick and dirty scripts in the past to add these tags to
sets of svg symbols. If needed I can help
OK so comparing dependencies has not found any that appear significant.
Only differences found were in a couple of OpenJDK packages.
Methodology:
1. Create a list of packages and versions from the entire system using
dpkg-query:
dpkg-query -W -f='${binary:Package}|${Version}\n'
14 matches
Mail list logo
