This is by-design so I have switched the group to feature request. While it may be possible to implement this, possibly even within the container, there are problems. The most prominent difficulty is that undo is implemented on the document and selection is implemented on the views.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
This is the basic mechanism but tweaks may be required for some commands. It needs to ensure that the selection at the very start and end of any command is saved rather than a selection manipulated by the command before starting the text change. Applications may need new start and end command APIs.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
More associated with undo than selection so renamed SelectionUndoHistory to UndoSelectionHistory[fe170a]. Made it an enum as its likely there will be more options added.
This is by-design so I have switched the group to feature request. While it may be possible to implement this, possibly even within the container, there are problems. The most prominent difficulty is that undo is implemented on the document and selection is implemented on the views.
Implemented by [769d2a].
Related
Commit: [769d2a]
This is the basic mechanism but tweaks may be required for some commands. It needs to ensure that the selection at the very start and end of any command is saved rather than a selection manipulated by the command before starting the text change. Applications may need new start and end command APIs.
More associated with undo than selection so renamed
SelectionUndoHistorytoUndoSelectionHistory[fe170a]. Made it an enum as its likely there will be more options added.Related
Commit: [fe170a]