FileSieve 4

  • Status Closed
  • Percent Complete
  • Task Type Feature
  • Category Plugin
  • Assigned To
    Joseph Cox
  • Operating System All
  • Severity Low
  • Priority High
  • Reported Version 4.35
  • Due in Version 4.36
  • Due Date Undecided
  • Votes
  • Private
Attached to Project: FileSieve 4
Opened by Joseph Cox - 22 February 2018
Last edited by Joseph Cox - 24 February 2018

FS#325 - Preserve datestamps for processed files

When files are copied or moved to their destination, their date stamps (Created, Modified, Written) are changed to the date and time of when FileSieve processed them.

This may sound like a bug (and initially did to me when this was reported), but the files are that copied/moved are entirely new files - not the originals that are being processed. FileSieve uses its own I/O code that supports buffer optimisation, async I/O, and operation progress; so it isn’t manually setting the date/time stamps like the OS does when it itself performs the copy or move.

This task entry is to add a new feature to FileSieve that preserves those date and time stamps.

I’m somewhat undecided whether this should be a core FileSieve setting or implemented as a Modifier. FileSieve settings aren’t configurable on a per-Profile basis and so will more than likely be a Modifier. The only potential issue with it being a Modifier is that FileSieve doesn’t set “default” Modifiers; coupling a FileSieve setting with the Modifier itself will provide user convenience in-spite of that fact FileSieve will become (loosely) coupled with a plugin.

Thanks to Olivier C. for reporting

Closed by  Joseph Cox
24 February 2018 11:04 AM
Reason for closing:  Implemented
Joseph Cox commented on 22 February 2018 09:17 PM

Despite this functionality being added as a Modifier, the code that actually sets the dates/times will be implemented within the FileSieve core as it will allow the Simulation window to display date/time changes.

There are now two nullable properties called SetCreationTime and SetLastWriteTime.

There's already a read-only property called LastWriteTime which is why the two new properties above are prefixed with Set, even though they are properties and not methods (as in the programming sense; not the FileSieve sense) as the Set prefix implies.


Available keyboard shortcuts


Task Details

Task Editing