Aggregate Change #11

New Issue

kske · 2021-12-29T22:44:55+01:00

kske commented

2021-12-29 22:44:55 +01:00

In some cases, multiple individual changes are supposed to be treated as one, e.g. when deleting multiple selected objects in an editor. For this purpose, an aggregate change class can be created that combines multiple changes into one.

The main issue with that is the type of that class and how it is used, as it should be usable with change managers for a specific kind of change without loosening their type constraints.

In some cases, multiple individual changes are supposed to be treated as one, e.g. when deleting multiple selected objects in an editor. For this purpose, an aggregate change class can be created that combines multiple changes into one. The main issue with that is the type of that class and how it is used, as it should be usable with change managers for a specific kind of change without loosening their type constraints.

kske added the

13

could have

enhancement

labels 2021-12-29 22:44:55 +01:00

kske self-assigned this 2021-12-29 22:44:55 +01:00

kske started working 2021-12-29 22:45:02 +01:00

kske worked for 16min 42s

2021-12-29 23:01:44 +01:00

kske added reference f/aggregate-change

2022-02-11 09:49:55 +01:00

kske added a new dependency 2022-02-11 09:51:13 +01:00

zdm/taskforce#169 - Multi-Selection in Editor Change History

This repo is archived. You cannot comment on issues.

1 Participants

Total Time Spent: 16 minutes 42 seconds

kske

16 minutes 42 seconds

Due Date

No due date set.

Blocks

You do not have permission to read 1 dependency

Reference: zdm/undo-redo#11