Version 4 won't set timestamps programmatically
I bought Advanced Renamer specifically because it allowed setting a file's modified (and/or creation date.)
And this worked well enough in version three. For example:
Script Start
------------
newD = new Date();
newD.setHours (newD.getHours() - 1); // Start 1 hour back to reduce chance of "Future" files.
newD.setSeconds (newD.getSeconds() + index); // Increment seconds by one to avoid time collisions.
item.newModifiedDate = newD; // This looks good in preview column but does not actually set the date of the file!
return item.newBasename;
------------
End Script
Followed by a Timestamp step, set to "Image date and time" (Insane but it was needed!)
But with version 4, no attempt to set newModifiedDate works.
I could work around it if Timestamp could be set off a pattern in the *New* Filename. That seems like it would be an easy thing to add.
PLEASE:
1) Fix newModifiedDate and newCreatedDate
2) Add Timestamp off of the New Filename
And this worked well enough in version three. For example:
Script Start
------------
newD = new Date();
newD.setHours (newD.getHours() - 1); // Start 1 hour back to reduce chance of "Future" files.
newD.setSeconds (newD.getSeconds() + index); // Increment seconds by one to avoid time collisions.
item.newModifiedDate = newD; // This looks good in preview column but does not actually set the date of the file!
return item.newBasename;
------------
End Script
Followed by a Timestamp step, set to "Image date and time" (Insane but it was needed!)
But with version 4, no attempt to set newModifiedDate works.
I could work around it if Timestamp could be set off a pattern in the *New* Filename. That seems like it would be an easy thing to add.
PLEASE:
1) Fix newModifiedDate and newCreatedDate
2) Add Timestamp off of the New Filename
Reply to #1:
Hallo Randy,
Op dit forum wordt bijvoorkeur gecommuniceerd in het Engels.
De meest ingewijde forumleden zijn Engelstalig, m.a.w. wil je een correct antwoord ontvangen, schrijf dat je reactie in het ‘Engels’.
Hallo Randy,
Op dit forum wordt bijvoorkeur gecommuniceerd in het Engels.
De meest ingewijde forumleden zijn Engelstalig, m.a.w. wil je een correct antwoord ontvangen, schrijf dat je reactie in het ‘Engels’.
Reply to #1:
Version 4 uses a different JS engine with a different integration, with the consequence that you cannot set newModifiedDate, like you could in version 3. The only fields you can change are newName and newPath.
But can you do the same without using a script? I'm not sure what you want the program to do. Are you trying to generate unique timestamps?
Version 4 uses a different JS engine with a different integration, with the consequence that you cannot set newModifiedDate, like you could in version 3. The only fields you can change are newName and newPath.
But can you do the same without using a script? I'm not sure what you want the program to do. Are you trying to generate unique timestamps?
Reply to #3:
Yes in that example, I am generating unique, sequential timestamps.
I have other scripts that set the dates in other ways. I use newModifiedDate a lot. I had to revert to version 3.
Please fix/restore/add newModifiedDate and newCreatedDate.
But if you add Timestamp off of the *New* Filename, that is an acceptable workaround. And it seems like it should be very easy to do.
PS: Are we supposed to get forum emails of new replies? I'm not seeing any.
Yes in that example, I am generating unique, sequential timestamps.
I have other scripts that set the dates in other ways. I use newModifiedDate a lot. I had to revert to version 3.
Please fix/restore/add newModifiedDate and newCreatedDate.
But if you add Timestamp off of the *New* Filename, that is an acceptable workaround. And it seems like it should be very easy to do.
PS: Are we supposed to get forum emails of new replies? I'm not seeing any.