I just realized that it is a whole year ago that i failed employing the TodoMap for my Project.
I want it as a solution for handling my presets mainly, and there’s really a lot of gaps to bridge there. So after installing the Visual Studio monster again, here’s a sketch for a
*** ‘Enable’ button for OSC Output is faulty; it’s somehow connected with ‘Enable’ Input button.
*** “add” and “save” buttons are painted black
*** can’t create new Category when adding variable.
*** exception after several OSC enables/disables
*** MinMax is not taken from IOBox
*** Apply deletion to multiple variable selection. (GUI)
*** Allow for editing with multiple selection (Category! MinMax!) (GUI)
*** Take ‘Category’ from IOBox-(Value Advanced)'s Tag
*** Add |Slice| column in OSC mapping to drive different variables with one bundle/spread input (GUI)
*** Add |current value| row. I guess there’s a reason why it is not there, but…
*** Add flag to TodoExposedController-(TodoMap) to make it generate variable names from absolute OSC paths instead of description. At the moment, IOBoxes in multi-instanced subpatches cannot be controlled individually!
*** Add Tag filter to TodoExposedController-(TodoMap) node to add variables to those only.
Realize missing parts:
*** Output Learn Mode, OSC Output.
*** Have map path/name in GUI?
*** Have Preset path/name and Load/Save buttons from GUI?
*** TodoLog tab and Variables tab.
*** Help files with warnings about the pitfalls of disabled components and missing server-(vvvv) node. I guess the author wasn’t thinking of internal controlling. Which makes a lot of sense when it comes to presets.
*** clear out conceptional friction between exposed nodes and TodoMap, especially it’s OSC part.
Thanks for comments and hints to code lines.