Giter Club home page Giter Club logo

Comments (4)

dmonad avatar dmonad commented on June 11, 2024

The meta property is intended to store information about the "before-state" that is required to restore exactly that state. One example would be to store the cursor position that should be recovered when undo is triggered. When you undo several undo-items at once (e.g. because they are merged), you usually only want to recover the first meta state.

Hence, we intentionally discard the meta properties of stack items that are merged. Only the first meta generated should survive.

There might be an argument why stack-items should be merged. However, this would be confusing to most, as the first stack-item created should always be the "authority". I suggest that you store all relevant information on all meta states.

If this seems unfeasible to you, can you please explain your use-case?

from yjs.

davidlessonup avatar davidlessonup commented on June 11, 2024

First of all, apologies for the late reply.

The meta property is intended to store information about the "before-state" that is required to restore exactly that state. One example would be to store the cursor position that should be recovered when undo is triggered. When you undo several undo-items at once (e.g. because they are merged), you usually only want to recover the first meta state.

The issue we're having lies somewhere with this.

Let's consider an undo action:
When the stackItem is popped from undo the beforeState sync doesn't apply in time for the creation of the redo stackItem meta.

Shouldn't the previous meta be accessible for cases like this? Because when moving something from a stack to another more often than not you could be creating the same meta information

from yjs.

dmonad avatar dmonad commented on June 11, 2024

Let's say:

  • Before performing a change, the cursor is at position X.
  • Before performing the second change, the cursor position is at position Y.
  • These two changes are merged into a single undo item.

When I hit undo, I expect that the cursor position is at position X.

I don't see a need to preserve the state "cursor it at position Y", because that change is merged into the first undo-stack item. We usually only want to restore a single state.

This is what the undo-manager was designed for. I'm not saying that we can't extend it. But I need to understand the problem first.

Now let's say we want to we want to preserve the meta of the second change. Clearly, we don't want to restore position X AND Y. So how exactly should "metas" be merged? Please be more specific.

This is an extremely generic ask and I honestly don't have an incentive to fix your specific problem. I'm not sure a solution would be beneficial to all.

from yjs.

davidlessonup avatar davidlessonup commented on June 11, 2024

Merging aside, and like you mentioned above, meta is supposed to store a "before-state" (which in redo it can be considered an"after-state")

Here's an example of what is trying to be done. When the user redos an action it should restore the position to where it was before the undo. No matter how long the user takes between the actions.

Also due to the current order of events (StackItem gets added before pop), it is not possible to just create a new meta directly with the correct position.

image

from yjs.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.