My UnitTest.moz lists several of these edge cases where Mozaic does not throw an error in the 'Differences to Mozaic' section near the end. As you work, Textastic shows the current line and column in the upper-right corner. I liked the empty brackets on the lvalue side, so the parser does not flag these - but it will flag empty array assignments on the right side. I checked this after finding a script using something like 'FillArray name, 0, 16' and 'table = '. Mozaic allows an 'array = ' statement that assigns to the array with index offset 0 using array assignment with an empty array - doing nothing than declaring the variable array (and all its 1000 indices) with the default value zero. The 'div' variable example above 'kills' the div function name with 2 parameters. So if you ever assign 'LastKnob = 2' your OnKnobChange will always use the 2 of the variable and not the result of the LastKnob function. Mozaic allows to use keywords as variables - and these override their intended functionality. Therefor 'a = Random' (which officially requires two parameters) returns a value between 0 and 127, using min=0 and max=127 as defaults. Mozaic uses internal default parameters if something is missing. LabelKnob chanKnob, ' without getting a syntax error. SetKnobScale chanKnob, 0, LastKnob = chanKnob The API could look like: SetKnobScale, , Īnd a script to send all notes to a selected channel could look like: = 0 I think it would really help if Mozaic would allow to bind a scaling to a knob. All tedious stuff that is no fun to write.
#Textastic read and write filetype code
I guess 10-20% of my code is for the actual logic, the other code is for getting knob values, scaling values, setting labels, scaling values back to re-set knob values. However, I find it to tedious to build a nice configuration interface for more complex scripts (especially with multiple screens). I always want to finish these script, make them configurable and upload them to patchstorage. So far I've written mostly one-off scripts. It's a really great way to spice up my AUM sessions. I came here to say how much I like Mozaic. (eagerly awaiting the invite for 2025 Mozaic Developers Conference, btw ) Information "won't happen" is also helpful, then I would know that any "workarounds" won't be void in a few weeks time. and more - most of it already mentioned - would it be possible for you to disclose some of the stuff planned for the future? A rough sketch of a roadmap or similar? It would help a lot in "planning" how/if to proceed along certain routes in my development.