I did a search online and didn't find any use of fluid_cmd_handler_register() except where FluidSynth was included in other projects and API documentation. So at least from an initial look it seems like this function is not really used by other projects.
I think I can see how this could be used though. This could allow for an application to add additional commands to the shell command set, assuming the default command handler instance can be retrieved (didn't check that). Might be useful for an application to extend the default shell commands. I leave it up to you though as to whether you think that is useful or should be handled in another way which doesn't expose the fluid_cmd_t structure. Best regards, Element On Sun, Jan 14, 2018 at 4:56 AM, Tom M. <tom.m...@googlemail.com> wrote: > Is anybody downstream using fluid_cmd_handler_register() to register > custom commands to fluidsynth's command_handler or shell? > > With the current ongoing API revision all public structs are removed from > the API, eventually by providing appropriate getter and setter functions > for those data types. struct fluid_cmd_t is only used by > fluid_cmd_handler_register(). Removing fluid_cmd_handler_register() would > also allow us to remove this struct and make the API a little more > lightweight. > > I cannot think of any use-case for this function, so in case you use > fluid_cmd_handler_register() please let us know. > > > Thanks. > Tom > > _______________________________________________ > fluid-dev mailing list > fluid-dev@nongnu.org > https://lists.nongnu.org/mailman/listinfo/fluid-dev > >
_______________________________________________ fluid-dev mailing list fluid-dev@nongnu.org https://lists.nongnu.org/mailman/listinfo/fluid-dev
