I’ve encountered an issue that seems to have been discussed already in another topic (linked above), but it doesn’t look like it was resolved; or at least, I don’t see the solution explicitly explained in the topic.
I’m attempting to map MIDI messages to cursor movements; start moving the cursor left on a ‘Note On’ message, stop moving the cursor left at the corresponding ‘Note Off’ message, etc. I’m accomplishing this by activating a timer at the Note On message, and killing the timer at Note Off. The timer is activated with no initial delay, and repeats infinitely every 10ms. When the timer fires, it sends a Mouse Movement message with a Right/Left value of -50px. This is repeated for each cardinal direction.
The basic functionality seems to be working, as I can see the cursor moving around the screen with the corresponding input, but it doesn’t reach the edges of the screen. It’s like there’s an invisible boundary an inch or so inside each edge of the screen. I can move the cursor to the edges of the screen when using a normal mouse, and I can see the ‘Mouse Out’ event is still firing at the bottom of the Bome window, but the cursor stops.
Similar to the linked topic above, my end goal is to use this to control looking/aiming in a video game, but in its current state, I can look around, but only in a very limited area.
As a proof of concept, I tried mapping a different note to move the mouse to the right by 150 pixels (no continuous movement with timers or anything, just move right 150px on ‘Note On’), and I see the same effect where repeated notes will gradually move the mouse right, but only to a particular point near the right edge of the screen, and no further.
Project attached below.
Guitar to Keys Translator.bmtp (6.3 KB)