[java-dev] Re: getParentPatcher().getPath() does not always work in the constructor
John Pitcairn
cycling74forum at opuslocus.net
Tue Mar 4 15:41:18 MST 2008
- Previous message: [java-dev] getParentPatcher().getPath() does not always work in the constructor
- Next message: [java-dev] Re: getParentPatcher().getPath() does not always work in the constructor
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
It's the same in JavaScript, where you can't get this.patcher's parent patcher immediately, it needs to be done from the js loadbang(). And there are similar issues in native C, we can't even rely on loadbang(), we need to defer_low() if we want to know anything about the patcher structure. Seems the parent heirarchy isn't fully discoverable until some time after the patcher loadbangs its contained objects. There was some discussion of this on the dev-list recently.
- Previous message: [java-dev] getParentPatcher().getPath() does not always work in the constructor
- Next message: [java-dev] Re: getParentPatcher().getPath() does not always work in the constructor
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
