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.


Notes from Team Vuo

Vuo Pro: 

No — available with both Vuo CE and Vuo Pro


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


●○○ — 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.


Thanks Team Vuo. I'm really

keithlang's picture
Submitted by

Thanks Team Vuo. I'm really hoping to find a way to add this functionality for a current project (which exports to a Mac app). Looking into creating a new Node Class / Library Module…but I'm not sure it's actually possible for a 3rd party (ie me) to create a node that can access mouse data beyond what the API can provide.

Would love if I could know 'it'll never work' vs 'it's doable', to save me some heartbreak 🙂 ?

Thanks. I would say 'kind of'

keithlang's picture
Submitted by

Thanks. I would say 'kind of'. Getting access to the keyboard, at all times, requires enabling that in Settings under accessibility. However, I don't believe the mouse falls under the same constraint. Ie, any app can get the mouse position. This may have changed in 10.15.

Thanks. Theres a distinction

keithlang's picture
Submitted by

Thanks. Theres a distinction between mouse and keyboard on Mac OS. Access to the keyboard at all times requires the user explicitly grant the app access through Accessibility. Mouse (for now) does not. For my project, Mouse will do. Of course others will have other needs.

I don't have any personal

cwilms-loyalist's picture
Submitted by

I don't have any personal interest in the keyboard part of the other feature request but am very interested in the mouse functionality. I think the other request should be separated now to just be for the keyboard since this feature request now has the mouse part covered and is "chosen".

Feature status

  • Submitted to
  • Reviewed by Team Vuo
  • Community voted
  • Scheduled for implementation
  • Released in Vuo 2.3.0

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.

Read more about how Vuo feature requests work.

Who voted?

keithlang's picture