Eric wrote:Anything is possible, but Magic's to-do list is many hundreds of lines long.
Yeah, I bet!
So you must be one of the developers of Magic? Did you also design it?
Yes.
You did a great job! I feel like it's very intuitive. I'm very excited about this program! I've been looking for a program like this for years now.
Does Trails keep a bunch of copies of the screen in memory then?
No, only one copy: the current frame blended with the previous one. But if you want more of an echo or delay effect, then yes, you have to keep many previous frames, which is why it would be very inefficient.
There's got to be some trick!
I think what you really want is a way to successively delay iterations, which is a good idea and I will put it on my list.
I'm not sure what you mean by "successively". I don't know how Magic works, but I think if the Iterator were implemented with a for-loop, then I want to insert a sleep statement just before the end of the loop.
Thanks, though! You've given me plenty of stuff to play with in the meantime!
Successively means i*d, where i is the iteration #, and d is the delay. So, for some number of iterations, the first iteration would have no delay (d*0), then the second would have d*1 delay, then d*2, and so on. If d is .1 seconds, then the specific delays would be 0, .1, .2, .3... etc. Overall, it would result in exactly what you asked for in your first post, which I didn’t understand at the time .
.