The attached patch includes a couple of other quirks / tests. I tried a number of things: using a queue internal to the iterator patch: it is interesting to compare the values stored in the queue and those stored in the multiplexor. They differ - this must be due to the execution order of the patches.
I also tried setting the time-base of the smooth patches internal and external to the iterator.
It may helpful (or maybe downright wrong - due to infinite looping) to be able to publish outputs from an iterator and feedback the values back in.
iterator_quirk.qtz
Description: application/quartzcomposer
Regards, Ian ******************************* Ian Grant Senior Lecturer in Digital Art Faculty of the Arts Thames Valley University Ealing, UK W5 5DX <[EMAIL PROTECTED]> ******************************* On 31 Mar 2008, at 01:28, lists @ tobyz wrote:
i have faced that exact issue and have an "iterator safe" smooth patch in development-stasis: i coded a smooth patch that kept an array of state variables controlled by an iterations input, however i encountered some unexpected behaviour and haven't finished the test cases to work out exactly what was going on.i will either get to the bottom of it, or post here / file a bug certainly in the next month, hopefully sooner. so if you can wait, watch this space. if somebody gets there first and releases it, all the better =]tobyps, and imho - the iterator concept needs some love from the dev team. the patch does its job by the letter of the law, but hardly the spirit of a "just works" environment: this being an example. i will be filing some bug reports / feature requests around this just once i've coded my work-arounds.On 30 Mar 2008, at 16:59, Benjamin Khoo wrote:hi alli am facing some problems with the iterator patch with a smooth patch inside it.The iterator patch was used to recursively draw a sphere over several locations in the rendering window.The locations of these will change based on some condition.i was trying to smoothen the animation of the sphere moving between states instead of "jumping" from one state to another.the initial test was done without the smooth function and the spheres all appeared in the right places. (jumping around as the state changes).but once the "Smooth" patch was introduced to help "smoothen" the jumping around motion, the spheres no longer appeared in the right places.in fact, they all seemed to take only the state of the last sphere. i was wondering if i am doing anything wrong here?or if the "smooth" path doesn't work work well inside the interator patch?i attached the QC here for critique thanks lots <fun.qtz> -- bENJAMIN kHOO qIU wENDA http://www.copperblue.per.sg http://himiko.dnsalias.net:8000 gpg --search-keys [EMAIL PROTECTED]perl -e "while(length(\$s='1079797275786966')-(++\$i*2)>=0) {push(@_,substr(\$s,length(\$s)-\$i*2,2))}print pack('c'.scalar(@_),@_)"_______________________________________________ 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/lists%40tobyz.net 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/ian.grant%40mac.com 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]
