Thomas Grill wrote:
well yes, but that is easy to fix.
sure, but it's your decision to give to objects a signal inlet, which i didn't want to take.
i see. btw, thanks for looking at the code (it seems like i haven't said anything positive about your bug-report+fix yet; this doesn't mean that we are not thankful)
what you get is a kind of time-stamped metro which can have message-based applications too. I have to say that i won't use the t3-objects themselves, just looked into them - but i'll use some mechanics of them for some more general clocking functionality.
ok but each message in pd is implicitly timestamped, so there is no use for such a feature, _unless_ you need explicit timestamps, which do not necessarily correspond to the exact time of the message. (e.g. scheduling messages in the future)
mfga.sdr IOhannes