From 5e4e6e537cce15c3ec421cd87170cc00136e404c Mon Sep 17 00:00:00 2001 From: twystd Date: Mon, 4 Nov 2024 17:20:49 -0800 Subject: [PATCH] Updated user guide with undo/redo --- CHANGELOG.md | 3 ++- GUIDE.md | 10 ++++++---- 2 files changed, 8 insertions(+), 5 deletions(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index b9b3295..269eaef 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -1,11 +1,12 @@ # CHANGELOG -## Unreleased +## [0.1.0](https://github.com/transcriptaze/VPD/releases/tag/v0.0.0) ### Added 1. Added trimpot, button, pushbutton and slider parts. 2. Added support for polar coordinates. 3. Added support for the (slightly idiosyncratic) DuckDuckGo browser. +4. Added (provisional) implementation of 'redo'. ### Updated 1. Implemented versioned structs so support future changes. diff --git a/GUIDE.md b/GUIDE.md index 66762be..d514b46 100644 --- a/GUIDE.md +++ b/GUIDE.md @@ -249,16 +249,18 @@ To save a project as a _.vpx_ file: ### Undo -- Undoes the last command and displays it in the command entry panel. +- Undoes the last command and displays it in the command entry panel. **Please see note below in _redo_.** ### Redo - _Redo_ undoes the ost recent _Undo_ and displays the next command (if any). -The _redo_ implementation is fairly basic and mostly intended to help locate a recent point in the command stack -at which to start making changes. Executing any command other than another _undo or _redo_ clears the redo stack -so if you're intending to make a change deep in the command stack rather save and modify the current script. +The _redo_ implementation is fairly basic and executing any command other than another _undo or _redo_ **clears the redo stack** +i.e. save the script if you have recent changes you would rather not lose. + +The _undo_/_redo_ implementation is mostly intended as a convenience to review recent commands - and for fixing simple mistakes. +More complex changes should rather be done by editing and then loading a VPX script. ### Macro keys