As one of Vuo's developers, I work on Vuo's engine (the thing that makes compositions run), work on nodes, and write documentation. You'll see me on the forums answering people's questions about Vuo.
I've been developing apps and frameworks for several years (since I was in college). Pre-Vuo projects include Kineme Quartz Composer plugins, iOS apps for education, an app that analyzes photographs of tomato slices, and software to help people with disabilities use talking keyboards.
I enjoy using Vuo to make live music visuals. My hope for Vuo is that it will grow into a community of people of diverse backgrounds and identities making lots of different artistic, useful, unique, goofy, beautiful, crafty, wonderful compositions.
We'll add "make" as a keyword of Share Value so it comes up in searches.
Share value and Make value would actually be the same node so perhaps the team left it out to enlighten the library ?
@Bodysoulspirit, yeah, rather than including the same node twice under different names, which could be confusing, we like to use search keywords so the node comes up if you search for either possible name.
If the button presses are coming from outside of Vuo, such as TouchOSC, and each is identified with an index (1-16), you can use Get Item from List in place of Select Input, as shown below and in "Get Item From List as Select.vuo". Get Item from List allows for 16 or even more choices.
If the button presses are coming from Vuo's Make Button node, you can use a combination of two 8-input Select Latest nodes and a 2-input Select Latest node, as shown below and in "Select Latest with names.vuo".
"Select Latest with indices.vuo" additionally shows how to convert a Make Button press to a numerical index (1-16), use the index to check if you should show an image or a movie frame (Select Output), and use the index again to choose the image or movie file (Get Item from List).