Skip to content

Conversation

@koebi
Copy link
Contributor

@koebi koebi commented Jun 4, 2025

Goal:
The former documentation and the existing implementation do not align.
This change aims to clear that up and make it more transparent to users what the algorithms do if they are used in-place.

  • Backport to LTR documentation is requested

To be available for in-place editing, processing algorithms implement
the `bool supportInPlaceEdit(…)`-method.
As this is not dependent on the algorithms only working on feature
source level or not modifying fields, but stands on its own, it might
make it easier for users if we communicate what these algorithms do, not
why or why not they are available.
koebi added a commit to koebi/QGIS-Documentation that referenced this pull request Jun 4, 2025
Copy link
Collaborator

@DelazJ DelazJ left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @koebi
The old description tried to (maybe incorrectly) explain the list of remaining algorithms i.e., what makes an algorithm eligible to in-place editing. If I understand clearly, this PR tries to explain how an algorithm works in in-place editing context. I don't think both are incompatible or one should replace the other. Is that not possible to have both?

layer level. It does not change the layer structure, e.g. adding or removing
fields. Algorithms that usually work on layer level, e.g. ``Reproject
layer`` or add fields, e.g. ``Orientated minimum bounding boxes`` will not
do so when editing features in-place.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It is unclear to me what the "Reproject layer" alg will not do.


* They work at the feature source and not at the layer level.
* They do not change the layer structure, e.g. adding or removing fields.
* They do not change the geometry type, e.g. from line to point layer.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The info about geometry type is removed. Does it mean that it is now possible to change geometry type of features?

Comment on lines +2170 to +2171
fields. Algorithms that usually work on layer level, e.g. ``Reproject
layer`` or add fields, e.g. ``Orientated minimum bounding boxes`` will not
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
fields. Algorithms that usually work on layer level, e.g. ``Reproject
layer`` or add fields, e.g. ``Orientated minimum bounding boxes`` will not
fields. Algorithms that usually work on layer level (e.g., ``Reproject
layer``) or add fields (e.g., ``Oriented minimum bounding box``) will not

qgis-bot pushed a commit that referenced this pull request Jun 19, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants