That doesn’t work if that other dataset doesn’t already exist. But I can’t give the other dataset a name for the same reason. So if I want to create a new dataset but don’t have a name for it, its the same problem.
That doesn’t show up in the “right-click input” thing, the helpfile, or the reference page though.
Well, I will manually create the dataset by creating an object called fluid.dataset~. I want to dynamically name it. So like, a patch may have a few of these “unnamed” fluid.dataset~s which I’ll (programmatically) name unique identifiers + strings.
Nice. Is that like common knowledge? Never in a million years would I have started typing arbitrary requests to an object that doesn’t say what it’s list of messages are.
Ok. Not possible, I’m afraid, but what’s wrong with the unique names that come with putting no name in?
It’s certainly true for all the jitter objects, not sure what of the newer Max object use dump outlets. Will make sure we add to docs somewhere, because evidently not common enough knowledge. It applies to any attribute on one of our objects that has a dump outlet at the right
Yes, to be fair to @rodrigo.constanzo I had the same epiphany at the hands of @weefuzzy at some point. It’s a convention that is quite useful, at least, you really are pleased when you know you need it and you are granted the wisdom to getstuff.