Skip to content

Serial number variable for text templates with auto-advance after each job #527

Open

Description

@switch87

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

  1. knipknap commented on Oct 9, 2026

    @knipknap
    Contributor

    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!

  2. added
    rca-doneA root cause analysis was attached
    and removed on Oct 9, 2026
  3. switch87 commented on Oct 12, 2026

    @switch87
    ContributorAuthor

    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).

  4. 33 remaining items

  5. github-actions commented on Nov 12, 2026

    @github-actions

    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.

  6. added
    StaleIssue was not updated for a long time and is likely outdated
    on Nov 12, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    StaleIssue was not updated for a long time and is likely outdatedrca-doneA root cause analysis was attached

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions