mirror of https://github.com/kivy/kivy.git
doc: added ref and link to touch event bubbling from guide/inputs.rst
This commit is contained in:
parent
e3cc847172
commit
6db77e27c1
|
@ -50,9 +50,9 @@ correct faulty input, as well as make meaningful interpretations like:
|
|||
- Reducing the amount of generated events if the native touch hardware is
|
||||
sending events with nearly the same position
|
||||
|
||||
After processing, the motion event is dispatched to the Window. As explained previosuly,
|
||||
not all events are dispatched to the whole widget tree: the window filters them.
|
||||
For a given event:
|
||||
After processing, the motion event is dispatched to the Window. As explained
|
||||
previously, not all events are dispatched to the whole widget tree: the window
|
||||
filters them. For a given event:
|
||||
|
||||
- if it's only a motion event, it will be dispatched to
|
||||
:meth:`~kivy.core.window.WindowBase.on_motion`
|
||||
|
@ -241,3 +241,10 @@ Here is an example of how to use grabbing::
|
|||
|
||||
# and accept the last up
|
||||
return True
|
||||
|
||||
Touch Event Management
|
||||
~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
In order to see how touch events are controlled and propogated between
|
||||
widgets, please refer to the
|
||||
:ref:`Widget touch event bubbling <widget-event-bubbling>` section.
|
|
@ -107,6 +107,8 @@ To draw a background in kv::
|
|||
These examples only scratch the surface. Please see the :mod:`kivy.graphics`
|
||||
documentation for more information.
|
||||
|
||||
.. _widget-event-bubbling:
|
||||
|
||||
Widget touch event bubbling
|
||||
---------------------------
|
||||
|
||||
|
|
Loading…
Reference in New Issue