When skipping (or removing, deleting, cutting and pasting) a task (or multiple tasks) the project is used as a scope for the undo/redo command. This can be reduced greatly (potentially reducing a significant lag spike for larger projects) if we use only the process component that is operated on (in case of the skip state) or at most the task group.
I would propose to add this to the next patch release (2-0-7 or 2-0-8). But it should be a quick fix.
Impact on the codebase
Minimal, and there should be no ABI change. We just have to change a few lines and update the scope
Current workarounds
None needed, however significant lag spikes must be endured when skipping a task for example.
Summary
When skipping (or removing, deleting, cutting and pasting) a task (or multiple tasks) the project is used as a scope for the undo/redo command. This can be reduced greatly (potentially reducing a significant lag spike for larger projects) if we use only the process component that is operated on (in case of the skip state) or at most the task group.
I would propose to add this to the next patch release (2-0-7 or 2-0-8). But it should be a quick fix.
Impact on the codebase
Minimal, and there should be no ABI change. We just have to change a few lines and update the scope
Current workarounds
None needed, however significant lag spikes must be endured when skipping a task for example.