2015-04-22, 16:06
You can use a utility found here in the forum to accomplish what you want (re-scanning NFO files) - http://forum.kodi.tv/showthread.php?tid=158373
I am using it for exactly this purpose (among other things), which leads me to my question...
When TMM updates an NFO file (Windows 7) should the (NFO) file's modified date change? It seems that it isn't - I edited a movie, re-wrote the NFO, checked that the change that I made was in the new NFO file). But the modified date hadn't actually changed...
Since texturecache relies on that date to determine if the NFO file has changed (to rescan the item), it would be great if this worked..
<edit> - Further research - I *think* texturecache.py is actually looking at the CREATE date (not the modified date). So, maybe this is more of a feature request for TMM.. When TMM re-writes an NFO file, could it delete the original NFO and replace it with a new one, thus setting the CREATION date to the current date/time?
I am using it for exactly this purpose (among other things), which leads me to my question...
When TMM updates an NFO file (Windows 7) should the (NFO) file's modified date change? It seems that it isn't - I edited a movie, re-wrote the NFO, checked that the change that I made was in the new NFO file). But the modified date hadn't actually changed...
Since texturecache relies on that date to determine if the NFO file has changed (to rescan the item), it would be great if this worked..
<edit> - Further research - I *think* texturecache.py is actually looking at the CREATE date (not the modified date). So, maybe this is more of a feature request for TMM.. When TMM re-writes an NFO file, could it delete the original NFO and replace it with a new one, thus setting the CREATION date to the current date/time?
