Jump to content
Artem F

History of object

Recommended Posts

Artem that is an INSANELY great idea! Finely granular or object-based history (undo/redo) +100

 

 

It can be very cool feature if I can select object and view history of his changes ignoring general history. What do you think about it?


2017 15" MacBook Pro 14,3 w/ Intel 4 Core i7 @ 2.8 GHz, 16 GB RAM, AMD 455 @ 2 GB, 512 GB SSD, macOS High Sierra

2018 11" iPad Pro 256 GB, latest iPadOS public beta

Share this post


Link to post
Share on other sites

an INSANELY great idea!

 

Or an insanely insane one! Complex drawings can have literally thousands of objects: I don't think it's generally useful, let alone practical, to have the software keep track of every little change to every single one of them.


Alfred online2long.gif
Affinity Designer/Photo/Publisher 1.7.3.481 • Windows 10 Home (4th gen Core i3 CPU)
Affinity Photo for iPad 1.8.2.174 • Designer for iPad 1.8.2.4 • iPadOS 13.3.1 (iPad Air 2)

Share this post


Link to post
Share on other sites

Your history have already write all info about all object. And I want using only history info about one object.

And I'll bet. There have been cases when you made a number of revisions, but decided to revert back without overwriting the new actions. And in this case such history can help you.

 

Now, of cource, I can use hack. Revert history to needed state of object cmd+c, then to end of history and cmd+v. But it is not such content-depending

Share this post


Link to post
Share on other sites

Artem I'm not sure if this is in the Feature Request forum (in on my smartphone) but you should DEFINITELY add this idea. Ad far as UI, It could be a simple switch in the History palette to switch from document History to Object history...

 

Your history have already write all info about all object. And I want using only history info about one object.

 

And I'll bet. There have been cases when you made a number of revisions, but decided to revert back without overwriting the new actions. And in this case such history can help you.

 

Now, of cource, I can use hack. Revert history to needed state of object cmd+c, then to end of history and cmd+v. But it is not such content-depending


2017 15" MacBook Pro 14,3 w/ Intel 4 Core i7 @ 2.8 GHz, 16 GB RAM, AMD 455 @ 2 GB, 512 GB SSD, macOS High Sierra

2018 11" iPad Pro 256 GB, latest iPadOS public beta

Share this post


Link to post
Share on other sites

I wonder if it would be possible for the history steps to be independent of each other? Here's my idea: If the steps are independent and the user could name the steps so you know what object they pertain to, then if you wanted to you could uncheck a step you wanted removed without affecting the rest of the art. I say uncheck because if you wanted to you could recheck it to put the step back or if you did something else to the object at that point, the checked step would be removed and your latest action would be recorded. Don't know if it's too complex to be done and it would require the user to name each step to make it work.

 

Just a thought...

Share this post


Link to post
Share on other sites

Don't want to put too much of a damper on this....

 

While it sounds wonderful, a non-linear undo history is very very difficult to implement.  Our history stack relies on deterministic state at each stage - it's the only way to make sure of data integrity and predictability without doing a lot of costly validation.  If you could optionally undo, remove or change random bits of the history the deterministic state does not exist - a previous history change invalidates the predictable state of the document later in the history.

 

Many years ago I worked on a project where someone insisted we tried to implement non-linear undo.  It was a total failure.  We went back and rewrote everything with a conventional linear undo stack.

 

Some tools implement something similar to non-linear undo through modifier stacks, but these are notoriously hard to understand from a user perspective.


SerifLabs team - Affinity Developer
  • Software engineer  -  Photographer  -  Guitarist  -  Philosopher
  • iMac 27" Retina 5K (Late 2015), 4.0GHz i7, AMD Radeon R9 M395
  • MacBook (Early 2015), 1.3GHz Core M, Intel HD 5300
  • iPad Pro 10.5", 256GB

Share this post


Link to post
Share on other sites

Just trying to get my head around how this would work, Ben.

 

Do y'all keep track of each objects ID in AD? If so, if there is an object selected on the artboard, would it be possible to filter the history by object ID? And if nothing is selected, then present the history fully as now?

 

Mike

Share this post


Link to post
Share on other sites

Ben, thanks for the explanation. So history is done based on the changes made to the document and the deterministic state is the total document? I gather it's not practical to record history based on objects instead of documents? So if I understand your explanation, if I delete an object and the history is non-linear (or object oriented), there isn't a way to easily validate that deletion at a later point in history. Without linearity, the means that the only way to handle history would be to basically replay all the previous steps up to the selected point? And I presume that the issue is compounded since history can be saved within the document and that document can be opened in multiple apps.

Share this post


Link to post
Share on other sites

We generally use pointers to identify an object. They are unique and we don't have to use arbitrary ID values that require special management.

 

Unfortunately, identifying what has been changed in a given command can be quite involved.  Without giving away too much about our architecture, our commands follow a number of different forms: some do one-off calculation and swap data, others have to do some work, in order to do/undo.  In order to work out if object X is affected by a command would require knowledge of how object X exists as it is affected by a sequence command.  What is logically an object that goes through changes might actually be a totally different memory object under the hood between commands.

 

So, tracking an object through history is not so straight forward.


SerifLabs team - Affinity Developer
  • Software engineer  -  Photographer  -  Guitarist  -  Philosopher
  • iMac 27" Retina 5K (Late 2015), 4.0GHz i7, AMD Radeon R9 M395
  • MacBook (Early 2015), 1.3GHz Core M, Intel HD 5300
  • iPad Pro 10.5", 256GB

Share this post


Link to post
Share on other sites

Ben, thanks for the explanation. So history is done based on the changes made to the document and the deterministic state is the total document? I gather it's not practical to record history based on objects instead of documents? So if I understand your explanation, if I delete an object and the history is non-linear (or object oriented), there isn't a way to easily validate that deletion at a later point in history. Without linearity, the means that the only way to handle history would be to basically replay all the previous steps up to the selected point? And I presume that the issue is compounded since history can be saved within the document and that document can be opened in multiple apps.

 

Something like that, yes.   ;)

 

Trivially, if command A creates an object, and command B sets that objects colour, what happens if I remove command A from the history???

 

Non trivially - with a more complicated scenario - it's a total nightmare.


SerifLabs team - Affinity Developer
  • Software engineer  -  Photographer  -  Guitarist  -  Philosopher
  • iMac 27" Retina 5K (Late 2015), 4.0GHz i7, AMD Radeon R9 M395
  • MacBook (Early 2015), 1.3GHz Core M, Intel HD 5300
  • iPad Pro 10.5", 256GB

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


×
×
  • Create New...

Important Information

Please note the Annual Company Closure section in the Terms of Use. These are the Terms of Use you will be asked to agree to if you join the forum. | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.