Bug 450942 - Save button improvement
Summary: Save button improvement
Status: RESOLVED DUPLICATE of bug 95849
Alias: None
Product: kate
Classification: Applications
Component: general (show other bugs)
Version: 21.12.2
Platform: Other Linux
: NOR wishlist
Target Milestone: ---
Assignee: KWrite Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-02-27 22:43 UTC by medin
Modified: 2022-08-16 13:36 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description medin 2022-02-27 22:43:34 UTC
It would be cool if the save button in toolbar becomes disabled after saving and return enabled upon any further edit, the current indicator at left bottom is hard to see and make my neck hurts by looking at bottom then clicking on save button at top.
Comment 1 Christoph Cullmann 2022-02-28 06:38:38 UTC
It is a design decision to always be able to save, e.g. to touch a file.

Therefore sorry, we will not disable the save action.

There are enough other indicators like changed window/tab caption.
Comment 2 medin 2022-02-28 09:24:16 UTC
(In reply to Christoph Cullmann from comment #1)
> It is a design decision to always be able to save, e.g. to touch a file.

It's really weird and not logical at all to save non modified file, I never encountered a word processor or a text editor that has this behavior. This situation could apply to "Save as" button where saving same unmodified data to another path is necessary but to force it on "Save" it seems not intuitive at all.
Comment 3 Christoph Cullmann 2022-02-28 09:34:00 UTC
Atom does it the same way, VS Code, too.
Save is there always active.
I don't see why we should handle this differently.
And we do handle it that way even a decade longer then these editors do exist.
Comment 4 Waqar Ahmed 2022-08-16 13:36:11 UTC

*** This bug has been marked as a duplicate of bug 95849 ***