[java-dev] Re: getParentPatcher().getPath() does not always work in the constructor
Adam Murray
adamjmurray at gmail.com
Tue Mar 4 16:20:34 MST 2008
- Previous message: [java-dev] Re: getParentPatcher().getPath() does not always work in the constructor
- Next message: [java-dev] net.mail problems
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Quote: johnpitcairn wrote on Tue, 04 March 2008 14:41 ---------------------------------------------------- > 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. ---------------------------------------------------- Too bad the Max APIs don't provide an onPatchInit() callback. -- Adam Murray compusition.com
- Previous message: [java-dev] Re: getParentPatcher().getPath() does not always work in the constructor
- Next message: [java-dev] net.mail problems
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
