I’ve seen this a couple of times in the past month:
The history object was copied text that I edited via doubleclicking. Then this popup at the next time I run SaveSmall. I always use save small - the current file is big and slow to save even without render meshes.
Does this make any sense? It doesn’t seem like SaveSmall should have have anything to do with history. Maybe this has always been there and I am just using history more for a current project? It’s not very repeatable though, I did this same process a lot of times, and just happened once today.
That does not make any sense to me off hand… I’ll test. So, I can reproduce this- the real history breakage is from the editing of the text… I am surmising that the next actual command (as opposed to the double-click) was SaveSmall and this is how the warning box gets its info about what broke History.
Thanks, Pascal. And it does seem repeatable here actually. Start new file, add some text. Drag+alt or copy, then doubleclick and edit the copy. SaveSmall brings up the warning.
Ah, I see. Must have only saved right after the edit the times it happened. I did notice the edit didn’t break history, but didn’t put 2 and 2 together.
