Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

3.16.5 queued backports #41054

Merged
merged 71 commits into from
Feb 19, 2021
Merged

Conversation

nyalldawson
Copy link
Collaborator

@nyalldawson nyalldawson commented Jan 17, 2021

Previously approved backports queued for 3.16.5

@nyalldawson nyalldawson added Backport Is a backport of another pull request NOT FOR MERGE Don't merge! labels Jan 17, 2021
@nyalldawson nyalldawson added this to the 3.16.5 milestone Jan 17, 2021
troopa81 and others added 24 commits February 19, 2021 10:37
…marker

available shapes

(cherry picked from commit c582967)
when a script calls Processing.initialize() if they are not
already loaded

This means the following ugly code can be avoided:

    Processing.initialize()
    QgsApplication.processingRegistry().addProvider(QgsNativeAlgorithms(QgsApplication.processingRegistry()))
    QgsApplication.processingRegistry().addProvider(Qgs3DAlgorithms(QgsApplication.processingRegistry()))

and instead the call to Processing.initialize() is sufficient to load
ALL providers

Fixes qgis#41310

(cherry picked from commit b402544)
the definition of one of the stored GDAL profiles

Fixes qgis#41378
Fixes qgis#40235

(cherry picked from commit 7454a0e)
…an algorithm from processing history

(cherry picked from commit 5ba423d)
And fix test flakiness

(cherry picked from commit 1ed964d)
save changes

Regardless of the reason why the saving failed, a message about
invalid JSON was always shown... which is totally confusing for
users when a table has NO json fields or values (ノ`Д´)ノ

(cherry picked from commit e34779a)
(cherry picked from commit a7ff77b)
results in an incorrect failure status when editing a layer
which contains joins

This causes the attribute form to incorrectly report that changes
cannot be saved whenever attempting to edit a layer which contains
a join and a mix of joined/not-joined attributes are edited.

(cherry picked from commit 01889d9)
indeterminate state

When editing multiple features with differing values for a text
edit widget field, the widget should show an empty line edit
and not a widget showing "NULL".

(cherry picked from commit fa91357)
the checkbox form widget

In QGIS 2.x we always displayed the underlying raw value of a field
using the checkbox widget in the attribute table or in identify results
(i.e. the text display of the field would always match the value
the user had set for the checked or unchecked representation status,
e.g. "yes"/"no", "present"/"absent", etc)

This was changed in 3.0 so that the representation status ONLY affected
how the underlying stored values are mapped to a boolean true or false
value, and accordingly the attribute table/identify results started
only showing "true" or "false" strings.

This new setting allows users to control whether they want plain text
displays of the field to use the 3.x "true"/"false" behavior (the
default), or if they want to see the 2.x style actual field value.

(cherry picked from commit eba9ffa)
manual table text format widgets

These text formats have access to the full layout item expression
context, and also extra variables for @row_number and @column_number,
but these weren't being shown in the UI. Expose them for use in
expressions and highlight the useful @row/column_number variables.

(cherry picked from commit f337271)
field) when the attribute form is opened.

This is incredibly expensive, yet only required in a very very small
corner case (field is from a joined layer without the upsert on edit
capabilities).

Refine logic to avoid the scan wherever we can.

Fixes qgis#41366
Fixes qgis#36863

(cherry picked from commit c661359)
Fixes qgis#29682

Manual backport of master commit e859d44
Follows GeoServer convention, fixes qgis#36584

Cherry-picked from master e967fd9
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Backport Is a backport of another pull request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

9 participants