The model is marked as unsaved when the client receives a changelog with any change. This includes SYSOUT changes, which are used to print messages to the console.
Instead, if the changelog only includes these changes which cannot change the model's state, then the model should not be marked as unsaved. This will improve the user experience by speeding up closing the model and removing the possibility for the user to be unsure of model changes.
The model is marked as unsaved when the client receives a changelog with any change. This includes SYSOUT changes, which are used to print messages to the console.
Instead, if the changelog only includes these changes which cannot change the model's state, then the model should not be marked as unsaved. This will improve the user experience by speeding up closing the model and removing the possibility for the user to be unsure of model changes.