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

expose more how list are spread out over the inlets #187

Closed
porres opened this issue Mar 14, 2024 · 3 comments · Fixed by pure-data/pure-data#2257
Closed

expose more how list are spread out over the inlets #187

porres opened this issue Mar 14, 2024 · 3 comments · Fixed by pure-data/pure-data#2257

Comments

@porres
Copy link
Collaborator

porres commented Mar 14, 2024

currently [line~]/[vline~] expose this but other objects could hint to this as [makenote], math objects, [expr] and stuff

@millerpuckette
Copy link

millerpuckette commented Mar 14, 2024 via email

@porres
Copy link
Collaborator Author

porres commented Apr 29, 2024

As I wrote in the list back then, I agree the not-quite-standardness is in the way the middle inlet itself acts, but it is still behaves the same wether it takes a list input in the left inlet to distribute or a single value directly

@umlaeute
Copy link

the not-quite-standardness is in the way the middle inlet

Actually the not-quite-standardness is in the left (hot) inlet, which resets the middle inlet...

porres added a commit to pure-data/pure-data that referenced this issue Apr 29, 2024
just making it clear the inlet values are cleared when the ramp starts, this wasn't clear in the help of [line~]. This was also pointed by @umlaeute in pure-data/pddp#187 (comment)

I also added information on how [line~] is less accurate than [vline~] in its help file
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

Successfully merging a pull request may close this issue.

3 participants