Skip to content
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

undo & redo support #4863

Open
wants to merge 47 commits into
base: main
Choose a base branch
from
Open

undo & redo support #4863

wants to merge 47 commits into from

Conversation

emptyrivers
Copy link
Contributor

if you want to test it out, checkout this branch, or download the build artifact, either should have the feature automatically enabled. This feature is (for now) disabled by default on alpha/beta/release builds, though you can enable it via the command /wa ff undo - this will persist thru a reload

currently implemented:

  • url on information tab
  • most of the action tab
  • most of the group tab
  • most non-position properties on display tab

there's still a lot to do, especially for custom options & condition options
image
(there's other changes to be made undo-able not caught by that grep)

@emptyrivers emptyrivers added 🎨 Enhancement This pull request implements a new feature. 👩‍🔬 Work in Progress This pull request is still being actively developed and shouldn't be merged. labels Feb 8, 2024
@emptyrivers
Copy link
Contributor Author

note that this is downstream of #4844, so I might close that pull request & just fold it into this one

@Stanzilla
Copy link
Contributor

note that this is downstream of #4844, so I might close that pull request & just fold it into this one

I think keeping it separate makes more sense, we just need to review the FF PR properly and test it, I haven't done that so far

@InfusOnWoW
Copy link
Contributor

Yeah, please keep them separate.

@emptyrivers
Copy link
Contributor Author

emptyrivers commented Apr 4, 2024

an update on progess:

majority of controls in WA options now perform undo-able actions. exceptions are:

  • some region/subregion options
  • (regular) group options
  • "exotic" things like MoverPicker, or TextEditor (though I imagine most folks who read this won't consider the code editor to be "exotic")
  • Duplicate/Add/Delete/Rename whole auras is not yet supported (delete will also immediately break the history until you reload the UI)

@emptyrivers
Copy link
Contributor Author

(note, this pull has #4982 merged in, for my own sanity. The actual changeset is smaller (though, honestly not that much smaller)

@krazyito65
Copy link
Contributor

Small graphical request: if either the 'undo' or 'redo' is empty (or the last item in the history), have the text 'fade' (optionally unclickable?) to indicate you can't go any further

functionality related to undo/redo will be hidden behind this feature until it's 'ready' for the LCD user

Signed-off-by: Allen Faure <afaure6@gmail.com>
Signed-off-by: Allen Faure <afaure6@gmail.com>
Signed-off-by: Allen Faure <afaure6@gmail.com>
Signed-off-by: Allen Faure <afaure6@gmail.com>
Signed-off-by: Allen Faure <afaure6@gmail.com>
mostly to accomodate how the commonoptions setall works

Signed-off-by: Allen Faure <afaure6@gmail.com>
…saction

Signed-off-by: Allen Faure <afaure6@gmail.com>
Signed-off-by: Allen Faure <afaure6@gmail.com>
Signed-off-by: Allen Faure <afaure6@gmail.com>
Signed-off-by: Allen Faure <afaure6@gmail.com>
Signed-off-by: Allen Faure <afaure6@gmail.com>
Signed-off-by: Allen Faure <afaure6@gmail.com>
Signed-off-by: Allen Faure <afaure6@gmail.com>
Signed-off-by: Allen Faure <afaure6@gmail.com>
Signed-off-by: Allen Faure <afaure6@gmail.com>
Signed-off-by: Allen Faure <afaure6@gmail.com>
array entry manipulation & reset to defaults aren't yet supported, and collapsed data needs to be handled better somehow

Signed-off-by: Allen Faure <afaure6@gmail.com>
Signed-off-by: Allen Faure <afaure6@gmail.com>
Signed-off-by: Allen Faure <afaure6@gmail.com>
detritus from an ancient (never actually released) time when there was "actionConditions" in auraData

Signed-off-by: Allen Faure <afaure6@gmail.com>
This might be wrong, or it might produce spurious empty tables. I'm not sure, though.

Signed-off-by: Allen Faure <afaure6@gmail.com>
Signed-off-by: Allen Faure <afaure6@gmail.com>
Signed-off-by: Allen Faure <afaure6@gmail.com>
Signed-off-by: Allen Faure <afaure6@gmail.com>
.
Signed-off-by: Allen Faure <afaure6@gmail.com>
Signed-off-by: Allen Faure <afaure6@gmail.com>
Signed-off-by: Allen Faure <afaure6@gmail.com>
only difference is one is shown when trigger.check == "update" and the other when trigger.check ~= "update"
presumably in the past, these were different in more significant ways

Signed-off-by: Allen Faure <afaure6@gmail.com>
Signed-off-by: Allen Faure <afaure6@gmail.com>
not doing customOverlayX because i think that's due for a migration to an array

Signed-off-by: Allen Faure <afaure6@gmail.com>
which is used for a lot of trigger options as well as load, apparently

Signed-off-by: Allen Faure <afaure6@gmail.com>
Signed-off-by: Allen Faure <afaure6@gmail.com>
(same semantics as table.insert/remove)

Signed-off-by: Allen Faure <afaure6@gmail.com>
Signed-off-by: Allen Faure <afaure6@gmail.com>
bonus: this means we don't need to ask for confirmation: user can just undo it
Signed-off-by: Allen Faure <afaure6@gmail.com>
Signed-off-by: Allen Faure <afaure6@gmail.com>
Signed-off-by: Allen Faure <afaure6@gmail.com>
Signed-off-by: Allen Faure <afaure6@gmail.com>
Signed-off-by: Allen Faure <afaure6@gmail.com>
Signed-off-by: Allen Faure <afaure6@gmail.com>
@InfusOnWoW InfusOnWoW added the 🆕 Feature Preview This is a draft intended to show a preview of an upcoming feature. label May 3, 2024
Copy link

github-actions bot commented May 3, 2024

An experimental build of WeakAuras with the changes in this pull request is available here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🎨 Enhancement This pull request implements a new feature. 🆕 Feature Preview This is a draft intended to show a preview of an upcoming feature. 👩‍🔬 Work in Progress This pull request is still being actively developed and shouldn't be merged.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants