-
... ins a number of synchronous and asynchronous tasks. The following will cause an error, as the SynthDef that the server needs has not yet been received. // Doing this all at once produces the error "FAILURE /s_new SynthDef not found" ( var n ...
-
... the SCView help file. That's it. Now recompile, only to find your first syntax errors. ;-) Happy subclassing. //try this after you have added the class to the class library ( GUI .cocoa; w= Window .new.front; v= MyWidget (w, Rect (10,20,20 ...
-
... at a time: f = { var foo; foo = 3; foo; }; f.value; foo; // this will cause an error as 'foo' is only valid within f. You can also declare variables at the top of any block of code which you execute altogether (i.e. by selecting it all). I ...
-
... or a particular signal, and no \default is supplied then one will get a runtime error. ( p = Pdfsm ( [ Pseq ( [ \foo , \bar ], 2 ), // foobar signals ( // state 0 \foo : [ 1, Pseq ([ 0, 1 ], 2 ) ] ), ( // state 1 \bar : [ 0, 3 ] ) ], 0, 2 ) ...
-
... les History .clear.start; 1 + 2; // code lines get stored ( nil + 2).postln; // error lines are ignored // comment-only line is kept, empty lines not: // save and load as text files History .saveCS; // save as compilestring for reloading. / ...
-
... *\\*a*\\*/"); "foobar".findRegexp("(o*)(bar)"); "aaaabaaa".findAllRegexp("a+"); error Prepends an error banner and posts the string warn Prepends a warning banner and posts the string. inform Posts the string. ++ aString Return a concatenat ...
-
... , repeats=1; if (list.size > 0) { ^ super .new.list_(list).repeats_(repeats) }{ Error ( "ListPattern (" ++ this .name ++ ") requires a non-empty collection; received " ++ list ++ "." ).throw; } } // some misc. methods omitted in this docume ...
-
... r's child patterns must be event patterns. Using value patterns in a Ppar is an error because value patterns contain no duration data. A Ppar is done when all of its subpatterns are done. ( Ppar ([ Pbind ( \dur , 0.2, \midinote , Pseq ([62, ...
-
... class is accessible. You should not do that. This will at some point become an error worthy of compilation failure. Catching methods that are not explicitly defined It is possible to catch calls to methods that are not explicitly defined i ...
-
... ironment.postln; // the value is stored in the environment ~b + ~a; // cause an error: ~b is nil. ~b = -90; // set ~b ~b + ~a; // now this works. // note that you can always access environments (or ProxySpaces) from outside as well: x = cur ...