patches with Square corners are macros (think functions) that have at least one
patch but usually more inside them. the inputs and outputs on those patches
inside can be published to the macro and therefore appear at the level of the
marco (the parent level).
If you hover the mouse over the patch title it will give some more details.
type part of the name in the patch library inspector search field and you’ll
also get the description. In preferences you can set how much info “tooltips”
provide. also hovering over ports gives you realtime value feedback. again
prefs can set the level of detail you get printed to the screen.
It used to be when CapsLock was on that you couldn’t double click a marco and
enter it which was really handing when adjust ing values and not accidentally
being sent inside. but Apple in their great wisdom removed that feature (they
like to remove features don’t they?). so just double click to go inside. You
can make your own macros and also virtual patches which are more like classes
or functions in programming where you change once and it changes all the
instances. when you create a virtual patch it creates a file for that macro and
makes the Marco a patch. if that makes sense. will after you try it out a few
times.
Best
Alastair
Alastair I Leith
Useful Design
0432 889 831
6/9 Princes St
C o t t e s l o e
WA 6011 Aust
> On 21 Oct 2015, at 10:43 am, Josh Reiss <j...@joshreiss.com> wrote:
>
> I'm sure this is a silly question... Is there any way to select a patch in
> the interface and find out what the patch type is?
>
> I'm looking at the top level of the basic "image filter" project and not sure
> what the inputs are that it created ("image" "x" "y"). Also I'm looking to
> create a few patches like this for basic inputs into the macro for new
> parameters on patches I'm creating, and not sure how to just create those
> basic patches.
>
> (these are called "patches" right? that's what everything in the interface
> seems to say)
>
> I think I've figured out to create a node/patch inside the macro, then
> publish an input to have it show up on the macro... then I'm guessing I need
> to put one of these basic patches on the macro level to publish the input to
> have it show up in the interface.
>
>
> <Screen Shot 2015-10-20 at 7.36.22 PM copy.jpg>
> _______________________________________________
> 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:
> https://lists.apple.com/mailman/options/quartzcomposer-dev/usefuldesign.au%40gmail.com
>
> This email sent to usefuldesign...@gmail.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:
https://lists.apple.com/mailman/options/quartzcomposer-dev/archive%40mail-archive.com
This email sent to arch...@mail-archive.com
