# Unwanted File Timestamp Updates

**URL:** https://community.mp3tag.de/t/unwanted-file-timestamp-updates/59178
**Category:** Support
**Created:** [November 24, 2022, 8:00am UTC](https://community.mp3tag.de/t/unwanted-file-timestamp-updates/59178 "2022-11-24T08:00:09Z")
**Posts on this page:** 1
**Showing post:** 9

<div class="post-metadata">

### Author: ![Freddy](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/f/3d9bf3/32.png) [@Freddy](https://community.mp3tag.de/u/Freddy)
#### Post date: [November 26, 2022, 10:33am UTC](https://community.mp3tag.de/t/unwanted-file-timestamp-updates/59178/9 "2022-11-26T10:33:01Z")

</div>

See here: [Alteration Request: Make MP3Tag Not Touch Files Unless It Has To](https://community.mp3tag.de/t/alteration-request-make-mp3tag-not-touch-files-unless-it-has-to/59190)

> [@ohrenkino](#):
>
> Getting into edit mode for a field is action enough to assume that you as the user wanted to modify something.

Is it? You've never had a slip of the mouse?? That is a lazy assumption by the software and not user-friendly.

> [@ohrenkino](#):
>
> MP3tag does not compare whether you have made any changes.

Just because it doesn't, doesn't mean it couldn't. Write comparison need not be required, just a flag to register input has occurred and not just that the tag field was highlighted. I would also suggest nothing should be committed unless Enter/Return gets pressed (which is the data-processing meaning of that key!). People who do want changes committed regardless could have an option setting.

> [@ohrenkino](#):
>
> instead of changing MP3tag's behaviour it would be an idea to change a workflow

Change the user to suit the software rather than the software to suit the user? Hmm.

---

_[View the full topic](https://community.mp3tag.de/t/unwanted-file-timestamp-updates/59178)._