Simon O'Rorke

: 8.2.0 (The bug does not occur in 8.1.11.)

If parent and child patchers in a project both host the same third patcher (as an abstraction or 

 object that references a file of the same name (apart from the extension) as itself, then, when the parent patcher is opened, error message 'newobj 

 is the name of the third patcher, will be shown on the Max console.

1) Create a project containing three empty patchers (child.maxpat, parent.maxpat and scored.maxpat) and one Javascript file (scored.js).

 object, specifying 'scored' as its filename argument.

3) In child.maxpat, add a 'scored' abstraction.

4) In parent.maxpat, add a 'scored' abstraction and a 'child' abstraction.

5) Close parent.maxpat and reopen it from the project window.

It should be possible to double-click the 'scored' abstraction in the 'parent' patcher to open the 'scored' patcher.

Error message 'newobj scored No such object' is shown on the Max console. In the 'parent' patcher, the 'scored' abstraction is colour-coded to indicate a non-existing object. Double-clicking the abstraction does nothing.

ParentChildCommonBUG.zip

The workaround is to call the Javascript file something that does not match (exclusively of the extension) the name of its host patcher. So, in the above example, 'scored.js' could be renamed to 'ranked.js', amending the filename in the referencing 

Example Project That Shows the Workaround

ParentChildCommonNOBUG.zip

Max Version: 8.2.0 (The bug does not occur in 8.1.11.)

If parent and child patchers in a project both host the same third patcher (as an abstraction or bpatcher) and the third patcher contains a js object that references a file of the same name (apart from the extension) as itself, then, when the parent patcher is opened, error message 'newobj xyz No such object', where xyz is the name of the third patcher, will be shown on the Max console.

2) In scored.maxpat, add a js object, specifying 'scored' as its filename argument.

The workaround is to call the Javascript file something that does not match (exclusively of the extension) the name of its host patcher. So, in the above example, 'scored.js' could be renamed to 'ranked.js', amending the filename in the referencing js in the 'scored' patcher accordingly.

Bug Report
Max Version: 8.2.0 (The bug does not occur in 8.1.11.)
Operating System: Windows 10
Summary
If parent and child patchers in a pro

bug-report-'newobj-…-no-such-object'-when-parent-and-child-patchers-in-a-project-both-host-the-same-third-patcher-and-the-third-patcher-contains-a-js-that-references-a-file-of-the-same-name-apart-from-the-extension-as-itself

I've just reported the bug to Cycling '74 Support via the Report a Problem form.

Cycling '74 Support have acknowledged that this is a bug and have passed it to Engineering for a fix.

 Cycling '74 Support  have acknowledged that this is a bug and have passed it to Engineering for a fix.

This has been fixed in version 8.2.1. See "subpatcher: no longer appears bogus when opened from project window" in 

This has been fixed in version 8.2.1.  See "subpatcher: no longer appears bogus when opened from project window" in the release notes.  Thanks.

Bug Report: 'newobj … No such object' when parent and child patchers in a project both host the same third patcher and the third patcher contains a js that references a file of the same name (apart from the extension) as itself