Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

add an abstraction with more info on how to interpret "reference" data. #96

Open
porres opened this issue May 30, 2022 · 0 comments
Open

Comments

@porres
Copy link
Collaborator

porres commented May 30, 2022

This would add and better explain special cases, so we don't need to give redundant information. The abstraction would reside under the reference subpacthes.

It would then specify what are the usual Pd messages and explain what "anything" means (and what it means is that it is "anything else" or generic messages, but it can also mean "all messages").

This would also say that when there's not a list method that you'd expect list messages to fan out in the inlets. And if you have only one inlet, it would then consider the first element of the list.

I need to elaborate more on this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant