This is a crucial feature, discovered only late, while building an overall integration test: it is quite common for processing functionality to require both a technical, and an artistic parametrisation. Obviously, both are configured from quite different sources, and thus we need a way to pre-configure ''some parameter values,'' while addressing other ones later by an automation function. Probably there will be further similar requirements, regarding the combination of automation and fixed user-provided settings (but I'll leave that for later to settle). On a technical level, wiring such independent sources of information can be quite a challenging organisational problem — which however can be decomposed using ''partial function closure'' (as building a value tuple can be packaged into a builder function). Thus in the end I was able to delegate a highly technical problem to an existing generic library function.
9.1 MiB
9.1 MiB
| The file is too large to be shown. |