Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature Request: Continous Counter for Output Filename #6209

Closed
foreachthing opened this issue Mar 12, 2021 · 3 comments
Closed

Feature Request: Continous Counter for Output Filename #6209

foreachthing opened this issue Mar 12, 2021 · 3 comments

Comments

@foreachthing
Copy link

Behavior

  • the new temp-file-method broke my post processing
  • I need for pseudo version control an increasing number (prefix) in my output filename (004636_file.gcode).

Is this a new feature request?
Yes, please.

There's now way, I can think of, to achieve it with my post processing... any ideas are still appreciated.

@murk-sy
Copy link

murk-sy commented Mar 12, 2021

Sequential numbering could still cause collisions if different instances of the slicer are used - which is unlikely, but wouldn't fix the problem universally.

This might not be optimal for your needs, but you can use [timestamp] in your output filename to get output like 20210312-144503 (date and time), so it is at least still sortable like a serial number would be. Unless you're slicing multiple files per second, collisions are very unlikely even with multiple instances of slicer being used at the same time.

@foreachthing
Copy link
Author

@murk-sy, this works well enough for the moment, I guess.
The issue I have with this is, that the timestamp is really long. When I choose my file on the display, it eats up almost the whole line (filename nearly not readable).

Sequential numbering could still cause collisions if different instances of the slicer are used - which is unlikely, but wouldn't fix the problem universally.

Possibly you're right. That's why the post processing script worked so good. It could've handled that, most likely ;-)

@foreachthing
Copy link
Author

Solved with post processing (https://github.com/foreachthing/Slic3rPostProcessing/blob/master/SPP-Python/Slic3rPostProcessor.py).
Also added reverse counter (count down: #6042 (comment))

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants