I've made a composition that allows user input only via a microphone. (For an 11-month old who likes to scream with delight!) Because there's no mouse or keyboard interaction, the screen saver keeps coming on and killing the mood. I'm aware that I could disable the screen saver on my computer, but I don't think it's reasonable to expect a user to change system settings to enable an occasionally-used app to function as expected.
I propose that either:
a vuo.window node that creates a window property enabling or disabling the screen saver; or
a setting for all compositions that automatically disables the screen saver when running an app in full screen.
A node to send an event (or data) first to one destination, then to the next (and the next, and the next...)
Working with MIDI as means of controlling other software is near impossible without this function as you often need to trigger an off-signal before triggering an on-signal from the same event source, and it will surely be beneficial in other scenarios as well.