The new approach of scaling the range of MIDIBuddy action by adjusting the range of the screen area in which MIDIBuddy "notices" mouse movements isn't working for me. Here's the problem, presented as clearly as I can state it:
- Adjust left border of active area this way..... tt=kr/3 , for example.
- Move mouse left so that it approaches the left border of the active (adjusted) area
- During this movement, the X-Axis output correctly decrements (toward value 0)
- Once left border is reached, the output correctly reaches 0.
- Now continue moving mouse left. The output correctly remains at 0.
- During this movement, though the output remains at 0, the feedback to BMT from MIDIBuddy continues to change in response to the continued mouse movement. This is as expected but may be the reason for the problems below.
- Now move the mouse to the right. This should result in immediate incrementing of the output value.
- What happens instead is that the value remains at 0 until the mouse position reaches the adjusted border.
- Once the border has been reached, the output value starts to increment correctly.
So, I think the approach of adjusting the screen area in which MIDIBuddy is responsive to mouse movements doesn't work, for me, at least. The dead zones outside the active screen area are a killer for me.
I will say, though, that somehow, this last fix has actually fixed the problem of over-running the left and right limits when I move the mouse quickly. I can always achieve 0 and 127 now, no matter how quickly I move the mouse.
Is there some way to prevent the dead zones that occur when going outside the active screen area as defined by MIDIBuddy?