Vectorworks Blog: Autosave Preferences

[Diamond]

Regarding today's blog post…

 

http://blog.vectorworks.net/020620archpreferences?

"Session > Maximum number of Undos > 42

Vectorworks tech support recommends a maximum of 25 undos, but I like to live on the edge, so I have mine set to 42 (fellow Douglas Adams fans might appreciate this). For my needs, I also have “Undo View Changes” set to “Grouping Similar View Changes.”"

 

I was not aware of this recommendation. Why is this? Beyond memory usage, is there another reason such as stability?

 

[Jim W]

Yup yup, the higher you set the number of undos, the slower things can go. Especially when you're working on complex multi-level container objects like Solid Additions or groups within groups within groups. 

[Diamond]

Before reading this article it never occurred to me that Undo history could be causing (m)any of my issues. Cheers.

[DBruhnke]

39 minutes ago, Diamond said:

Before reading this article it never occurred to me that Undo history could be causing (m)any of my issues. Cheers.

@Diamond Undo's can be a memory hog. Had a user complaining that they had constant beachballs. Come to find out they had set the Undo to the maximum of 100.

Changed that to 25 and "changed" their workflow to not need that many undo operations and bye bye beachballs.

#Technology

 

 

[Diamond]

Thanks for the comments
 

On 2/11/2020 at 5:38 AM, Jim W said:

Especially when you're working on complex multi-level container objects like Solid Additions

At least the new solids modelling history negate the need for such long Undo history.