Julian Rohrhuber

yes we should definitely consolidate this, in particular because you may want to use midi and osc in combination. It would be optimal if one could set that value at...

> 2\. Why does `loadRelative` return an array? Because it may interpret several files, when the path is a wildcard. `loadRelative` calls `loadPaths` which returns an array. This is more...

In my memory, there is indeed a bug in loadRelative, and resolveRelative (If I understand, you also found it?) This should be done in a separate issue, and probably fixed...

Thank you! The important thing in all the changes was that we still have an option to have several of them if needed (e.g. for multi-screen setups). s.meter –> `ServerMeter`...

One more idea, to make multiple views even more useful: instead of passing the argument `server`, you could call it `target`. Then, the view could monitor any group in the...

Sorry for not coming back to this, I was busy with outher things. Will continue later, if this is ok.

Probably, this is based on a misunderstanding: subclasses do not implement all superclass interface.

The implementation of `basicNewCopyArgsToInstanceVars` seems to be correct: ``` int length = sc_min(numArgsPushed-1, newobj->size); for (int i=0; islots[i], &b[i]); } ``` But the reported `numArgsPushed` is wrong for exactly two...

Somehow I have the suspicion that it has to do with `int checkPushAllArgs(PyrParseNode *actualArg, int numArgs)` or similar. There is a check for `numArgs < 3`. But it is strange...

even if it is uncontroversial, someone needs to run one compile and check if it breaks nothing. (I can't, because for me the build is stil broken)