Suggested process for handling variable number of parameters for a custom block

@kinestheticlearning In reply to your questions on other thread about why not use variadic slots

One of the problems of variadic inputs in a custom block is that if you make even the slightest edit to the block definition - any existing use of the blocks in a project immediately lose their parameters. :frowning:

I am looking to try and persuade a library author to add additional options to their blocks and I want to keep things as simple as possible in order to boost chances of my enhancements being accepted

I decided that Dardoro's clever ideas might be a step too far so just going to try a simple approach at first.

Could I persuade you to delete your comments in the other thread to keep it on topic please? :slight_smile: