Undo/ Redo issues



  • The undo function causes me a lot of problems.
    It is unpredictable.
    In some of the topics I have already mentioned this.

    1. Taking a step back using CTRL + Z on the keyboard also affects the settings, e.g. stroke thickness. When I use the same shortcut on the tablet, the stroke remains unchanged.
    2. It happens that when I want to go back one operation, the program also deletes the actions that I did a long time ago. No chronology. However, when I try to recover them using redo, the elements do not appear or copies of completely different unrelated ones appear. I can't predict what's going to happen next, or what consequences undoing will have, which makes me save files frequently.
    3. Redo Icon in left corner doesn't work. Sometimes its faded when it shouldn't be. I can use it from Edit menu.

    I don't know how other users experience using it, but I run into many problems that sometimes I can't even describe. On my computer. Windows version is definitely not ready for trouble-free operation.
    I will try to record, for example, an hour of work to show what surprises it offers



  • @encart said in Undo/ Redo issues:

    I don't know how other users experience using it, but I run into many problems that sometimes I can't even describe.

    @encart

    You are not alone.

    I'm currently using a Mac (Intel), and I too have had unexpected things happen, including Undo/Redo, but many other things as well. Crashes too.

    I'll ask myself "Is this a bug?" "Do I not understand how this is suppose to work?" "What the heck is going on?" "This can't be right". "If this is how it is supposed to work, it needs serious improvement", etc., etc.

    I've even thought, "It must be just me, because no one else has posted the problem I've noticed"**.

    Sometimes upon further examination, I discover I did indeed do something wrong or misunderstood how something was supposed to work in VectorStyler. But many other times I am totally perplexed.

    Some of the wierd stuff seems to happen sporadically.

    I admit there I times when I haven't posted something because I thought maybe it was user error and I'd look like an idiot🤣 because I just flat out misunderstood something or simply had a hard time replicating the problem so I felt It wouldn't be of much value to post it. I don't want to send the developer on wild goose chases.

    I just keep reminding myself that if I (or anybody else) doesn't report this stuff, we are doing ourselves a disservice as the problem(s) will go unresolved.

    Just wanted to let you know that you are not losing you mind!☺


  • administrators

    @encart One thing that would help replicating this is to enable the Store History ion the Document Setup -> General section.
    This will also store the undo/redo steps in the file, and then these can be replicated easier.

    1. in some cases, several stroke width changes are merged into a single undo. this might be the case here, or not, I have to replicate this one.
    2. this looks like a bug. there might be some action that breaks the undo/redo stack.
    3. again a bug, probably the button activation is not updated.

    I will try to replicate these ones, but a file with stored undo/redo history might help a great deal.



  • I would like to use the program for larger projects, but have already lost many hours due to bugs that cause irreversible changes. That's why all my work at VS now is testing and catching bugs.
    Agree that the crash has appeared more frequently since the last two or three builds. Today VS crashed when I wanted to use the Stroke Width Brush on a circle, but then I couldn't reproduce it.
    I assumed that these are the flaws of the Windows version only.
    Sometimes I have the impression that there are so many of these functionalities and they overlap with each other that repairing one causes the error of another.
    It's great that the program has many functions, but you need to make sure that the basic functions work as they should. Without it, it will be a problem to encourage users of other programs to switch.
    The number of dependencies a new user has to learn is very large and dissuasive. The learning curve is quite long. Even though I've been playing VS for a few months, I still feel like I'm at the beginning of my journey. This is also because of
    what @Vector-Rock said. It is not known what is intended or what is the error. You have to focus on the basic functionalities to make them work reliably, intuitively and simply. This is the first necessary step to get people to get into VS



  • Again.

    I was drawing a flower with a pencil. When I was making the 5th petal, I wanted undo. After pressing the last petal, the first and the second one disappeared. 3 and 4 remained in place. Redo and refreshing didn't work. After pressing Undo several times, the application is creashed.

    Have no file beacuse app crashed.



  • Now I have file and video and the file. https://streamable.com/4hkhk0



  • Could you check if you can reproduce that issue?

    https://recordit.co/VTFphQvvpf

    At the beginning I thought that this only happens by using the keyboard shortcut CTRL + Z, but by using the menu and icon also.


  • administrators

    @encart This new one can be replicated.


  • administrators

    @encart The break apart undo / redo issue should be fixed in build 1.0.041.