I've been noticing a handful of oddities with the iterator, but this is one
I would like to seek some feedback on this one before submitting a bug:

Basically, when this is opened, what one will see is that this is set to two
iterations, and renders one Sprite.

Weird part : when I reduce the iteration count to one, then increase back to
two, all of a sudden two sprites magically render.

So, *an iteration count of two can yield either one or two sprites depending
on the order of editing events.*

If I was to automate the input port with an lfo or interpolate/round (or
whatever) two go back and forth between one and three iterations, stopping
at each step, at two iterations I *always* see one object.

To add a further level of strangeness, if I am automating the port and have
a simple image with string to billboard setup, so that I can see the current
iteration count... and then I *disconnect it entirely but it is still on the
Editor doing the "reduce iteration count to 1, increase to 2" never yields
two sprites, following the original procedure. The second I delete the
Billboard/string setup (even though it isn't connected to anything), doing
the "decrease to 1 iteration, increase to 2" goes back to rendering two
sprites.*
*
*
*The reason I seek inquiry on this; am I misunderstanding what a square wave
should render in this scenario? I believe that it should render two Sprites.
In any event, it doesn't seem like this should ever be dependent on the
Editor state in this way.*
*
*
*-George Toledo*

Attachment: lfo iteration oddity.qtz
Description: Binary data

 _______________________________________________
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

Reply via email to