Missing description field on any -(0000) saves

[wmoritz]

Any time nb650B13 saves a duplicate file with the -(000x) such as Tommy1-(0001).jpg it will not save a description field data text with that file.
Only Tommy1.jpg gets a description field data text saved duplicate Tommy1-(0001).jpg has a blank description field data text.
Simple enough?

[wmoritz]

This feature is important in that it can be a sort field when file duplicate are the same please fix...

[Quade]

Sorry forgot to reply to this.

I'll have to look into it. I'm skeptical that it's not saving. I think what's happening is that it's saving with the original filename and not the renamed filename.

[wmoritz]

Newbin Pro as I remember earlier in the beta versions use to save the description because I utilized that feature to sort when I could not sort on the file name. I could be wrong I know it did with version nb432. I miss it...

[wmoritz]

By the way, it does save with the first save. Just no duplicates does it save the description to.

No I get it - nb saves the dupe but overwrites the description again to the non (000x), plain file, instead of writing it with the (000x) filename that makes sense me.

[wmoritz]

Any chance a fix in the next beta version?

[Quade]

I looked into it and there's no easy fix for this.

Newsbin renames the files that's already on disk and not the one that's currently downloading. Because of that the description file will always be wrong because the current file description already has the original file in it. It renames this way because autopar and repair will wipe out the original filename when it renames to get the proper filename for repair so, this preserves the original file even when autopar is doing renames.

Now, I might be able to write two files to description when I rename. The current file and a record for the renamed file but, that won't remove the existing record for this file. I'd have to switch to something like a database to track the files using something like a CRC instead of a filename to know which file is which. That's probably not what you're looking for though.

I'm still thinking about it. I could probably rename the old way if autopar was disabled. Do you download sets that need repair?

[wmoritz]

I only care about the single picture files that get renamed not within rars - I could care not they are already safely protected from their descriptions getting overwritten.

Again, for an example, it's 25.jpg with a description "a good picture" and if another 25.jpg file get read so I get 25-(0001).jpg with a description " " instead of a desciption of "the world's top model" which it has as its description. Both 25.jpg files are unique files with the same file name of 25.jpg and because of that the second file name of would write on top of the first that 25.jpg gets renamed to 25-(0001).jpg with a blank field rather than including its proper description of "the world's top model".

Hopefully that makes it clear - I ramble rather than write at times...and thank you for your attention.

[gkar]

+1

[wmoritz]

Newsbin 6.50 Beta 14, August 6, 2013 did not have a fix for this problem.
Will it be solved in the next revision?
I believe a solution to be important because many picture creators don't uniquely name their session shoots.
Thank you, kindly.