https://bugs.kde.org/show_bug.cgi?id=444309

--- Comment #7 from tomtomtomreportin...@gmail.com ---
By the way, I'm not sure if this the right place (or time, this late into 5.0
development) for a suggestion, but: 

Instead of an explicit save button/autosaving on quit to prevent versioning
spam, would it be a bad idea to make it so that it only keeps the original and
latest modified version of that particular palette for the session, so that it
can autosave on modification again? This would also prevent changes being lost
from crashes, and perhaps the save button could be replaced with a reload
button.

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to