NUM_API_FUNCTION_SLOTS

[d.healey]

@Christoph-Hart I've been adding functions to the Engine class and it seems I've hit this limit. What do I do?

[d.healey]

Could I just increase the limit, or is that a bad idea?

[d.healey]

Bump bump

[Christoph Hart]

Hmm, the problem is that there are a few performance implications of having a large number of API calls per class, so we can't raise that number indefinitely so at some point we might think about breaking the Engine class down into multiple smaller classes. However this will completely break all existing code, so it's not an option unless we add an automatic migration tool.

Nevertheless, problem of future chris. Raise it!

[d.healey]

@Christoph-Hart All of the functions I'm adding are to make the custom settings panel options available via scripting. So maybe a Settings class would be the answer?

[Christoph Hart]

Yeah, that's better. Do you know how to add an API class?

[d.healey]

@Christoph-Hart I don't but I don't mind learning, can you point me to the documentation?

[Christoph Hart]

Yeah, the documentation

I've added the setting API class as template, so you can populate it with the stuff you need.

https://github.com/christophhart/HISE/commit/c61759fa260dcbda57da56631f5c8d1a18e32416

Also this commit is now the documentation for how to add a new API class

[d.healey]

@Christoph-Hart Excellent, thank you