Hallo, Chuckk Hubbard hat gesagt: // Chuckk Hubbard wrote:
Yes. I was going nuts trying to figure this out, when I detached the inlet in my [until] version and it suddenly worked using your testing print objects. Apparently it is the way I have it implemented in my patch: its own left outlet is still set up to retrigger the inlet. I didn't have any stray [next( messages going in, that was what was confusing me; because if there were, my previous version should have given empty pointer errors, and it didn't.
I don't know how else to implement this, without its output retriggering it. I did fix my transposing function, pretty much, so the old recursive JInext patch is doing all its jobs fine. It's just not realistic to try to revamp my whole sequencing function this close to my finals (this program isn't for credit).
If you want to do this later, I have a small addition: The [spigot] stuff turned out to be unnecessary. Triggering the until multiple times in my patch doesn't change or break anything. I attached a cleaned up version of the example I did, called "ds-traverse". It should be possible to use as a drop-in replacement for JInext with the supplied wrapper called "JInext-dropin.pd", which has exactly the same interface as your JInext.pd.
Now I'm wondering: a) is it possible to use integers as a type for a struct field?
No, I don't think so: only float, symbol, array and list are possible types in struct-definitions.
b) what are the limits on Pd's float accuracy?
There is a thread going on about this currently, you should have it in your mailbox, it's subject is "32bit integer float".
Ciao
Frank Barknecht _ ______footils.org_ __goto10.org__