Asmatzaile
Asmatzaile
Yes, the first available release of the library for Processing 4 is compatible only with Processing 4.0b6 and newer. See https://github.com/processing/processing-video/releases/tag/9 (@codeanticode, should this issue be closed?)
@smoge go ahead for me! I don't know how to > normaliz[e] internally [so that it] doesn't require a full array copy
I am trying to find a discussion around the original implementation of the `wchoose` and `windex` functions but it seems like they were there from [very early on](https://sourceforge.net/p/supercollider/supercollider/ci/e3a18fc9891d931f9b5b539758a7c6102d86184f/tree/build/SCClassLibrary/Common/Collections/SequenceableCollection.sc?force=True#l24). FWIW, some...
How about adding optional arguments to `.choose`: (weights=nil, n_weights=nil)? When n_weights!=nil, it could call to wchoose[nweights]; else if weights != nil, wchoose[weights.normalizeSum], and else, the usual `choose` function. That would...
What I'm suggesting now is to keep `.wchoose` as it is and change `.choose` instead. `[/one, /two, /three].choose` would work like now. But one could also do `[/one, /two, /three].choose([1,2,3])`...
Cool! Will make a PR later.
Actually the syntax should be block["name"], right? https://github.com/mermaid-js/mermaid/wiki/Block-Diagram-(WIP)#layout-direction
> Thanks @Asmatzaile for the PR! It seems that there was a lengthy discussion on adding arguments vs a new method in #6601 Would you consider #6601 to supersede your...
Rethinking about this issue, maybe the best option would be to leverage [use-gesture's `axis` option](https://use-gesture.netlify.app/docs/options/#axis) to provide the four of its alternatives to the user. So, for backward compatibility (if...