2018-07-05, 06:58
Another user recently reported an issue with lost data, inadvertently overwritten by tMM. There have been some things that bother me a bit, so I thought I would propose them for consideration.
1) The ability to "lock" images / artwork, especially the poster and fanart. When you do a new scrape, those items are often overwritten / replaced with whatever is selected by tMM or the scraper, not sure how it works exactly. But many customize these, or make specific selections and having them overwritten can easily waste a lot of bandwidth and time and file writes for no intended reason. Write actions being more relevant to those with SSD and/or with backups, especially real time backups. Even a replacement of an image with the same image will prompt the backup to see a change.
2) The ability to lock / prevent the "initialize database" menu item. Although not easy to accidentally click, it would be nice for some redundant safety measures to be there to prevent inadvertent use.
3) Automatic file backup. This is 2 parts:
a) Each time tMM starts (maybe given the setting of a variable to turn on and off), tMM automatically creates a backup of the starting database files. This would be sort of how system and programs logs work, where each time you start the system or program, the former log is saved and you start with a fresh and empty log. This would just make a integrated one prior backup at all times.
b) When tMM overwrites a NFO file, like movie.nfo, it creates a movie.nfo.bak before the overwrite.
These are just some items I thought of that I believe most all users would see a benefit in... especially if you could turn them on and off so you are not forced to change anything should you desire not to.
1) The ability to "lock" images / artwork, especially the poster and fanart. When you do a new scrape, those items are often overwritten / replaced with whatever is selected by tMM or the scraper, not sure how it works exactly. But many customize these, or make specific selections and having them overwritten can easily waste a lot of bandwidth and time and file writes for no intended reason. Write actions being more relevant to those with SSD and/or with backups, especially real time backups. Even a replacement of an image with the same image will prompt the backup to see a change.
2) The ability to lock / prevent the "initialize database" menu item. Although not easy to accidentally click, it would be nice for some redundant safety measures to be there to prevent inadvertent use.
3) Automatic file backup. This is 2 parts:
a) Each time tMM starts (maybe given the setting of a variable to turn on and off), tMM automatically creates a backup of the starting database files. This would be sort of how system and programs logs work, where each time you start the system or program, the former log is saved and you start with a fresh and empty log. This would just make a integrated one prior backup at all times.
b) When tMM overwrites a NFO file, like movie.nfo, it creates a movie.nfo.bak before the overwrite.
These are just some items I thought of that I believe most all users would see a benefit in... especially if you could turn them on and off so you are not forced to change anything should you desire not to.
