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 stack is getting disordered #6635

Closed
2 tasks
sylwiabr opened this issue May 10, 2023 · 3 comments
Closed
2 tasks

Undo-redo stack is getting disordered #6635

sylwiabr opened this issue May 10, 2023 · 3 comments
Assignees
Labels
--bug Type: bug p-lowest Should be completed at some point

Comments

@sylwiabr
Copy link
Member

Discord username

No response

What type of issue is this?

Transient – Occurring only once

Is this issue blocking you from using Enso?

  • Yes, I can't use Enso because of this issue.

Is this a regression?

  • Yes, previous version of Enso did not have this issue.

What issue are you facing?

We were working for a longer time with a project (can attach later a video from a full workflow if needed):

  1. opened an existing project
  2. added few nodes at the beginning of the workflow
  3. worked a little with the graph
  4. moved down the graph
  5. disconnected two nodes
  6. another node was moved
  7. we tried to undo last actions - it took us 7 undo to get the connection back
  8. before we got to reconnecting the node, the nodes we added at the beginning of the workflow were removed

Expected behaviour

Right order in the undo stack

How we can reproduce it?

No response

Screenshots or screencasts

No response

Enso Version

develop 10.05

Browser or standalone distribution

Standalone distribution

Browser Version or standalone distribution

standalone

Operating System

Windows

Operating System Version

No response

Hardware you are using

No response

@sylwiabr sylwiabr added the p-high Should be completed in the next sprint label May 10, 2023
@Akirathan
Copy link
Member

I tried to reproduce it on larger project Enso_201 and I am unable to reproduce it. Video would be nice, if you have some.

@Akirathan Akirathan removed the triage label May 11, 2023
@farmaazon
Copy link
Contributor

farmaazon commented May 19, 2023

I think this should be considered a part of #6435. @mwu-tow please close this one if I'm right.

@farmaazon farmaazon moved this from ❓New to 📤 Backlog in Issues Board Aug 7, 2023
@sylwiabr sylwiabr added p-lowest Should be completed at some point and removed p-high Should be completed in the next sprint labels Aug 30, 2023
@farmaazon
Copy link
Contributor

Closing, as we use different tool for undo redo in GUI2. Any issue with it should be reported as a new task.

@farmaazon farmaazon closed this as not planned Won't fix, can't repro, duplicate, stale Feb 27, 2024
@github-project-automation github-project-automation bot moved this from 📤 Backlog to 🟢 Accepted in Issues Board Feb 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
--bug Type: bug p-lowest Should be completed at some point
Projects
Archived in project
Development

No branches or pull requests

4 participants