Quote:
Originally Posted by arspr
Entering brainstorming mode, outside team, non-expert, ignorant role:
Just in case you were so focused in solving the issue in an orthodox, "correct" way that you didn't think of this possible way. Although it has a probability of 99% of being just plain nonsense.
About killing the trailing obsolete branch of checkpoints: When you perform any automated action you have already set an add-checkpoint action which actually removes that branch. So AFAIK you only need to catch the manual "typing" event, because any automated one is already solved.
And thinking about that, it looks pretty similar to me to whatever mechanism you have implemented to detect the file-has-been-modified event. I mean when you open the book you somehow detect when the user modifies any text file, and then you put the pencil icon on its tab and you activate the save button.
I know it's not exactly the same case but, couldn't you "port" that detecting tool to the checkpoint cleaning?
|
I believe that's what he tried. The
changelog for removal of this is:
Code:
if is_modified:
self.set_modified()
- self.global_undo.truncate()
- self.update_global_history_actions()