Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • P purr-data
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 362
    • Issues 362
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 54
    • Merge requests 54
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Jonathan Wilkes
  • purr-data
  • Issues
  • #629

Closed
Open
Created Apr 05, 2020 by Dave Riedstra@driedstr

[clone] counter reset when sent [all(

This issue is a duplicate of pure-data#305, which is fixed in vanilla pd 0.48-2, but hasn't made its way into purr-data yet.

When using [clone]'s built-in counter, sending it an [all( message will incorrectly reset the counter.

(I'm not aware of the mechanism by which purr-data is kept up-to-date with changes in pure-data vanilla, nor can I find a recommended way of reporting issues like this, so I'm reporting it as a plain bug.)

Assignee
Assign to
Time tracking