pattrstorage glitch


    Jan 13 2006 | 10:33 pm
    Hi,
    I found a glitch in pattrstorage's handling of pattr client objects-
    not totally a bug, but still a pain.
    In pattrstorage's client window, I expect it to update the name of the
    subpatches containing pattr objects when I change them, but it doesn't.
    In addition, when I copy and paste a pattrstorage object from one patch
    to another, it retains the old info and never updates the subpatch name
    in the client window. Removing and adding pattr objects in the
    renamed subpatch do not update the name in pattrstorage.
    Here is a patch showing this:
    max v2;

    • Jan 15 2006 | 10:54 am
      I'm sorry, what am I supposed to do with this patch? Looks like a job
      for the BUG REPORTING GUIDELINES, attached below.
      Please, including a patch is brilliant and useful and extremely
      appreciated, but without clear, numbered instructions, I am forced to
      (probably incorrectly) interpret what an imprecise sentence like "I
      expect it to update the name of the subpatches containing pattr
      objects when I change them, but it doesn't" could possibly mean.
      Thanks,
      jb
      BUG REPORTING GUIDELINES
      Please report any problems you experience with clear and complete
      information, including steps to reproduce, software and system
      information, and where possible, an isolated example patch and crash
      log. Something like the following would be ideal. This makes it
      easier for us to find and fix the problems you experience. Without
      such clear and complete information, it is less likely we will be
      able to.
      Summary:
      Provide a descriptive summary of the issue.
      Steps to Reproduce:
      In numbered format, detail the exact steps taken to produce the bug.
      Expected Results:
      Describe what you expected to happen when you executed the steps above.
      Actual Results:
      Please explain what actually occurred when steps above are executed.
      Regression:
      Describe circumstances where the problem occurs or does not occur,
      such as software versions and/or hardware configurations.
      Notes:
      Provide additional information, such as references to related
      problems, workarounds and relevant attachments.
    • Jan 16 2006 | 4:50 am
      While we're on this topic, why isn't there a super-simple Php (or
      perl, or whatever) form on the web that we can use to automatically
      report bugs, that CC's the maxmsp list automagially? Why do I have
      to sort through all of the list whenever I want to find the bug
      reporting sheet (which who knows, may change in the future)?
      It's incredibly easy to make such a form. So I put my money (or
      time) where my mouth is:
      It emails bug reports to the max list in the proper format (the user
      must be subscribed to the max list).
      If it is abused I will remove it promptly.
      If you have Php+PEAR installed (or simply Php) it will work, and I'd
      be happy to provide the very simple source code.
      -Evan
    • Jan 17 2006 | 8:14 am
      Evan,
      Thanks for doing this.
      I didn't get an updated bug report regarding the original issue,
      though. I'd like to look at the problem, but I was being serious
      about not having any idea of what to do with the patch you sent.
      jb