-
-
Notifications
You must be signed in to change notification settings - Fork 884
Align in-place documentation #9926
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
base: master
Are you sure you want to change the base?
Conversation
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.
This is superseded by qgis#9926
DelazJ
left a comment
There was a problem hiding this 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. |
There was a problem hiding this comment.
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. |
There was a problem hiding this comment.
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?
| fields. Algorithms that usually work on layer level, e.g. ``Reproject | ||
| layer`` or add fields, e.g. ``Orientated minimum bounding boxes`` will not |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| 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 |
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.