update to mouse & keyboard nodesApril 5, 2013 posted by: Elias
the mouse and keyboard nodes of vvvv have seen a complete rewrite in the lastest alpha version (29.4). their interface (in- and outputs) and behaviour is still the same, but under the hood they work differently: up till now vvvv installed a so called system wide global hook on startup which rerouted mouse and keyboard messages from other processes to the vvvv process. for reasons beyond the scope of this blog post, this caused random freezes of vvvv or even crashes of other processes. another issue was that it only worked with one vvvv instance at a time. with the new nodes we got rid of those global hooks. in case of the window versions of the nodes we use a much safer technique called subclassing and in case of the global versions the keyboard and mouse states are retrieved at node evaluation.
hopefully this change shouldn’t affect the user at all, if it does, please report in our alpha forum.
what’s probably also worth mentioning is that the mouse nodes now output the state of XButton1 and XButton2.
to plugin developers:
- if you’re writing a gui-plugin (eg. a renderer) and want the window versions of the mouse and keyboard nodes to work with your plugin, implement the new interface IUserInputWindow where you return the window handle of the control which has focus. for an example have a look at the source code of our svg renderer.
- MouseState uses the System.Windows.Forms.MouseButtons enumeration now.
Comments are no longer accepted for this post.
If no functionality is changed this probably means that mouse/keyboard input still won’t work from non-vvvv fullscreen windows (–> “global” is not really “global”?)
E.g. having vvvv in the background as a “do-something-in-the-background-central”. I created a “real” global keyboard hook some time ago (for the vvvv-Unity-connection I was showing at NODE13), because built-in “Keyboard Global” didn’t receive keys from fullscreen Unity. I just uploaded it to contributions: global-keyhookbeta-contribution