aboutsummaryrefslogtreecommitdiffhomepage
path: root/backends/wininput.md
diff options
context:
space:
mode:
authorcbdev <cb@cbcdn.com>2020-06-11 12:27:57 +0200
committercbdev <cb@cbcdn.com>2020-06-11 12:27:57 +0200
commit5e4c3fe5a81f548243aab01a42973333b559004f (patch)
tree2cc9125aa681e6fac7d263413959db1388a97b46 /backends/wininput.md
parente52c67ce0da7c3847d2583c8df6d5f1bd1fecb9e (diff)
downloadmidimonster-5e4c3fe5a81f548243aab01a42973333b559004f.tar.gz
midimonster-5e4c3fe5a81f548243aab01a42973333b559004f.tar.bz2
midimonster-5e4c3fe5a81f548243aab01a42973333b559004f.zip
Query joystick buttons
Diffstat (limited to 'backends/wininput.md')
-rw-r--r--backends/wininput.md5
1 files changed, 4 insertions, 1 deletions
diff --git a/backends/wininput.md b/backends/wininput.md
index 6ead158..6e665bb 100644
--- a/backends/wininput.md
+++ b/backends/wininput.md
@@ -79,8 +79,11 @@ input.X > wi1.key.escape
#### Known bugs / problems
+Joysticks can only be used as input to the MIDIMonster, as Windows does not provide a method to emulate
+Joystick input from user space. This is unlikely to change.
+
Keyboard and mouse input is subject to UIPI. You can not send input to applications that run at a higher
-privilege level than the MIDIMonster.
+privilege level than the MIDIMonster. This limitation is by design and will not change.
Due to inconsistencies in the Windows API, mouse position input and output may differ for the same cursor location.
This may be correlated with the use and arrangement of multi-monitor desktops. If you encounter problems with either