Bug report: how to byork and crash filedrop


    May 11 2006 | 3:23 pm
    > Summary: > Provide a descriptive summary of the issue.
    filedrop crash.
    > Steps to Reproduce: > In numbered format, detail the exact steps taken to produce the bug.
    i. create a filedrop object in a new patcher ii. send the message 'types #1' to the filedrop iii. save the patcher (I'm saving as text, FWIW) iv. try to use this patcher inside a bpatcher v. bang, illegal address exception (null) inside filedrop
    > Expected Results: > Describe what you expected to happen when you executed the steps above.
    bpatcher.
    > Actual Results: > Please explain what actually occurred when steps above are executed.
    Max go byebye.
    > Regression: > Describe circumstances where the problem occurs or does not occur, > such as software versions and/or hardware configurations.
    Problem occurs on MaxMSP 4.5.7, OS X 10.4.6.
    > Notes: > Provide additional information, such as references to related > problems, workarounds and relevant attachments.
    Why does filedrop save its current 'types' configuration in the patcher? This behaviour is not visible (filedrop doesn't have an inspector).
    nick rothwell -- composition, systems, performance -- http:// www.cassiel.com

    • May 11 2006 | 3:32 pm
      On 11 May 2006, at 16:23, Nick Rothwell wrote:
      > > Summary: > > Provide a descriptive summary of the issue.
      Rothwell refers to "dropfile" as "filedrop".
      > > Expected Results:
      "dropfile".
      > > Actual Results:
      "filedrop".
      > > Notes:
      Rothwell should pay more attention in class.
      -- N.
      nick rothwell -- composition, systems, performance -- http:// www.cassiel.com
    • May 11 2006 | 5:53 pm
      > > > Summary: > > > Provide a descriptive summary of the issue. > > Rothwell refers to "dropfile" as "filedrop".
      and i was hoping for a new object mb.