Queued LTR backports #59225

…gle quote

…en no atlas geometry available

… not supported The PDF driver only supports 'random' creation for vectors, not raster. For raster, it only supports CreateCopy() mode Refs #58891

Just reset the font size to a standard size when generating the preview, otherwise we end up with invisible text on the buttons if the font size is too big or too little.

While painting, it happens that other code can modify current item position, but this new position will be really used on the new draw, not the current one. So we have to backup it early enough (at the very beginning of paint) so we can translate to this new position at the end of the paint method. Fixes #37566 (Again)

…': it is go.Barplot in recent plotly versions

…ttribute table dialog breaks the current sort column and sort order due to the column and order being hard-coded to 0 and Qt::AscendingOrder respectively.

Always internally store the distance in canvas's CRS units, transform for display. Fix #58620 where the CRS units are US Feet.

Fix #58862

In other cases we'll need a blocking hit test anyway, and we run a risk of deadlocks if a non-preview render is then started on the main thread. Fixes #58496

The `srsName` used in `QgsWfsGetFeature::startGetFeature` can be defined with the `urn:ogc:def:crs:EPSG::X` syntax. In that case, the destination crs is not valid because it is created with the default `QgsCoordinateReferenceSystem` constructor which does not handle this syntax. Therefore, in that case, the requested transformation fails and the envelope coordinates are always in the input crs (the layer one). This issue is fixed by using `QgsCoordinateReferenceSystem::setDestinationCrs` which handles the ogc urn syntax. The test suite already covers the `urn:ogc:def:crs:EPSG::X` syntax case. However, this issue is not detected because the requested output crs is the same as the input one.

The axis inversion needs to be checked on the output crs, not the input one. The existing test does not detect this issue because the requested output crs is the same as the input one. To cover this case, a new test with a output crs different from the input one is added.

This makes it easier to understand its usage.

There are 2 different parameters to check to define the output crs: - the request parameter (`SRSNAME` from the request) - the query crs parameter For a `GET` request, if `SRSNAME` is set, both parameters are set and equal. For a `POST` request, only the query parameter is set if defined. In `writeGetFeature()`, the `outputCrs` correctly takes into account the query parameter. However, this is not the case for the output srs name (`srsName`) which only takes into account the query CRS as an auth id. Therefore, the output srsName will always be defined as an authid even if the parameter is an ogc urn. This issue is fixed by first computing the output srs name (`outputSrsName`) by taking into account the query and the query parameters. Then, this name is used to compute `outputCrs`.

Always use the canvas method to create an expression context for expression widgets (when available), as it will always contain all the available variables. Fixes missing variables (eg @animation_*) in some contexts, eg in the labeling widget.

When a layout attribute table is set to show features in atlas only, but atlas geometry is NOT available, then just early exit instead of looping through every feature just to show none of them

The filter rect was NOT being set in this situation, because the atlas geom filter has an empty (but non-null) extent Fixes #58274

…nderer Fixes #55426

…iles algorithms

…are not used to conduct bulk download of OSM tiles

…sed to conduct bulk download OSM tiles

…en exporting the layer to file (both via the browser panel as well as the layer tree)

Fixes rendering of vector tile and annotation layers with non default blend modes in layouts Fixes #55629 (cherry picked from commit 9ed009f)

With previous code, pixmap was never taken from cache

Fix #58845

If not, saveEdits would be called when we fire widgetValueChanged signal and widgets containing non updated old values could potentially overwrite new ones, leading to discard user modifications.

Co-authored-by: Alessandro Pasotti <[email protected]>

When the aggregate uses variables, we need to ensure that the cache key correctly considers the current value of ALL those variables. Otherwise we'll return incorrect results when an expression is re-evaluated after changing the variable value for the context. Fixes use of aggregate function with @symbol_label in legends. Fixes #58221 (cherry picked from commit 7b88103)

(cherry picked from commit f618993)

…agDontResolveLayers Fixes #58818 (cherry picked from commit 0c9320c)

This can happen when eg a broken item size causes a nan position, which breaks the layout size calculation and results in nan or massive x/y values. Restoring these leads to a broken layout which cannot be interacted with. Refs #55240

This causes the map item to have nan pos or size, which corrupts the layout

…ized

In multi edit mode feature is not updated (so attributeChanged is false) until user validate it but we need to update the value relation which could have an expression depending on another modified field

… explicit This will avoid implicit conversion to bool when comparing QList<QgsMapLayerRef>s in the future.

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Queued LTR backports #59225

Queued LTR backports #59225

Commits on Oct 25, 2024