Scrolling generates a mouse up event for previously pressed button instead of scrolling event

[valsr]

Versions

• Python: 3.4.3
• OS: LinuxMint (17.3)
• Kivy: 1.9.1
• Kivy installation method: Package manager

Description

Attempted to use capture mouse wheel events while holding a button down (i.e. press left then scroll up/down using the mouse wheel). In essence kivy converts the first scroll up/down to a mouse up event of the previous button

Expected:

1. Left button down event
2. Mouse wheel event

Actual:

1. Left button down event
2. Left button up event
3. (on continuing scrolling) Mouse wheel event

Code and Logs

To demonstrate:

1. Run application
2. Press and hold left mouse button
3. Scroll the mouse wheel button once (while still holding the left mouse button)

from kivy.uix.boxlayout import BoxLayout
from kivy.uix.textinput import TextInput

from kivy.app import App

class Example(App):

    def __init__(self, **kwargs):
        App.__init__(self, **kwargs)
        self.layout = None
        self.text = None

    def build(self):
        self.layout = BoxLayout()
        self.layout.bind(on_touch_down=self.on_touch_down)
        self.layout.bind(on_touch_up=self.on_touch_up)
        self.text = TextInput(multiline=True)
        self.layout.add_widget(self.text)

        return self.layout

    def on_touch_down(self, widget, touch):
        text = self.text.text
        text += "\n DOWN: " + touch.button
        self.text.text = text

    def on_touch_up(self, widget, touch):
        text = self.text.text
        text += "\n UP: " + touch.button
        self.text.text = text

if __name__ == '__main__':
    Example().run()

[dessant]

It's also not just a scroll issue and it's reproducible with any widget, here is another test case for the example:

1. press and hold left mouse button
2. press and release right mouse button

Expected:
DOWN: left
DOWN: right
UP: right

Actual (Kivy<=1.8.0):
DOWN: left

Actual (Kivy>=1.9.0):
DOWN: left
UP: left

EDIT: The behavior also changes between kivy versions.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[baboosh]

m