If a composer uses a Receive Keyboard Buttons node configured to fire events when a standard keyboard shortcut (such as cmd+Q) is used, the standard behaviour should be disabled.
Alternatively, if the above is not implemented, the composer should receive a warning of some flavour if he or she attempts to use an existing keyboard shortcut in a Vuo composition.
Rather than expanding it to include all possible combinations of modifiers (growing the list of 6 above to a list of 17), would it be possible to have checkboxes and radio buttons or a switch? Something like this:
[ ] Command |
[ ] Option | Checkboxes
[ ] Control |
[ ] Shift |
( ) Any of the above | Radios or
( ) All of the above | a switch
For the "None", just select no checkboxes, (and Vuo can ignore the radios). For the "Any" option, select all checkboxes and the "Any of the above" radio.
Shortcut buttons or hyperlink-style labels could be placed at the top or bottom of the dialog to quickly select all or none of the checkboxes.
...Or at least an option to continue receiving this data.
I see four ways to implement this:
Add a new input port on mouse or keyboard related nodes (such as Receive Mouse Moves) with a boolean value for allowing the data to continue being received by the composition;
Add a new input port on a window related node with a boolean value for allowing the application window to continue allowing mouse or keyboard data to be received by the composition;
Create a vuo.window node that allows a composer to set this behaviour for an application window; or
Create separate mouse or keyboard nodes that will continue to send this data regardless of whether the composition is the active application.
I see 3 as the best option, as it would not require the addition of new nodes or the addition of new ports on existing nodes, but rather a single new node that would plug into a window node in the same way that Change Fullscreen Status and related nodes already work.
In addition, a way to further extend this idea is to also allow the composer to control whether this would also apply if the window were minimized, or if the application were hidden. These properties could be implemented on the same vuo.window node.
Simple flat UI stopwatch with the last runs displayed ...
_
When going fullscreen, then leaving fullscreen again, pressing the keyboard make some finder alert noises. Because the window is not the most active front one then or something. Is there a way to get rid of this ? Just asking :)
