The two screenshots show how JavaScript inputs and outputs used to be
handled in the version of QC shipped with MacOS X 10.4 (Tiger), and
that shipped with 10.5+, respectively. For compatibility reasons, if
a Quartz Composer file created in the Tiger version of QC is opened
in a later version of the application, JavaScript patches will look
as they did when originally created- ie they will handle IO as in the
top screenshot. Newly-created JavaScript patches however, will look
as the 2nd screenshot, and input and output ports are created in the
function-declaration block for the main function.
Hope this makes things clearer.
a|x
http://www.machinesdontcare.wordpress.com
On 1 Nov 2010, at 08:54, Christoph Kluxen wrote:
Hi,
thanks for the answer.
I´m not sure you got me right, I´m using QC3 at 10.5.8, so that`s
right, but the QC3 patches from cybero use no main function as is
in the default javascript to define in and outputs, but a checkbox
for the in and outputs and I don`t know why. It`s not an
error....Perhaps a different Javascript patch?
Christoph
cybero
<Bild 2.png>
default:
<Bild 3.png>
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Quartzcomposer-dev mailing list (Quartzcomposer-
[email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/quartzcomposer-dev/the_voder%
40yahoo.co.uk
This email sent to [email protected]
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Quartzcomposer-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/quartzcomposer-dev/archive%40mail-archive.com
This email sent to [email protected]
