> Provide a descriptive summary of the issue.
> 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
> Actual Results:
> Please explain what actually occurred when steps above are executed.
Max go byebye.
> 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.
> 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