Receive Mouse Clicks on Layer

It would be good to have consistency with the 'Receive Mouse...' interaction and add a 'Receive Mouse Clicks on Layer' node. Likewise the 'Receive Mouse Moves' should also have a corresponding 'Receive Mouse Moves on Layer'.

One use case might be a window which contained controls (buttons, sliders, etc) and visual I/O (input/output) layers with mouse interaction restricted to the the I/O layers.

At the moment I can't target mouse moves to a specific layer.

Component: 

Ability to get mouse coordinates, when not active window

Gotta say, the control of Windows is awesome. I'm able to prototype some really cool stuff.

The Vuo window is able to get mouse positions (even outside of its window) when it's frontmost, but not when not frontmost. Request: ability to get mouse coordinates, at all times, regardless of window level. I assume it's not a security issue, since the screen capture node continues to work, even when the Vuo window is not active.

Component: 

Notes from Team Vuo

Vuo Pro: 

No — available with both Vuo CE and Vuo Pro

Complexity: 

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

Potential: 

●○○ — Appeals to current community

Implemented in Vuo version: 

We'll plan to implement this by adding an option to the Receive Mouse Moves node, so compositions can opt-in to tracking mouse coordinates when in the background.

360° image/movie viewer

View a 360° image or movie by dragging the file into this composition's window. Drag the mouse to look around. Scroll to change the field of view.

For best results, images and movies should be equirectangular panoramas (360° on the X axis, 180° on the Y axis).

Composition and supporting files: 

Exported App: 

Continue receiving keyboard events/status even when the composition is not the active application

...Or at least an option to continue receiving this data.

I see four ways to implement this:

  1. 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;
  2. 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;
  3. Create a vuo.window node that allows a composer to set this behaviour for an application window; or
  4. 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.

Component: 

Notes from Team Vuo

Vuo Pro: 

No — available with both Vuo CE and Vuo Pro

Complexity: 

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

Potential: 

●○○ — Appeals to current community

We've changed the title since the mouse part of this FR has been chosen to be implemented.

Pages

Subscribe to RSS - Mouse