Repository navigation
Description
Is your feature request related to a problem? Please describe.
Numbered plates, tags and labels need a serial number that moves on by itself after every job. Text boxes already resolve {...} templates (date, time, uuid), but a counter is only possible with a custom --script function that keeps its own state outside the project. There is also no way to give the copies of a grid array consecutive numbers, so a sheet of 20 numbered plates has to be built by hand.
Describe the solution you'd like
A project-level serial counter, similar to LightBurn's Variable Text "Serial number" mode:
- A
{serial}variable in text box templates. It is an integer, so the existing format specs handle padding and prefixes:{serial:04d},SN-{serial:05d}. - Counter settings stored in the project (
.ryp): current value, start, step ("advance by") and an optional end value after which the counter wraps back to the start. - A per-workpiece variable offset: a workpiece shows
current + offset × step. Grid and circular arrays give their copies increasing offsets automatically, so one array gives a sheet with consecutive numbers. - Auto-advance (on by default, can be switched off): after a job has been sent and has finished, the counter moves on by
step × number of copies on the bed, so the next run continues where the last one stopped. Framing, pointer dry runs and failed or cancelled jobs do not advance it. - A small "Variable Text" dialog with the settings, Previous / Next / Reset buttons and a preview of the numbers the next job will use. Every change goes through the undo history, so the document is marked as modified and an accidental advance can be undone.
Describe alternatives you've considered
A --script template function with a counter file works, but the state lives outside the project, it cannot give array copies different numbers, and it advances on every render instead of after a job.
Additional context
The offsets and the auto-advance hook are generic, so a CSV merge (one row per copy / per job) can use the same mechanism; I'll open a separate issue for that. I'm working on this and will report back with a branch.
Activity
knipknap commentedon Oct 9, 2026
Thanks for the very detailed proposal — I really like this one. The
{serial:04d}format fitting into the existing template syntax is exactly how I'd want it, and tying the auto-advance to finished jobs only (skipping framing and dry runs) is the right call. The generic offset mechanism is also a good foundation, since it should reuse nicely for the CSV merge idea in #528. Looking forward to your branch!feat: undoable serial counter commands and numbered array copies
feat: advance the serial counter after a finished job
feat: Variable Text dialog for the serial counter
docs: document Variable Text and serial numbers
test: guard optional subtitles in the variable text dialog tests
switch87 commentedon Oct 12, 2026
The serial counter is up as #554 (a draft only because GitHub would not let me open it as a regular PR; it is complete and ready for review).
feat: project serial counter for text templates
feat: undoable serial counter commands and numbered array copies
feat: advance the serial counter after a finished job
feat: Variable Text dialog for the serial counter
docs: document Variable Text and serial numbers
33 remaining items
docs: translate the Variable Text page
test: give the template test provider a reference point
fix: keep the anchor in place when the counter changes the text
docs: move the job counter changelog entry to UNRELEASED
fix: drop the serial number wording from the job counter dialog
refactor: name the job counter in the last two variable text leftovers
test: give main's parametric fake provider the template methods
style: apply ruff format to the job counter files
fix: count no copies for providers that give no variables
fix: keep uuid and date text when the job counter changes
docs: describe one job counter, not template variables
refactor: drop the Job Counter group from the properties panel
refactor: sort copies by the public item bbox
github-actions commentedon Nov 12, 2026
This issue is stale because it has been open 30 days with no activity. Remove the stale label or comment, otherwise it will be closed in 7 days.