I'm not intending to create inputs in the execute method, not sure where you got that idea.
My concern is that I want my hosting app to be able to set the values of inputs that are created dynamically when the composition is loaded. But my understanding is that it can only do this to published inputs. I don't know how to publish an input programmatically. -- Rick On Jun 6, 2010, at 22:09:26, Troy Koelling wrote: > You should not (and I believe you will be blocked if you try) add ports > dynamically in the execute method. This will cause issues with serialization > and also make it so that connections are disconnected at runtime if the > source file changes. > > if the ports will be connected to items in the file that have unique names > it's best to have a settings panel that defines the interface to the patch > and any file that matches that protocol will be supported by it. You would > probably want to have a "configure with file..." button for ease of use. This > is similar to how the Composition Loader works, love it or hate it :) > > It that is not possible or files are too specific to define this sort of > interface, you may want to make it so the file path is not editable at > runtime. Rather than having a path input on he patch, use the settings panel > to setup based on the file (or maybe even serialize it Into the composition > state). > > As long as you add the dynamic ports during setup or init you should be fine > with published ports. > > Troy > > Sent from my iPad > > On Jun 3, 2010, at 4:30 PM, Rick Mann <rm...@latencyzero.com> wrote: > >> I haven't looked into this much, but I'm thinking my custom patch will need >> to create inputs dynamically, based on a data file it will read when >> initialized. >> >> However, I also need for these inputs to be published, so that my rendering >> app can provide the data for each one. Is this possible? >> >> TIA, >> Rick >> >> _______________________________________________ >> Do not post admin requests to the list. They will be ignored. >> Quartzcomposer-dev mailing list (Quartzcomposer-dev@lists.apple.com) >> Help/Unsubscribe/Update your Subscription: >> http://lists.apple.com/mailman/options/quartzcomposer-dev/tkoelling%40apple.com >> >> This email sent to tkoell...@apple.com _______________________________________________ Do not post admin requests to the list. They will be ignored. Quartzcomposer-dev mailing list (Quartzcomposer-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/quartzcomposer-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
