Builder InterfaceTypes

[Lindon]

@David-Healey thanks yes I know where to find the connectToScript, and my current version of auto-complete refuses to load my selection so I dont use it (much), still I guess I can read and copy..(ugly)

thanks.

[David Healey]

@Lindon The autocomplete is a bit dodgy, if you add a new object or you have a compile error it doesn't populate until you next successfully compile.

[Lindon]

@David-Healey it turns out its worse than that:

var stdscript = builder.create(
              builder.MidiProcessors.Arpeggiator, // the module type
              "Arpeggiator1",                       // the ID
              mastercontainer,                       // the parent (root)
              builder.ChainIndexes.Direct);             // the slot type

gives me:

Interface:! Line 19, column 31: Couldn't create module with ID Arpeggiator 

[Lindon]

@Lindon turns out its me being dumb...

var stdscript = builder.create(
              builder.MidiProcessors.Arpeggiator, // the module type
              "Arpeggiator1",                       // the ID
              mastercontainer,                       // the parent (root)
              builder.ChainIndexes.Midi);             // the slot type

[Lindon]

OK so now I cant get builder.connectToScript(strum, "AScript2.js"); to work its telling me

StrumProcessor:! onControl could not be parsed!

heres onControl

function onControl(number, value)
{
	
}
 

[David Healey]

@Lindon Do you see that error when you use that script manually?

[Lindon]

@David-Healey nope...

[David Healey]

@Lindon What about through the builder in a minimal test project?

[Lindon]

@David-Healey this is a minimalist test project...

[David Healey]

@Lindon Can you send it to me?

[Lindon]

@David-Healey yep hold on I will have to do some rebuilding...

[Lindon]

@David-Healey - OK how do you want it - its literally an init HISEScript and a .js file with the script in it...

[David Healey]

@Lindon If you can post it publicly just dump it here. Or a dm/email