I am the Senior AV Broadcast Technology Analyst at Loyalist College where I primarily design, install and maintain campus AV, Digital Signage and Broadcast systems and equipment. I have also do some teaching for Camera, VFX and Audio/Video editing as well; I love my job. My background includes Broadcast Television, Video Production and Technical work. My passions include traditional and digital drawing, fictional creative writing, VFX, and cinematic video projects. I have also recently rekindled my interest in robotics and have tinkered with Arduino and Raspberry Pi and a few programable robots.
I find I most comfortably find myself in the chaotic limbo between the artistically and technically creative, believing one can indeed excel at both. Which is probably why I am loving VUO! :)
It would be nice if the Slider Node could have a list of real numbers fed into it so the slider can snap to set user chosen increments within the set range for the slider. This would allow say for the slider to be easily positioned at exactly 50%, or at precise 10% increments etc.
I see this feature as having some behaviour options:
1. Snap to List - The slider snaps to only listed values
2. Weighted Snaps - The slider snaps to listed values only when within certain threshold of a listed value, otherwise it can be set freely to non-listed values.
3. Override Snaps Boolean (Default - True) - Allows the listed values to be ignored and frees the slider to be set at any value with its range. Kind of like how holding down in Photoshop temporally turns off snap to guides feature.
I've run into a few instances where I needed to run a composition at specific frame rate and just used the fire periodically node. I just take the frame rate and divide that number into 1 to get the refresh timing.
To really be able to customize the look of a UI it would be a nice addition to have Image Skinning for each button state, with options for stretch to fit, crop and scale.
It would also be cool to allow for even more customized buttons shapes like those in a D-Pad where the buttons are something other than rectangle but I'm not sure what the best implementation for that would be. Maybe by allowing a skins alpha transparency to dictate which parts of the button are press-able?