Duplicate with date stamp

[avsfan]

Hi,

I really like the Ctrl-D "Copy Here With Suffix Number" functionality (and was really glad when I discovered it)!

However, I almost always end up changing the suffix from the -01 to yymmdd, and then, if it happens more than once in a day, adding a letter suffix as well i.e. the file foo.txt would first be duplicated as foo-060816.txt, then foo-060816a.txt etc...

I would love to be able to have this functionality automatically (or some close variation thereof)...

Thanks for listening!

andy

[zridling]

I agree. When working with versions and photo editing, this is a major time saver.

[admin]

I really like the Ctrl-D "Copy Here With Suffix Number" functionality (and was really glad when I discovered it)!

Oh yes, me too! I would buy the program for this feature alone.

Duplicate with date stamp, yeah yeah yeah! Ctrl+Shift+D is still free as far as I see...
I'm not sure about the suffixed letters: what you do after "z"?? I'd rather append a number.

[avsfan]

Duplicate with date stamp, yeah yeah yeah! Ctrl+Shift+D is still free as far as I see... Cool
I'm not sure about the suffixed letters: what you do after "z"?? I'd rather append a number.

Ctrl-Shift-D sounds good to me!

I suppose a number would be fine -- the letters work for me since on a given day I rarely will save more than 10 dups...

Since I've been using letters, that's my initial preference, but it seems that "foo-060816-01.txt" (or maybe foo_060816-01.txt ...) would be just as effective for what I do (and since I've learned to change a lot of the way I do things since I started using XY, what's one more? )

Thanks! Looking forward to this one!

andy

[avsfan]

This new feature is great! thanks much for adding it!

I think that it'd be even better if the date were based on the last modified date of the file rather than today's date (even though in most cases the two dates will be the same)... This way if I am going to start working on a file that I worked on previously, I can easily capture the date that it was last modified....

Thanks again, Don -- you ROCK!

andy

[admin]

I think that it'd be even better if the date were based on the last modified date of the file rather than today's date (even though in most cases the two dates will be the same)... This way if I am going to start working on a file that I worked on previously, I can easily capture the date that it was last modified...

But the mod date is already stored in the file system. Duplicating this info in the file name can lead to conflicts/confusion. I think it's better to have the Date Suffix as "Last Back-upped".

[avsfan]

But the mod date is already stored in the file system. Duplicating this info in the file name can lead to conflicts/confusion. I think it's better to have the Date Suffix as "Last Back-upped".

I think I see your point, though the way I usually work with this type of thing, I use those backup files exclusively for reference (so heck, we could even make them read-only when they're backed up!)

Actually, the more I think about it, the less sense it makes to me (again, for the way that I use it) to have the date of backup in the file name. If I don't have the details view open, I'd like to know when that backup was last modified (obviously if the file gets changed after the rename, that's a problem, but that will be an issue any time you start putting dates/times into filenames...) And, if the files start out with the same date (i.e. using the file mod date), then if the name doesn't match the mod date, it's clear that either the file was modified or renamed (but at least they start out consistent... ).

I don't know if this reasoning is very persuasive, or if it's worth adding an option for it, but I'd sure like to see it work with the file date rather than the current date (such as if I modified a file 2 months ago and then come back today to start working on it, I'd like to have it date-stamped with the date two months ago so I'll have a relative idea of how long ago I was working with it just based on its name...)

OK... I guess that's (more than) enough... I'd be glad to let you know how I feel on this issue if you're interested....

Thanks, Don!

andy

[j_c_hallgren]

If I understand this topic correctly, I can easily see the benefit of having a selectable option to either use curr date or file last modif date...because...if I have some digital photo files that were shot at various prior dates, I might wish to have those dates embedded in the file name, instead of todays date being applied to it...that's the best example I can think of...ok?

[admin]

... I've learned to change a lot of the way I do things ...

Me learn too: now it's the modified date. You convinced me.

[avsfan]

Me learn too: now it's the modified date. You convinced me.

Excellent! This does *exactly* what I need!

Thanks for the quick work! (and for being flexible!)

Great job, as always!

andy

[jacky]

... I've learned to change a lot of the way I do things ...

Me learn too: now it's the modified date. You convinced me.

Ok was reading through the recent changes... so just to make sure, this only apply here, Batch Rename still uses the current date right?

[admin]

... I've learned to change a lot of the way I do things ...

Me learn too: now it's the modified date. You convinced me.

Ok was reading through the recent changes... so just to make sure, this only apply here, Batch Rename still uses the current date right?

Yes. Hm. I see it's a bit inconsequent/confusing... I personally will hardly use datestamp-renaming. Who does and what for?

[jacky]

Yes. Hm. I see it's a bit inconsequent/confusing... I personally will hardly use datestamp-renaming. Who does and what for?

Same here I won't say anything....

But, while on subject, about the two settings PostfixNum & PostfixDate; it seems one cannot use a space as first character. Well, dunno if it should be listed as bug or wish, but either way I'd like a way to do so

hmm after a few more tests i changed my mind, it is a bug! I say this because using:

Code: Select all

PostfixNum=" - 00"

does work, XY uses the space and it's all great.
But, when saving the config XY saves with the space but without the quotes; so on next restart the first space is gone

[admin]

hmm after a few more tests i changed my mind, it is a bug!

It was a bug. And it uncovered another bug as well (UnitByte... see history). Good find!