https://bugs.kde.org/show_bug.cgi?id=389738
--- Comment #3 from schwim <sch...@bitrail.com> --- (In reply to Jasem Mutlaq from comment #2) > Actually, that solution is not complete and can have issues. I have another > proposal. Would it be OK if we make the path like this: > > TargetName/Job_#/Light/OIII/..etc > > That is, after the target name, each each a subdirectory containing the job > number. This way the path is always unique. What do you think? That would work, however it would induce a bit of work when collecting all the data for processing (need to descend into multiple directory trees to get all the files pulled together). Presuming its a matter of having a unique filename for each image, I have a few alternatives: 1) Require that TS be on for file naming and rely on that -or- 2) Append a part of the job name to the file -or- 3) Use a system-wide counter for all image saves I've seen 1&3 in use elsewhere and they work well. In the case of #3, the user can maybe even set the numbering if they wish. Example - append 4 digits at the end of each image, start at 1234 and increment, never repeat unless reset. Probably good to have some corner case collision avoidance as well. In the rare instance a collision does occur, iterate to the next for the filename. #1 and #3 should both accommodate this. -- You are receiving this mail because: You are watching all bug changes.
