When daylight savings time changes, that makes the displayed (local) timestamps of every file change. It does not, however, change the underlying UTC-based last-write timestamps (on NTFS partitions).
It would be nice if BC's "file on disk changed" recognizer used the UTC timestamp rather than the displayed/local timestamp, so it didn't report all open files as having changed twice a year.
I saw this problem in Notepad++ (all my open files were reported as having been changed, tho none had been) as well -- so you're not alone. But you could fix this, I think.
(It might be that Windows reports these as changes if you're using the "file system change notification" mechanism. But you could ignore them when both UTC timestamp and size are unchanged.)
Thanks for listening.
It would be nice if BC's "file on disk changed" recognizer used the UTC timestamp rather than the displayed/local timestamp, so it didn't report all open files as having changed twice a year.
I saw this problem in Notepad++ (all my open files were reported as having been changed, tho none had been) as well -- so you're not alone. But you could fix this, I think.
(It might be that Windows reports these as changes if you're using the "file system change notification" mechanism. But you could ignore them when both UTC timestamp and size are unchanged.)
Thanks for listening.
Comment