PyoungRyang Ko
PyoungRyang Ko
Editing code in the code block area of the Help browser often results in errors. Even Shift + Enter doesn't work.
>I don't know if we want to advertise if with ugens, it's a bit of a hack... If I recall correctly, the use of `if` within SynthDefs and `if` with...
Is it better to move the following sections from the [User FAQ](https://doc.sccode.org/Guides/UserFAQ.html#SynthDef%20Issues) - "If" statements inside a SynthDef - Why is x ＞ 0 "non-Boolean" in the "test"? - If...
>Perhaps you might wish to emphasize "if is a hack" a bit more? But the content you describe is already there. This is my thought, so I linked those parts...
>This file (irrespective of your additions) is one of those help files that is actually disorienting. That is, I remember multiple times where I wanted to verify my if syntax...
I think: The text in this PR should be moved to PR #6967 once it has been merged. Alternatively, #6967 could replace this PR.
noticed that if.schelp was removed in #6967. If the changes proposed here are already covered by the corresponding content in #6967, I believe this PR can be closed. Please feel...
>The content of the PR doesn't seem to match its description? I changed the title, but I am not sure if you agree... If you have a better one, please...
For me, it would be great if the following PRs and issues could be implemented: - #6501 - #6401 - #6566 - #6563 - #6554 - #6549 - #6545 -...
>btw - please do not add merge commits to your PRs if they are not necessary as it adds noise to the PRs commit history. Merge commits are essentially only...