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:

  1. a vuo.window node that creates a window property enabling or disabling the screen saver; or
  2. a setting for all compositions that automatically disables the screen saver when running an app in full screen.

Component: 

Notes from Team Vuo

Vuo Pro: 

No — available with both Vuo and Vuo Pro licenses

Complexity: 

●○○○ — Up to a few days of work

Potential: 

●○○ — Appeals to current community

Comments

Opened for voting.

jstrecker's picture
Submitted by
Feature status:
Waiting for review by Team Vuo
»
Open for community voting

Opened for voting.

We're thinking of implementing this as a standalone node, rather than a window property node, since it applies system-wide. Having it as a node rather than an editor setting would enable it to work for exported apps.

Feature status

When we (Team Vuo) plan each release, we try to implement as many of the community's top-voted feature requests as we have time for. Vote your favorite features to the top! (How do Vuo feature requests work?)

  • Submitted to vuo.org
  • Reviewed by Team Vuo
  • Open for community voting
  • Chosen to be implemented
  • Released

Votes

1 vote so far!

Who voted?

Kewl's picture