Julian Rohrhuber

Yes, they should only warn, but then return early. I don't think you can do this from a method outside the scope of the call (without tricks).

It is not possible to return from another method via any of those methods like `ifRunning` or `checkRunning`. Try this: ```supercollider TryCanWeReturnFromDefault { pleaseReturnForMe { |message| "trying to return for...

By summary, I think this is too complicated. Two solutions: 1. simple one: standardise the existing warnings in the code. Don't make them elaborate, the warning should not obfuscate what...

Maybe it would be enough to say: ```supercollider if (server.warnIfNotRunning("Who", "X will not work.")) { ^this }; ``` Although some of the complexity is also in the "Who". This should...

> I think the warning message I constructed is good, so I want to preserve it if possible. Will it be ok? ```supercollider var warnLabel = this.asCompileString ++ "." ++...

Do we maybe want to fix the classes before having the failing tests in the CI? We can use the new UnitTest to make sure it is all done.

There is a (slightly hidden) already existing issue that I just noticed and just want to mention here. It has to do with the combination of subclassing and overriding `doesNotUnderstand`....

> Should this PR contain all of these fixes? Could you start another one that focusses on these fixes? I would suggest that we implement the obvious ones. When we...

I had never thought of `this.subClassResponsibility(thisMethod)` as a duty of subclasses, but as an abdication of duty on the side of the superclass. It signals that the superclass cannot know...

Btw. for naming conventions and avalability of easy to reach features in SuperDirt, you could check this help: https://doc.sccode.org/Classes/Event.html#Useful%20keys%20for%20notes The SuperCollider event model allows for scales, tunings, stretched octaves, steps...