We deliberately changed this as there was a design inconsistency as although the > Save Project > command got grayed-out when the project was “clean” (i.e. in a saved state with no changes) it was > always > possible to use its > Ctrl + S > shortcut regardless of the “clean”/“dirty” state of the project.
It doesn’t seem reasonable to remove this nice “hidden” feature (i.e. “Save Project” menu entry is grayed-out when project is clean) because it’s possible to use Ctrl-S shortcut to save a clean project “again”. If Ctrl-S shortcut currently re-saves an already-saved project, this is an issue of Ctrl-S shortcut, not issue of the Save Project menu entry. We can properly fix Ctrl-S shortcut instead of removing another feature. We can let Ctrl-S do nothing if the project is already saved (i.e. is already in clean state).
Maybe what you really need is a permanently shown visual cue that shows the “clean”/“dirty” state of the project - but that would
a) be an enhancement request - and
b) many folk would likely regard it as unnecessary clutter in the GUI.
This is another good idea. We can easily tell the project state (clean vs. dirty) with a visual cue such as a little dot (e.g. green for clean state, red for dirty state).