fdo-mirrors/libinput
1
0
Fork 0
mirror of https://gitlab.freedesktop.org/libinput/libinput.git synced 2026-05-09 08:18:02 +02:00
Code Issues Projects Releases Packages Wiki Activity Actions
libinput/doc/touchpad-tap-state-machine.svg

1211 lines
134 KiB
XML
Raw Permalink Normal View History

touchpad: introduce MULTITAP for multi-tap-and-drag Once we have a doubletap, enter a loop in the state machine where we can tap multiple times and either get a multi-click or a multi-click drag-and-drop. The sequence down/up down/up down/up produces a triple-click. The sequence down/up down/up down/up down produces a triple-click with a button down for dragging. Yes, that glorious octuple-tap-and-drag, it is now possible. World domination has been achieved, thank you for playing. We don't know when we finish tapping now, so add a timeout to send the last click event once the finger has been released for the last time. This guarantees that the timestamp of the last button down is later than the last release. This avoids the bug fixed in synaptics commit xf86-input-synaptics-1.8.0-21-g37d34f0 (some application don't handle doubletap correctly without the timestamps). This works for double-tap immediately, for multi-tap we need to remember the timestamp of the first press event and use it for the release event so that there's a forced gap between the release and the second press. https://bugs.freedesktop.org/show_bug.cgi?id=89511 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-04-16 10:19:11 +10:00
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE svg PUBLIC "-//W3C//DTD SVG 1.1//EN" "http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd">
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<svg xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" width="62220px" height="45863px" version="1.1">
touchpad: disable tapping for fingers exceeding the timeout/motion threshold The current code triggers multi-finger tapping even if the finger released was previously held on the touchpad for a while. For an event sequence of: 1. first finger down 2. first finger move past threshold/wait past timeout 3. second finger down 4. first finger up The second finger initiates the two-finger tap state, but the button event is sent when the first finger releases - despite that finger not meeting the usual tap constraints. This sequence can happen whenever a user swaps fingers. Add the finger state to the actual touchpoints and update them whenever the constrains are broken. Then, discard button events if the respective touch did not meet the conditions. http://bugs.freedesktop.org/76760 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2014-06-20 14:16:13 +10:00
<defs/>
<g transform="translate(0.5,0.5)">
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<path d="M 61382.62 44197 L 62115.92 43740.37" fill="none" stroke="#000000" stroke-miterlimit="10" stroke-dasharray="3 3" pointer-events="none"/>
<path d="M 62120.37 43737.59 L 62116.28 43744.26 L 62115.92 43740.37 L 62112.58 43738.32 Z" fill="#000000" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 61270.26 43182 L 62115.5 43675.47" fill="none" stroke="#000000" stroke-miterlimit="10" stroke-dasharray="3 3" pointer-events="none"/>
<path d="M 62120.03 43678.12 L 62112.22 43677.61 L 62115.5 43675.47 L 62115.75 43671.57 Z" fill="#000000" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 60817.06 44920.5 L 60840.99 44941.77" fill="none" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 60844.91 44945.26 L 60837.36 44943.22 L 60840.99 44941.77 L 60842.01 44937.99 Z" fill="#000000" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<ellipse cx="61229" cy="42882" rx="49.5" ry="30" fill="#ccccff" stroke="#000000" stroke-width="2" pointer-events="none"/>
<g fill="#000000" font-family="Helvetica" text-anchor="middle" font-size="12px">
<text x="61228.75" y="42885.75">
touchpad: end tap-and-drag with an extra tap Currently for the tap-and-drag gesture to end user has to wait for a timeout to expire. Make it possible to end the drag gesture by just tapping. The allowed finger sequences to start and end a drag are thus: tap, down, .... move ...., up <wait for timeout> tap, down, .... move ...., up, tap https://bugs.freedesktop.org/show_bug.cgi?id=90255 Signed-off-by: Velimir Lisec <lisec.velimir@gmail.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> State diagram changes and a doc change squashed in. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-04-30 00:13:51 +02:00
IDLE</text>
touchpad: disable tapping for fingers exceeding the timeout/motion threshold The current code triggers multi-finger tapping even if the finger released was previously held on the touchpad for a while. For an event sequence of: 1. first finger down 2. first finger move past threshold/wait past timeout 3. second finger down 4. first finger up The second finger initiates the two-finger tap state, but the button event is sent when the first finger releases - despite that finger not meeting the usual tap constraints. This sequence can happen whenever a user swaps fingers. Add the finger state to the actual touchpoints and update them whenever the constrains are broken. Then, discard button events if the respective touch did not meet the conditions. http://bugs.freedesktop.org/76760 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2014-06-20 14:16:13 +10:00
</g>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<rect x="61171" y="43142" width="130" height="40" rx="2.4" ry="2.4" fill="#ccffcc" stroke="#000000" stroke-width="2" pointer-events="none"/>
touchpad: disable tapping for fingers exceeding the timeout/motion threshold The current code triggers multi-finger tapping even if the finger released was previously held on the touchpad for a while. For an event sequence of: 1. first finger down 2. first finger move past threshold/wait past timeout 3. second finger down 4. first finger up The second finger initiates the two-finger tap state, but the button event is sent when the first finger releases - despite that finger not meeting the usual tap constraints. This sequence can happen whenever a user swaps fingers. Add the finger state to the actual touchpoints and update them whenever the constrains are broken. Then, discard button events if the respective touch did not meet the conditions. http://bugs.freedesktop.org/76760 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2014-06-20 14:16:13 +10:00
<g fill="#000000" font-family="Helvetica" text-anchor="middle" font-size="12px">
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<text x="61235.75" y="43165.75">
touchpad: end tap-and-drag with an extra tap Currently for the tap-and-drag gesture to end user has to wait for a timeout to expire. Make it possible to end the drag gesture by just tapping. The allowed finger sequences to start and end a drag are thus: tap, down, .... move ...., up <wait for timeout> tap, down, .... move ...., up, tap https://bugs.freedesktop.org/show_bug.cgi?id=90255 Signed-off-by: Velimir Lisec <lisec.velimir@gmail.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> State diagram changes and a doc change squashed in. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-04-30 00:13:51 +02:00
TOUCH</text>
touchpad: disable tapping for fingers exceeding the timeout/motion threshold The current code triggers multi-finger tapping even if the finger released was previously held on the touchpad for a while. For an event sequence of: 1. first finger down 2. first finger move past threshold/wait past timeout 3. second finger down 4. first finger up The second finger initiates the two-finger tap state, but the button event is sent when the first finger releases - despite that finger not meeting the usual tap constraints. This sequence can happen whenever a user swaps fingers. Add the finger state to the actual touchpoints and update them whenever the constrains are broken. Then, discard button events if the respective touch did not meet the conditions. http://bugs.freedesktop.org/76760 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2014-06-20 14:16:13 +10:00
</g>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<path d="M 61205.04 42957 C 61207.84 42953.86 61211.82 42952.05 61216.02 42952 L 61249.99 42952 C 61254.19 42952.05 61258.17 42953.86 61260.97 42957 L 61280.95 42980 C 61281.51 42981.28 61281.51 42982.72 61280.95 42984 L 61260.97 43007 C 61258.17 43010.14 61254.19 43011.95 61249.99 43012 L 61216.02 43012 C 61211.82 43011.95 61207.84 43010.14 61205.04 43007 L 61185.06 42984 C 61184.5 42982.72 61184.5 42981.28 61185.06 42980 L 61205.04 42957 Z" fill="#ffd966" stroke="#000000" stroke-width="2" stroke-miterlimit="10" pointer-events="none"/>
touchpad: disable tapping for fingers exceeding the timeout/motion threshold The current code triggers multi-finger tapping even if the finger released was previously held on the touchpad for a while. For an event sequence of: 1. first finger down 2. first finger move past threshold/wait past timeout 3. second finger down 4. first finger up The second finger initiates the two-finger tap state, but the button event is sent when the first finger releases - despite that finger not meeting the usual tap constraints. This sequence can happen whenever a user swaps fingers. Add the finger state to the actual touchpoints and update them whenever the constrains are broken. Then, discard button events if the respective touch did not meet the conditions. http://bugs.freedesktop.org/76760 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2014-06-20 14:16:13 +10:00
<g fill="#000000" font-family="Helvetica" text-anchor="middle" font-size="12px">
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<text x="61232.75" y="42978.75">
touchpad: end tap-and-drag with an extra tap Currently for the tap-and-drag gesture to end user has to wait for a timeout to expire. Make it possible to end the drag gesture by just tapping. The allowed finger sequences to start and end a drag are thus: tap, down, .... move ...., up <wait for timeout> tap, down, .... move ...., up, tap https://bugs.freedesktop.org/show_bug.cgi?id=90255 Signed-off-by: Velimir Lisec <lisec.velimir@gmail.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> State diagram changes and a doc change squashed in. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-04-30 00:13:51 +02:00
first</text>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<text x="61232.75" y="42992.75">
touchpad: end tap-and-drag with an extra tap Currently for the tap-and-drag gesture to end user has to wait for a timeout to expire. Make it possible to end the drag gesture by just tapping. The allowed finger sequences to start and end a drag are thus: tap, down, .... move ...., up <wait for timeout> tap, down, .... move ...., up, tap https://bugs.freedesktop.org/show_bug.cgi?id=90255 Signed-off-by: Velimir Lisec <lisec.velimir@gmail.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> State diagram changes and a doc change squashed in. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-04-30 00:13:51 +02:00
finger down</text>
touchpad: disable tapping for fingers exceeding the timeout/motion threshold The current code triggers multi-finger tapping even if the finger released was previously held on the touchpad for a while. For an event sequence of: 1. first finger down 2. first finger move past threshold/wait past timeout 3. second finger down 4. first finger up The second finger initiates the two-finger tap state, but the button event is sent when the first finger releases - despite that finger not meeting the usual tap constraints. This sequence can happen whenever a user swaps fingers. Add the finger state to the actual touchpoints and update them whenever the constrains are broken. Then, discard button events if the respective touch did not meet the conditions. http://bugs.freedesktop.org/76760 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2014-06-20 14:16:13 +10:00
</g>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<path d="M 61230.2 42912 L 61231.55 42945.64" fill="none" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 61231.76 42950.88 L 61227.98 42944.03 L 61231.55 42945.64 L 61234.97 42943.75 Z" fill="#000000" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 60935.04 43257 C 60937.84 43253.86 60941.82 43252.05 60946.02 43252 L 60979.99 43252 C 60984.19 43252.05 60988.17 43253.86 60990.97 43257 L 61010.95 43280 C 61011.51 43281.28 61011.51 43282.72 61010.95 43284 L 60990.97 43307 C 60988.17 43310.14 60984.19 43311.95 60979.99 43312 L 60946.02 43312 C 60941.82 43311.95 60937.84 43310.14 60935.04 43307 L 60915.06 43284 C 60914.5 43282.72 60914.5 43281.28 60915.06 43280 L 60935.04 43257 Z" fill="#ffd966" stroke="#000000" stroke-width="2" stroke-miterlimit="10" pointer-events="none"/>
touchpad: disable tapping for fingers exceeding the timeout/motion threshold The current code triggers multi-finger tapping even if the finger released was previously held on the touchpad for a while. For an event sequence of: 1. first finger down 2. first finger move past threshold/wait past timeout 3. second finger down 4. first finger up The second finger initiates the two-finger tap state, but the button event is sent when the first finger releases - despite that finger not meeting the usual tap constraints. This sequence can happen whenever a user swaps fingers. Add the finger state to the actual touchpoints and update them whenever the constrains are broken. Then, discard button events if the respective touch did not meet the conditions. http://bugs.freedesktop.org/76760 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2014-06-20 14:16:13 +10:00
<g fill="#000000" font-family="Helvetica" text-anchor="middle" font-size="12px">
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<text x="60962.75" y="43285.75">
touchpad: end tap-and-drag with an extra tap Currently for the tap-and-drag gesture to end user has to wait for a timeout to expire. Make it possible to end the drag gesture by just tapping. The allowed finger sequences to start and end a drag are thus: tap, down, .... move ...., up <wait for timeout> tap, down, .... move ...., up, tap https://bugs.freedesktop.org/show_bug.cgi?id=90255 Signed-off-by: Velimir Lisec <lisec.velimir@gmail.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> State diagram changes and a doc change squashed in. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-04-30 00:13:51 +02:00
finger up</text>
touchpad: disable tapping for fingers exceeding the timeout/motion threshold The current code triggers multi-finger tapping even if the finger released was previously held on the touchpad for a while. For an event sequence of: 1. first finger down 2. first finger move past threshold/wait past timeout 3. second finger down 4. first finger up The second finger initiates the two-finger tap state, but the button event is sent when the first finger releases - despite that finger not meeting the usual tap constraints. This sequence can happen whenever a user swaps fingers. Add the finger state to the actual touchpoints and update them whenever the constrains are broken. Then, discard button events if the respective touch did not meet the conditions. http://bugs.freedesktop.org/76760 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2014-06-20 14:16:13 +10:00
</g>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<path d="M 61190.5 43182 L 61017.33 43258.12" fill="none" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 61012.52 43260.23 L 61017.52 43254.21 L 61017.33 43258.12 L 61020.34 43260.62 Z" fill="#000000" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 60695.22 43565.1 C 60696.36 43561.9 60698.22 43560.04 60700.18 43560.12 L 60768.64 43560.12 C 60770.2 43560.08 60771.7 43560.63 60772.67 43561.61 C 60773.65 43562.59 60773.99 43563.88 60773.6 43565.1 L 60754.75 43614.9 C 60753.61 43618.1 60751.75 43619.96 60749.79 43619.88 L 60680.34 43619.88 C 60678.95 43619.69 60677.73 43619.05 60676.97 43618.1 C 60676.22 43617.15 60676 43615.99 60676.37 43614.9 Z" fill="#ff6666" stroke="#000000" stroke-width="2" stroke-miterlimit="10" pointer-events="none"/>
touchpad: disable tapping for fingers exceeding the timeout/motion threshold The current code triggers multi-finger tapping even if the finger released was previously held on the touchpad for a while. For an event sequence of: 1. first finger down 2. first finger move past threshold/wait past timeout 3. second finger down 4. first finger up The second finger initiates the two-finger tap state, but the button event is sent when the first finger releases - despite that finger not meeting the usual tap constraints. This sequence can happen whenever a user swaps fingers. Add the finger state to the actual touchpoints and update them whenever the constrains are broken. Then, discard button events if the respective touch did not meet the conditions. http://bugs.freedesktop.org/76760 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2014-06-20 14:16:13 +10:00
<g fill="#000000" font-family="Helvetica" text-anchor="middle" font-size="12px">
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<text x="60724.75" y="43586.75">
touchpad: end tap-and-drag with an extra tap Currently for the tap-and-drag gesture to end user has to wait for a timeout to expire. Make it possible to end the drag gesture by just tapping. The allowed finger sequences to start and end a drag are thus: tap, down, .... move ...., up <wait for timeout> tap, down, .... move ...., up, tap https://bugs.freedesktop.org/show_bug.cgi?id=90255 Signed-off-by: Velimir Lisec <lisec.velimir@gmail.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> State diagram changes and a doc change squashed in. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-04-30 00:13:51 +02:00
button 1</text>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<text x="60724.75" y="43600.75">
touchpad: end tap-and-drag with an extra tap Currently for the tap-and-drag gesture to end user has to wait for a timeout to expire. Make it possible to end the drag gesture by just tapping. The allowed finger sequences to start and end a drag are thus: tap, down, .... move ...., up <wait for timeout> tap, down, .... move ...., up, tap https://bugs.freedesktop.org/show_bug.cgi?id=90255 Signed-off-by: Velimir Lisec <lisec.velimir@gmail.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> State diagram changes and a doc change squashed in. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-04-30 00:13:51 +02:00
press</text>
touchpad: disable tapping for fingers exceeding the timeout/motion threshold The current code triggers multi-finger tapping even if the finger released was previously held on the touchpad for a while. For an event sequence of: 1. first finger down 2. first finger move past threshold/wait past timeout 3. second finger down 4. first finger up The second finger initiates the two-finger tap state, but the button event is sent when the first finger releases - despite that finger not meeting the usual tap constraints. This sequence can happen whenever a user swaps fingers. Add the finger state to the actual touchpoints and update them whenever the constrains are broken. Then, discard button events if the respective touch did not meet the conditions. http://bugs.freedesktop.org/76760 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2014-06-20 14:16:13 +10:00
</g>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<path d="M 61482.54 43257 C 61485.34 43253.86 61489.32 43252.05 61493.52 43252 L 61527.49 43252 C 61531.69 43252.05 61535.67 43253.86 61538.47 43257 L 61558.45 43280 C 61559.01 43281.28 61559.01 43282.72 61558.45 43284 L 61538.47 43307 C 61535.67 43310.14 61531.69 43311.95 61527.49 43312 L 61493.52 43312 C 61489.32 43311.95 61485.34 43310.14 61482.54 43307 L 61462.56 43284 C 61462 43282.72 61462 43281.28 61462.56 43280 L 61482.54 43257 Z" fill="#99ffff" stroke="#000000" stroke-width="2" stroke-miterlimit="10" pointer-events="none"/>
touchpad: disable tapping for fingers exceeding the timeout/motion threshold The current code triggers multi-finger tapping even if the finger released was previously held on the touchpad for a while. For an event sequence of: 1. first finger down 2. first finger move past threshold/wait past timeout 3. second finger down 4. first finger up The second finger initiates the two-finger tap state, but the button event is sent when the first finger releases - despite that finger not meeting the usual tap constraints. This sequence can happen whenever a user swaps fingers. Add the finger state to the actual touchpoints and update them whenever the constrains are broken. Then, discard button events if the respective touch did not meet the conditions. http://bugs.freedesktop.org/76760 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2014-06-20 14:16:13 +10:00
<g fill="#000000" font-family="Helvetica" text-anchor="middle" font-size="12px">
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<text x="61510.25" y="43285.75">
touchpad: end tap-and-drag with an extra tap Currently for the tap-and-drag gesture to end user has to wait for a timeout to expire. Make it possible to end the drag gesture by just tapping. The allowed finger sequences to start and end a drag are thus: tap, down, .... move ...., up <wait for timeout> tap, down, .... move ...., up, tap https://bugs.freedesktop.org/show_bug.cgi?id=90255 Signed-off-by: Velimir Lisec <lisec.velimir@gmail.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> State diagram changes and a doc change squashed in. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-04-30 00:13:51 +02:00
timeout</text>
touchpad: disable tapping for fingers exceeding the timeout/motion threshold The current code triggers multi-finger tapping even if the finger released was previously held on the touchpad for a while. For an event sequence of: 1. first finger down 2. first finger move past threshold/wait past timeout 3. second finger down 4. first finger up The second finger initiates the two-finger tap state, but the button event is sent when the first finger releases - despite that finger not meeting the usual tap constraints. This sequence can happen whenever a user swaps fingers. Add the finger state to the actual touchpoints and update them whenever the constrains are broken. Then, discard button events if the respective touch did not meet the conditions. http://bugs.freedesktop.org/76760 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2014-06-20 14:16:13 +10:00
</g>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<path d="M 61281.75 43182 L 61456.17 43258.25" fill="none" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 61460.98 43260.35 L 61453.16 43260.75 L 61456.17 43258.25 L 61455.96 43254.34 Z" fill="#000000" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 61301.54 43257 C 61304.34 43253.86 61308.32 43252.05 61312.52 43252 L 61346.49 43252 C 61350.69 43252.05 61354.67 43253.86 61357.47 43257 L 61377.45 43280 C 61378.01 43281.28 61378.01 43282.72 61377.45 43284 L 61357.47 43307 C 61354.67 43310.14 61350.69 43311.95 61346.49 43312 L 61312.52 43312 C 61308.32 43311.95 61304.34 43310.14 61301.54 43307 L 61281.56 43284 C 61281 43282.72 61281 43281.28 61281.56 43280 L 61301.54 43257 Z" fill="#67ab9f" stroke="#000000" stroke-width="2" stroke-miterlimit="10" pointer-events="none"/>
touchpad: disable tapping for fingers exceeding the timeout/motion threshold The current code triggers multi-finger tapping even if the finger released was previously held on the touchpad for a while. For an event sequence of: 1. first finger down 2. first finger move past threshold/wait past timeout 3. second finger down 4. first finger up The second finger initiates the two-finger tap state, but the button event is sent when the first finger releases - despite that finger not meeting the usual tap constraints. This sequence can happen whenever a user swaps fingers. Add the finger state to the actual touchpoints and update them whenever the constrains are broken. Then, discard button events if the respective touch did not meet the conditions. http://bugs.freedesktop.org/76760 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2014-06-20 14:16:13 +10:00
<g fill="#000000" font-family="Helvetica" text-anchor="middle" font-size="12px">
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<text x="61329.25" y="43278.75">
touchpad: end tap-and-drag with an extra tap Currently for the tap-and-drag gesture to end user has to wait for a timeout to expire. Make it possible to end the drag gesture by just tapping. The allowed finger sequences to start and end a drag are thus: tap, down, .... move ...., up <wait for timeout> tap, down, .... move ...., up, tap https://bugs.freedesktop.org/show_bug.cgi?id=90255 Signed-off-by: Velimir Lisec <lisec.velimir@gmail.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> State diagram changes and a doc change squashed in. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-04-30 00:13:51 +02:00
move &gt; </text>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<text x="61329.25" y="43292.75">
touchpad: end tap-and-drag with an extra tap Currently for the tap-and-drag gesture to end user has to wait for a timeout to expire. Make it possible to end the drag gesture by just tapping. The allowed finger sequences to start and end a drag are thus: tap, down, .... move ...., up <wait for timeout> tap, down, .... move ...., up, tap https://bugs.freedesktop.org/show_bug.cgi?id=90255 Signed-off-by: Velimir Lisec <lisec.velimir@gmail.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> State diagram changes and a doc change squashed in. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-04-30 00:13:51 +02:00
threshold</text>
touchpad: disable tapping for fingers exceeding the timeout/motion threshold The current code triggers multi-finger tapping even if the finger released was previously held on the touchpad for a while. For an event sequence of: 1. first finger down 2. first finger move past threshold/wait past timeout 3. second finger down 4. first finger up The second finger initiates the two-finger tap state, but the button event is sent when the first finger releases - despite that finger not meeting the usual tap constraints. This sequence can happen whenever a user swaps fingers. Add the finger state to the actual touchpoints and update them whenever the constrains are broken. Then, discard button events if the respective touch did not meet the conditions. http://bugs.freedesktop.org/76760 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2014-06-20 14:16:13 +10:00
</g>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<path d="M 61251.58 43182 L 61302.21 43246.98" fill="none" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 61305.44 43251.12 L 61298.37 43247.75 L 61302.21 43246.98 L 61303.9 43243.45 Z" fill="#000000" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 61112.54 43257 C 61115.34 43253.86 61119.32 43252.05 61123.52 43252 L 61157.49 43252 C 61161.69 43252.05 61165.67 43253.86 61168.47 43257 L 61188.45 43280 C 61189.01 43281.28 61189.01 43282.72 61188.45 43284 L 61168.47 43307 C 61165.67 43310.14 61161.69 43311.95 61157.49 43312 L 61123.52 43312 C 61119.32 43311.95 61115.34 43310.14 61112.54 43307 L 61092.56 43284 C 61092 43282.72 61092 43281.28 61092.56 43280 L 61112.54 43257 Z" fill="#7ea6e0" stroke="#000000" stroke-width="2" stroke-miterlimit="10" pointer-events="none"/>
touchpad: disable tapping for fingers exceeding the timeout/motion threshold The current code triggers multi-finger tapping even if the finger released was previously held on the touchpad for a while. For an event sequence of: 1. first finger down 2. first finger move past threshold/wait past timeout 3. second finger down 4. first finger up The second finger initiates the two-finger tap state, but the button event is sent when the first finger releases - despite that finger not meeting the usual tap constraints. This sequence can happen whenever a user swaps fingers. Add the finger state to the actual touchpoints and update them whenever the constrains are broken. Then, discard button events if the respective touch did not meet the conditions. http://bugs.freedesktop.org/76760 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2014-06-20 14:16:13 +10:00
<g fill="#000000" font-family="Helvetica" text-anchor="middle" font-size="12px">
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<text x="61140.25" y="43278.75">
touchpad: end tap-and-drag with an extra tap Currently for the tap-and-drag gesture to end user has to wait for a timeout to expire. Make it possible to end the drag gesture by just tapping. The allowed finger sequences to start and end a drag are thus: tap, down, .... move ...., up <wait for timeout> tap, down, .... move ...., up, tap https://bugs.freedesktop.org/show_bug.cgi?id=90255 Signed-off-by: Velimir Lisec <lisec.velimir@gmail.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> State diagram changes and a doc change squashed in. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-04-30 00:13:51 +02:00
second</text>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<text x="61140.25" y="43292.75">
touchpad: end tap-and-drag with an extra tap Currently for the tap-and-drag gesture to end user has to wait for a timeout to expire. Make it possible to end the drag gesture by just tapping. The allowed finger sequences to start and end a drag are thus: tap, down, .... move ...., up <wait for timeout> tap, down, .... move ...., up, tap https://bugs.freedesktop.org/show_bug.cgi?id=90255 Signed-off-by: Velimir Lisec <lisec.velimir@gmail.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> State diagram changes and a doc change squashed in. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-04-30 00:13:51 +02:00
finger down</text>
touchpad: disable tapping for fingers exceeding the timeout/motion threshold The current code triggers multi-finger tapping even if the finger released was previously held on the touchpad for a while. For an event sequence of: 1. first finger down 2. first finger move past threshold/wait past timeout 3. second finger down 4. first finger up The second finger initiates the two-finger tap state, but the button event is sent when the first finger releases - despite that finger not meeting the usual tap constraints. This sequence can happen whenever a user swaps fingers. Add the finger state to the actual touchpoints and update them whenever the constrains are broken. Then, discard button events if the respective touch did not meet the conditions. http://bugs.freedesktop.org/76760 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2014-06-20 14:16:13 +10:00
</g>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<path d="M 61220.08 43182 L 61168.34 43247.02" fill="none" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 61165.07 43251.13 L 61166.69 43243.47 L 61168.34 43247.02 L 61172.17 43247.83 Z" fill="#000000" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<rect x="61316" y="43697" width="130" height="40" rx="2.4" ry="2.4" fill="#ccffcc" stroke="#000000" stroke-width="2" pointer-events="none"/>
touchpad: disable tapping for fingers exceeding the timeout/motion threshold The current code triggers multi-finger tapping even if the finger released was previously held on the touchpad for a while. For an event sequence of: 1. first finger down 2. first finger move past threshold/wait past timeout 3. second finger down 4. first finger up The second finger initiates the two-finger tap state, but the button event is sent when the first finger releases - despite that finger not meeting the usual tap constraints. This sequence can happen whenever a user swaps fingers. Add the finger state to the actual touchpoints and update them whenever the constrains are broken. Then, discard button events if the respective touch did not meet the conditions. http://bugs.freedesktop.org/76760 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2014-06-20 14:16:13 +10:00
<g fill="#000000" font-family="Helvetica" text-anchor="middle" font-size="12px">
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<text x="61380.75" y="43720.75">
touchpad: end tap-and-drag with an extra tap Currently for the tap-and-drag gesture to end user has to wait for a timeout to expire. Make it possible to end the drag gesture by just tapping. The allowed finger sequences to start and end a drag are thus: tap, down, .... move ...., up <wait for timeout> tap, down, .... move ...., up, tap https://bugs.freedesktop.org/show_bug.cgi?id=90255 Signed-off-by: Velimir Lisec <lisec.velimir@gmail.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> State diagram changes and a doc change squashed in. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-04-30 00:13:51 +02:00
TOUCH_2</text>
touchpad: disable tapping for fingers exceeding the timeout/motion threshold The current code triggers multi-finger tapping even if the finger released was previously held on the touchpad for a while. For an event sequence of: 1. first finger down 2. first finger move past threshold/wait past timeout 3. second finger down 4. first finger up The second finger initiates the two-finger tap state, but the button event is sent when the first finger releases - despite that finger not meeting the usual tap constraints. This sequence can happen whenever a user swaps fingers. Add the finger state to the actual touchpoints and update them whenever the constrains are broken. Then, discard button events if the respective touch did not meet the conditions. http://bugs.freedesktop.org/76760 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2014-06-20 14:16:13 +10:00
</g>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<path d="M 61176.04 43768 C 61178.84 43764.86 61182.82 43763.05 61187.02 43763 L 61220.99 43763 C 61225.19 43763.05 61229.17 43764.86 61231.97 43768 L 61251.95 43791 C 61252.51 43792.28 61252.51 43793.72 61251.95 43795 L 61231.97 43818 C 61229.17 43821.14 61225.19 43822.95 61220.99 43823 L 61187.02 43823 C 61182.82 43822.95 61178.84 43821.14 61176.04 43818 L 61156.06 43795 C 61155.5 43793.72 61155.5 43792.28 61156.06 43791 L 61176.04 43768 Z" fill="#7ea6e0" stroke="#000000" stroke-width="2" stroke-miterlimit="10" pointer-events="none"/>
touchpad: disable tapping for fingers exceeding the timeout/motion threshold The current code triggers multi-finger tapping even if the finger released was previously held on the touchpad for a while. For an event sequence of: 1. first finger down 2. first finger move past threshold/wait past timeout 3. second finger down 4. first finger up The second finger initiates the two-finger tap state, but the button event is sent when the first finger releases - despite that finger not meeting the usual tap constraints. This sequence can happen whenever a user swaps fingers. Add the finger state to the actual touchpoints and update them whenever the constrains are broken. Then, discard button events if the respective touch did not meet the conditions. http://bugs.freedesktop.org/76760 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2014-06-20 14:16:13 +10:00
<g fill="#000000" font-family="Helvetica" text-anchor="middle" font-size="12px">
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<text x="61203.75" y="43789.75">
touchpad: end tap-and-drag with an extra tap Currently for the tap-and-drag gesture to end user has to wait for a timeout to expire. Make it possible to end the drag gesture by just tapping. The allowed finger sequences to start and end a drag are thus: tap, down, .... move ...., up <wait for timeout> tap, down, .... move ...., up, tap https://bugs.freedesktop.org/show_bug.cgi?id=90255 Signed-off-by: Velimir Lisec <lisec.velimir@gmail.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> State diagram changes and a doc change squashed in. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-04-30 00:13:51 +02:00
second</text>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<text x="61203.75" y="43803.75">
touchpad: end tap-and-drag with an extra tap Currently for the tap-and-drag gesture to end user has to wait for a timeout to expire. Make it possible to end the drag gesture by just tapping. The allowed finger sequences to start and end a drag are thus: tap, down, .... move ...., up <wait for timeout> tap, down, .... move ...., up, tap https://bugs.freedesktop.org/show_bug.cgi?id=90255 Signed-off-by: Velimir Lisec <lisec.velimir@gmail.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> State diagram changes and a doc change squashed in. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-04-30 00:13:51 +02:00
finger up</text>
touchpad: disable tapping for fingers exceeding the timeout/motion threshold The current code triggers multi-finger tapping even if the finger released was previously held on the touchpad for a while. For an event sequence of: 1. first finger down 2. first finger move past threshold/wait past timeout 3. second finger down 4. first finger up The second finger initiates the two-finger tap state, but the button event is sent when the first finger releases - despite that finger not meeting the usual tap constraints. This sequence can happen whenever a user swaps fingers. Add the finger state to the actual touchpoints and update them whenever the constrains are broken. Then, discard button events if the respective touch did not meet the conditions. http://bugs.freedesktop.org/76760 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2014-06-20 14:16:13 +10:00
</g>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<path d="M 61334.42 43737 L 61258.35 43769.66" fill="none" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 61253.53 43771.73 L 61258.58 43765.76 L 61258.35 43769.66 L 61261.34 43772.19 Z" fill="#000000" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 60780.22 43247.1 C 60781.36 43243.9 60783.22 43242.04 60785.18 43242.12 L 60853.64 43242.12 C 60855.2 43242.08 60856.7 43242.63 60857.67 43243.61 C 60858.65 43244.59 60858.99 43245.88 60858.6 43247.1 L 60839.75 43296.9 C 60838.61 43300.1 60836.75 43301.96 60834.79 43301.88 L 60765.34 43301.88 C 60763.95 43301.69 60762.73 43301.05 60761.97 43300.1 C 60761.22 43299.15 60761 43297.99 60761.37 43296.9 Z" fill="#ff6666" stroke="#000000" stroke-width="2" stroke-miterlimit="10" pointer-events="none"/>
touchpad: disable tapping for fingers exceeding the timeout/motion threshold The current code triggers multi-finger tapping even if the finger released was previously held on the touchpad for a while. For an event sequence of: 1. first finger down 2. first finger move past threshold/wait past timeout 3. second finger down 4. first finger up The second finger initiates the two-finger tap state, but the button event is sent when the first finger releases - despite that finger not meeting the usual tap constraints. This sequence can happen whenever a user swaps fingers. Add the finger state to the actual touchpoints and update them whenever the constrains are broken. Then, discard button events if the respective touch did not meet the conditions. http://bugs.freedesktop.org/76760 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2014-06-20 14:16:13 +10:00
<g fill="#000000" font-family="Helvetica" text-anchor="middle" font-size="12px">
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<text x="60809.75" y="43268.75">
touchpad: end tap-and-drag with an extra tap Currently for the tap-and-drag gesture to end user has to wait for a timeout to expire. Make it possible to end the drag gesture by just tapping. The allowed finger sequences to start and end a drag are thus: tap, down, .... move ...., up <wait for timeout> tap, down, .... move ...., up, tap https://bugs.freedesktop.org/show_bug.cgi?id=90255 Signed-off-by: Velimir Lisec <lisec.velimir@gmail.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> State diagram changes and a doc change squashed in. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-04-30 00:13:51 +02:00
button 2</text>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<text x="60809.75" y="43282.75">
touchpad: end tap-and-drag with an extra tap Currently for the tap-and-drag gesture to end user has to wait for a timeout to expire. Make it possible to end the drag gesture by just tapping. The allowed finger sequences to start and end a drag are thus: tap, down, .... move ...., up <wait for timeout> tap, down, .... move ...., up, tap https://bugs.freedesktop.org/show_bug.cgi?id=90255 Signed-off-by: Velimir Lisec <lisec.velimir@gmail.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> State diagram changes and a doc change squashed in. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-04-30 00:13:51 +02:00
press</text>
touchpad: disable tapping for fingers exceeding the timeout/motion threshold The current code triggers multi-finger tapping even if the finger released was previously held on the touchpad for a while. For an event sequence of: 1. first finger down 2. first finger move past threshold/wait past timeout 3. second finger down 4. first finger up The second finger initiates the two-finger tap state, but the button event is sent when the first finger releases - despite that finger not meeting the usual tap constraints. This sequence can happen whenever a user swaps fingers. Add the finger state to the actual touchpoints and update them whenever the constrains are broken. Then, discard button events if the respective touch did not meet the conditions. http://bugs.freedesktop.org/76760 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2014-06-20 14:16:13 +10:00
</g>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<path d="M 61475.54 43812 C 61478.34 43808.86 61482.32 43807.05 61486.52 43807 L 61520.49 43807 C 61524.69 43807.05 61528.67 43808.86 61531.47 43812 L 61551.45 43835 C 61552.01 43836.28 61552.01 43837.72 61551.45 43839 L 61531.47 43862 C 61528.67 43865.14 61524.69 43866.95 61520.49 43867 L 61486.52 43867 C 61482.32 43866.95 61478.34 43865.14 61475.54 43862 L 61455.56 43839 C 61455 43837.72 61455 43836.28 61455.56 43835 L 61475.54 43812 Z" fill="#67ab9f" stroke="#000000" stroke-width="2" stroke-miterlimit="10" pointer-events="none"/>
touchpad: disable tapping for fingers exceeding the timeout/motion threshold The current code triggers multi-finger tapping even if the finger released was previously held on the touchpad for a while. For an event sequence of: 1. first finger down 2. first finger move past threshold/wait past timeout 3. second finger down 4. first finger up The second finger initiates the two-finger tap state, but the button event is sent when the first finger releases - despite that finger not meeting the usual tap constraints. This sequence can happen whenever a user swaps fingers. Add the finger state to the actual touchpoints and update them whenever the constrains are broken. Then, discard button events if the respective touch did not meet the conditions. http://bugs.freedesktop.org/76760 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2014-06-20 14:16:13 +10:00
<g fill="#000000" font-family="Helvetica" text-anchor="middle" font-size="12px">
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<text x="61503.25" y="43833.75">
touchpad: end tap-and-drag with an extra tap Currently for the tap-and-drag gesture to end user has to wait for a timeout to expire. Make it possible to end the drag gesture by just tapping. The allowed finger sequences to start and end a drag are thus: tap, down, .... move ...., up <wait for timeout> tap, down, .... move ...., up, tap https://bugs.freedesktop.org/show_bug.cgi?id=90255 Signed-off-by: Velimir Lisec <lisec.velimir@gmail.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> State diagram changes and a doc change squashed in. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-04-30 00:13:51 +02:00
move &gt; </text>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<text x="61503.25" y="43847.75">
touchpad: end tap-and-drag with an extra tap Currently for the tap-and-drag gesture to end user has to wait for a timeout to expire. Make it possible to end the drag gesture by just tapping. The allowed finger sequences to start and end a drag are thus: tap, down, .... move ...., up <wait for timeout> tap, down, .... move ...., up, tap https://bugs.freedesktop.org/show_bug.cgi?id=90255 Signed-off-by: Velimir Lisec <lisec.velimir@gmail.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> State diagram changes and a doc change squashed in. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-04-30 00:13:51 +02:00
threshold</text>
touchpad: disable tapping for fingers exceeding the timeout/motion threshold The current code triggers multi-finger tapping even if the finger released was previously held on the touchpad for a while. For an event sequence of: 1. first finger down 2. first finger move past threshold/wait past timeout 3. second finger down 4. first finger up The second finger initiates the two-finger tap state, but the button event is sent when the first finger releases - despite that finger not meeting the usual tap constraints. This sequence can happen whenever a user swaps fingers. Add the finger state to the actual touchpoints and update them whenever the constrains are broken. Then, discard button events if the respective touch did not meet the conditions. http://bugs.freedesktop.org/76760 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2014-06-20 14:16:13 +10:00
</g>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<path d="M 61601.54 43752 C 61604.34 43748.86 61608.32 43747.05 61612.52 43747 L 61646.49 43747 C 61650.69 43747.05 61654.67 43748.86 61657.47 43752 L 61677.45 43775 C 61678.01 43776.28 61678.01 43777.72 61677.45 43779 L 61657.47 43802 C 61654.67 43805.14 61650.69 43806.95 61646.49 43807 L 61612.52 43807 C 61608.32 43806.95 61604.34 43805.14 61601.54 43802 L 61581.56 43779 C 61581 43777.72 61581 43776.28 61581.56 43775 L 61601.54 43752 Z" fill="#99ffff" stroke="#000000" stroke-width="2" stroke-miterlimit="10" pointer-events="none"/>
touchpad: disable tapping for fingers exceeding the timeout/motion threshold The current code triggers multi-finger tapping even if the finger released was previously held on the touchpad for a while. For an event sequence of: 1. first finger down 2. first finger move past threshold/wait past timeout 3. second finger down 4. first finger up The second finger initiates the two-finger tap state, but the button event is sent when the first finger releases - despite that finger not meeting the usual tap constraints. This sequence can happen whenever a user swaps fingers. Add the finger state to the actual touchpoints and update them whenever the constrains are broken. Then, discard button events if the respective touch did not meet the conditions. http://bugs.freedesktop.org/76760 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2014-06-20 14:16:13 +10:00
<g fill="#000000" font-family="Helvetica" text-anchor="middle" font-size="12px">
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<text x="61629.25" y="43780.75">
touchpad: end tap-and-drag with an extra tap Currently for the tap-and-drag gesture to end user has to wait for a timeout to expire. Make it possible to end the drag gesture by just tapping. The allowed finger sequences to start and end a drag are thus: tap, down, .... move ...., up <wait for timeout> tap, down, .... move ...., up, tap https://bugs.freedesktop.org/show_bug.cgi?id=90255 Signed-off-by: Velimir Lisec <lisec.velimir@gmail.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> State diagram changes and a doc change squashed in. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-04-30 00:13:51 +02:00
timeout</text>
touchpad: disable tapping for fingers exceeding the timeout/motion threshold The current code triggers multi-finger tapping even if the finger released was previously held on the touchpad for a while. For an event sequence of: 1. first finger down 2. first finger move past threshold/wait past timeout 3. second finger down 4. first finger up The second finger initiates the two-finger tap state, but the button event is sent when the first finger releases - despite that finger not meeting the usual tap constraints. This sequence can happen whenever a user swaps fingers. Add the finger state to the actual touchpoints and update them whenever the constrains are broken. Then, discard button events if the respective touch did not meet the conditions. http://bugs.freedesktop.org/76760 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2014-06-20 14:16:13 +10:00
</g>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<path d="M 61446 43732.69 L 61574.81 43763.8" fill="none" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 61579.91 43765.03 L 61572.29 43766.79 L 61574.81 43763.8 L 61573.93 43759.98 Z" fill="#000000" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 61401.42 43737 L 61468.33 43802.54" fill="none" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 61472.08 43806.22 L 61464.63 43803.82 L 61468.33 43802.54 L 61469.53 43798.82 Z" fill="#000000" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 60914.72 43992.1 C 60915.86 43988.9 60917.72 43987.04 60919.68 43987.12 L 60988.14 43987.12 C 60989.7 43987.08 60991.2 43987.63 60992.17 43988.61 C 60993.15 43989.59 60993.49 43990.88 60993.1 43992.1 L 60974.25 44041.9 C 60973.11 44045.1 60971.25 44046.96 60969.29 44046.88 L 60899.84 44046.88 C 60898.45 44046.69 60897.23 44046.05 60896.47 44045.1 C 60895.72 44044.15 60895.5 44042.99 60895.87 44041.9 Z" fill="#ff6666" stroke="#000000" stroke-width="2" stroke-miterlimit="10" pointer-events="none"/>
touchpad: disable tapping for fingers exceeding the timeout/motion threshold The current code triggers multi-finger tapping even if the finger released was previously held on the touchpad for a while. For an event sequence of: 1. first finger down 2. first finger move past threshold/wait past timeout 3. second finger down 4. first finger up The second finger initiates the two-finger tap state, but the button event is sent when the first finger releases - despite that finger not meeting the usual tap constraints. This sequence can happen whenever a user swaps fingers. Add the finger state to the actual touchpoints and update them whenever the constrains are broken. Then, discard button events if the respective touch did not meet the conditions. http://bugs.freedesktop.org/76760 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2014-06-20 14:16:13 +10:00
<g fill="#000000" font-family="Helvetica" text-anchor="middle" font-size="12px">
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<text x="60944.25" y="44013.75">
touchpad: end tap-and-drag with an extra tap Currently for the tap-and-drag gesture to end user has to wait for a timeout to expire. Make it possible to end the drag gesture by just tapping. The allowed finger sequences to start and end a drag are thus: tap, down, .... move ...., up <wait for timeout> tap, down, .... move ...., up, tap https://bugs.freedesktop.org/show_bug.cgi?id=90255 Signed-off-by: Velimir Lisec <lisec.velimir@gmail.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> State diagram changes and a doc change squashed in. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-04-30 00:13:51 +02:00
button 1</text>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<text x="60944.25" y="44027.75">
touchpad: end tap-and-drag with an extra tap Currently for the tap-and-drag gesture to end user has to wait for a timeout to expire. Make it possible to end the drag gesture by just tapping. The allowed finger sequences to start and end a drag are thus: tap, down, .... move ...., up <wait for timeout> tap, down, .... move ...., up, tap https://bugs.freedesktop.org/show_bug.cgi?id=90255 Signed-off-by: Velimir Lisec <lisec.velimir@gmail.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> State diagram changes and a doc change squashed in. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-04-30 00:13:51 +02:00
release</text>
touchpad: disable tapping for fingers exceeding the timeout/motion threshold The current code triggers multi-finger tapping even if the finger released was previously held on the touchpad for a while. For an event sequence of: 1. first finger down 2. first finger move past threshold/wait past timeout 3. second finger down 4. first finger up The second finger initiates the two-finger tap state, but the button event is sent when the first finger releases - despite that finger not meeting the usual tap constraints. This sequence can happen whenever a user swaps fingers. Add the finger state to the actual touchpoints and update them whenever the constrains are broken. Then, discard button events if the respective touch did not meet the conditions. http://bugs.freedesktop.org/76760 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2014-06-20 14:16:13 +10:00
</g>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<path d="M 60816.72 43147.1 C 60817.86 43143.9 60819.72 43142.04 60821.68 43142.12 L 60890.14 43142.12 C 60891.7 43142.08 60893.2 43142.63 60894.17 43143.61 C 60895.15 43144.59 60895.49 43145.88 60895.1 43147.1 L 60876.25 43196.9 C 60875.11 43200.1 60873.25 43201.96 60871.29 43201.88 L 60801.84 43201.88 C 60800.45 43201.69 60799.23 43201.05 60798.47 43200.1 C 60797.72 43199.15 60797.5 43197.99 60797.87 43196.9 Z" fill="#ff6666" stroke="#000000" stroke-width="2" stroke-miterlimit="10" pointer-events="none"/>
touchpad: disable tapping for fingers exceeding the timeout/motion threshold The current code triggers multi-finger tapping even if the finger released was previously held on the touchpad for a while. For an event sequence of: 1. first finger down 2. first finger move past threshold/wait past timeout 3. second finger down 4. first finger up The second finger initiates the two-finger tap state, but the button event is sent when the first finger releases - despite that finger not meeting the usual tap constraints. This sequence can happen whenever a user swaps fingers. Add the finger state to the actual touchpoints and update them whenever the constrains are broken. Then, discard button events if the respective touch did not meet the conditions. http://bugs.freedesktop.org/76760 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2014-06-20 14:16:13 +10:00
<g fill="#000000" font-family="Helvetica" text-anchor="middle" font-size="12px">
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<text x="60846.25" y="43168.75">
touchpad: end tap-and-drag with an extra tap Currently for the tap-and-drag gesture to end user has to wait for a timeout to expire. Make it possible to end the drag gesture by just tapping. The allowed finger sequences to start and end a drag are thus: tap, down, .... move ...., up <wait for timeout> tap, down, .... move ...., up, tap https://bugs.freedesktop.org/show_bug.cgi?id=90255 Signed-off-by: Velimir Lisec <lisec.velimir@gmail.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> State diagram changes and a doc change squashed in. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-04-30 00:13:51 +02:00
button 2</text>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<text x="60846.25" y="43182.75">
touchpad: end tap-and-drag with an extra tap Currently for the tap-and-drag gesture to end user has to wait for a timeout to expire. Make it possible to end the drag gesture by just tapping. The allowed finger sequences to start and end a drag are thus: tap, down, .... move ...., up <wait for timeout> tap, down, .... move ...., up, tap https://bugs.freedesktop.org/show_bug.cgi?id=90255 Signed-off-by: Velimir Lisec <lisec.velimir@gmail.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> State diagram changes and a doc change squashed in. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-04-30 00:13:51 +02:00
release</text>
touchpad: disable tapping for fingers exceeding the timeout/motion threshold The current code triggers multi-finger tapping even if the finger released was previously held on the touchpad for a while. For an event sequence of: 1. first finger down 2. first finger move past threshold/wait past timeout 3. second finger down 4. first finger up The second finger initiates the two-finger tap state, but the button event is sent when the first finger releases - despite that finger not meeting the usual tap constraints. This sequence can happen whenever a user swaps fingers. Add the finger state to the actual touchpoints and update them whenever the constrains are broken. Then, discard button events if the respective touch did not meet the conditions. http://bugs.freedesktop.org/76760 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2014-06-20 14:16:13 +10:00
</g>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<path d="M 61124.58 43597.5 L 61071.42 43541.61" fill="none" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 61067.8 43537.81 L 61075.16 43540.47 L 61071.42 43541.61 L 61070.09 43545.29 Z" fill="#000000" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 60820.95 43242 L 60833.37 43207.98" fill="none" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 60835.17 43203.05 L 60836.05 43210.83 L 60833.37 43207.98 L 60829.48 43208.43 Z" fill="#000000" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<rect x="60666" y="43745" width="130" height="40" rx="2.4" ry="2.4" fill="#ccffcc" stroke="#000000" stroke-width="2" pointer-events="none"/>
touchpad: disable tapping for fingers exceeding the timeout/motion threshold The current code triggers multi-finger tapping even if the finger released was previously held on the touchpad for a while. For an event sequence of: 1. first finger down 2. first finger move past threshold/wait past timeout 3. second finger down 4. first finger up The second finger initiates the two-finger tap state, but the button event is sent when the first finger releases - despite that finger not meeting the usual tap constraints. This sequence can happen whenever a user swaps fingers. Add the finger state to the actual touchpoints and update them whenever the constrains are broken. Then, discard button events if the respective touch did not meet the conditions. http://bugs.freedesktop.org/76760 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2014-06-20 14:16:13 +10:00
<g fill="#000000" font-family="Helvetica" text-anchor="middle" font-size="12px">
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<text x="60730.75" y="43768.75">
touchpad: end tap-and-drag with an extra tap Currently for the tap-and-drag gesture to end user has to wait for a timeout to expire. Make it possible to end the drag gesture by just tapping. The allowed finger sequences to start and end a drag are thus: tap, down, .... move ...., up <wait for timeout> tap, down, .... move ...., up, tap https://bugs.freedesktop.org/show_bug.cgi?id=90255 Signed-off-by: Velimir Lisec <lisec.velimir@gmail.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> State diagram changes and a doc change squashed in. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-04-30 00:13:51 +02:00
TAPPED</text>
touchpad: disable tapping for fingers exceeding the timeout/motion threshold The current code triggers multi-finger tapping even if the finger released was previously held on the touchpad for a while. For an event sequence of: 1. first finger down 2. first finger move past threshold/wait past timeout 3. second finger down 4. first finger up The second finger initiates the two-finger tap state, but the button event is sent when the first finger releases - despite that finger not meeting the usual tap constraints. This sequence can happen whenever a user swaps fingers. Add the finger state to the actual touchpoints and update them whenever the constrains are broken. Then, discard button events if the respective touch did not meet the conditions. http://bugs.freedesktop.org/76760 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2014-06-20 14:16:13 +10:00
</g>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<path d="M 60872.04 43868 C 60874.84 43864.86 60878.82 43863.05 60883.02 43863 L 60916.99 43863 C 60921.19 43863.05 60925.17 43864.86 60927.97 43868 L 60947.95 43891 C 60948.51 43892.28 60948.51 43893.72 60947.95 43895 L 60927.97 43918 C 60925.17 43921.14 60921.19 43922.95 60916.99 43923 L 60883.02 43923 C 60878.82 43922.95 60874.84 43921.14 60872.04 43918 L 60852.06 43895 C 60851.5 43893.72 60851.5 43892.28 60852.06 43891 L 60872.04 43868 Z" fill="#99ffff" stroke="#000000" stroke-width="2" stroke-miterlimit="10" pointer-events="none"/>
touchpad: disable tapping for fingers exceeding the timeout/motion threshold The current code triggers multi-finger tapping even if the finger released was previously held on the touchpad for a while. For an event sequence of: 1. first finger down 2. first finger move past threshold/wait past timeout 3. second finger down 4. first finger up The second finger initiates the two-finger tap state, but the button event is sent when the first finger releases - despite that finger not meeting the usual tap constraints. This sequence can happen whenever a user swaps fingers. Add the finger state to the actual touchpoints and update them whenever the constrains are broken. Then, discard button events if the respective touch did not meet the conditions. http://bugs.freedesktop.org/76760 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2014-06-20 14:16:13 +10:00
<g fill="#000000" font-family="Helvetica" text-anchor="middle" font-size="12px">
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<text x="60899.75" y="43896.75">
touchpad: end tap-and-drag with an extra tap Currently for the tap-and-drag gesture to end user has to wait for a timeout to expire. Make it possible to end the drag gesture by just tapping. The allowed finger sequences to start and end a drag are thus: tap, down, .... move ...., up <wait for timeout> tap, down, .... move ...., up, tap https://bugs.freedesktop.org/show_bug.cgi?id=90255 Signed-off-by: Velimir Lisec <lisec.velimir@gmail.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> State diagram changes and a doc change squashed in. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-04-30 00:13:51 +02:00
timeout</text>
touchpad: disable tapping for fingers exceeding the timeout/motion threshold The current code triggers multi-finger tapping even if the finger released was previously held on the touchpad for a while. For an event sequence of: 1. first finger down 2. first finger move past threshold/wait past timeout 3. second finger down 4. first finger up The second finger initiates the two-finger tap state, but the button event is sent when the first finger releases - despite that finger not meeting the usual tap constraints. This sequence can happen whenever a user swaps fingers. Add the finger state to the actual touchpoints and update them whenever the constrains are broken. Then, discard button events if the respective touch did not meet the conditions. http://bugs.freedesktop.org/76760 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2014-06-20 14:16:13 +10:00
</g>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<path d="M 60757.41 43785 L 60855.31 43859.16" fill="none" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 60859.5 43862.32 L 60851.81 43860.89 L 60855.31 43859.16 L 60856.03 43855.31 Z" fill="#000000" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 60666.54 43848 C 60669.34 43844.86 60673.32 43843.05 60677.52 43843 L 60711.49 43843 C 60715.69 43843.05 60719.67 43844.86 60722.47 43848 L 60742.45 43871 C 60743.01 43872.28 60743.01 43873.72 60742.45 43875 L 60722.47 43898 C 60719.67 43901.14 60715.69 43902.95 60711.49 43903 L 60677.52 43903 C 60673.32 43902.95 60669.34 43901.14 60666.54 43898 L 60646.56 43875 C 60646 43873.72 60646 43872.28 60646.56 43871 L 60666.54 43848 Z" fill="#ffd966" stroke="#000000" stroke-width="2" stroke-miterlimit="10" pointer-events="none"/>
touchpad: disable tapping for fingers exceeding the timeout/motion threshold The current code triggers multi-finger tapping even if the finger released was previously held on the touchpad for a while. For an event sequence of: 1. first finger down 2. first finger move past threshold/wait past timeout 3. second finger down 4. first finger up The second finger initiates the two-finger tap state, but the button event is sent when the first finger releases - despite that finger not meeting the usual tap constraints. This sequence can happen whenever a user swaps fingers. Add the finger state to the actual touchpoints and update them whenever the constrains are broken. Then, discard button events if the respective touch did not meet the conditions. http://bugs.freedesktop.org/76760 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2014-06-20 14:16:13 +10:00
<g fill="#000000" font-family="Helvetica" text-anchor="middle" font-size="12px">
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<text x="60694.25" y="43869.75">
touchpad: end tap-and-drag with an extra tap Currently for the tap-and-drag gesture to end user has to wait for a timeout to expire. Make it possible to end the drag gesture by just tapping. The allowed finger sequences to start and end a drag are thus: tap, down, .... move ...., up <wait for timeout> tap, down, .... move ...., up, tap https://bugs.freedesktop.org/show_bug.cgi?id=90255 Signed-off-by: Velimir Lisec <lisec.velimir@gmail.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> State diagram changes and a doc change squashed in. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-04-30 00:13:51 +02:00
first</text>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<text x="60694.25" y="43883.75">
touchpad: end tap-and-drag with an extra tap Currently for the tap-and-drag gesture to end user has to wait for a timeout to expire. Make it possible to end the drag gesture by just tapping. The allowed finger sequences to start and end a drag are thus: tap, down, .... move ...., up <wait for timeout> tap, down, .... move ...., up, tap https://bugs.freedesktop.org/show_bug.cgi?id=90255 Signed-off-by: Velimir Lisec <lisec.velimir@gmail.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> State diagram changes and a doc change squashed in. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-04-30 00:13:51 +02:00
finger down</text>
touchpad: disable tapping for fingers exceeding the timeout/motion threshold The current code triggers multi-finger tapping even if the finger released was previously held on the touchpad for a while. For an event sequence of: 1. first finger down 2. first finger move past threshold/wait past timeout 3. second finger down 4. first finger up The second finger initiates the two-finger tap state, but the button event is sent when the first finger releases - despite that finger not meeting the usual tap constraints. This sequence can happen whenever a user swaps fingers. Add the finger state to the actual touchpoints and update them whenever the constrains are broken. Then, discard button events if the respective touch did not meet the conditions. http://bugs.freedesktop.org/76760 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2014-06-20 14:16:13 +10:00
</g>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<path d="M 60724.24 43785 L 60706.68 43836.97" fill="none" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 60705 43841.94 L 60703.92 43834.19 L 60706.68 43836.97 L 60710.55 43836.43 Z" fill="#000000" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<rect x="60329" y="44337" width="130" height="40" rx="2.4" ry="2.4" fill="#ccffcc" stroke="#000000" stroke-width="2" pointer-events="none"/>
touchpad: disable tapping for fingers exceeding the timeout/motion threshold The current code triggers multi-finger tapping even if the finger released was previously held on the touchpad for a while. For an event sequence of: 1. first finger down 2. first finger move past threshold/wait past timeout 3. second finger down 4. first finger up The second finger initiates the two-finger tap state, but the button event is sent when the first finger releases - despite that finger not meeting the usual tap constraints. This sequence can happen whenever a user swaps fingers. Add the finger state to the actual touchpoints and update them whenever the constrains are broken. Then, discard button events if the respective touch did not meet the conditions. http://bugs.freedesktop.org/76760 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2014-06-20 14:16:13 +10:00
<g fill="#000000" font-family="Helvetica" text-anchor="middle" font-size="12px">
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<text x="60393.75" y="44360.75">
touchpad: end tap-and-drag with an extra tap Currently for the tap-and-drag gesture to end user has to wait for a timeout to expire. Make it possible to end the drag gesture by just tapping. The allowed finger sequences to start and end a drag are thus: tap, down, .... move ...., up <wait for timeout> tap, down, .... move ...., up, tap https://bugs.freedesktop.org/show_bug.cgi?id=90255 Signed-off-by: Velimir Lisec <lisec.velimir@gmail.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> State diagram changes and a doc change squashed in. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-04-30 00:13:51 +02:00
DRAGGING</text>
touchpad: disable tapping for fingers exceeding the timeout/motion threshold The current code triggers multi-finger tapping even if the finger released was previously held on the touchpad for a while. For an event sequence of: 1. first finger down 2. first finger move past threshold/wait past timeout 3. second finger down 4. first finger up The second finger initiates the two-finger tap state, but the button event is sent when the first finger releases - despite that finger not meeting the usual tap constraints. This sequence can happen whenever a user swaps fingers. Add the finger state to the actual touchpoints and update them whenever the constrains are broken. Then, discard button events if the respective touch did not meet the conditions. http://bugs.freedesktop.org/76760 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2014-06-20 14:16:13 +10:00
</g>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<path d="M 60223.04 44467 C 60225.84 44463.86 60229.82 44462.05 60234.02 44462 L 60267.99 44462 C 60272.19 44462.05 60276.17 44463.86 60278.97 44467 L 60298.95 44490 C 60299.51 44491.28 60299.51 44492.72 60298.95 44494 L 60278.97 44517 C 60276.17 44520.14 60272.19 44521.95 60267.99 44522 L 60234.02 44522 C 60229.82 44521.95 60225.84 44520.14 60223.04 44517 L 60203.06 44494 C 60202.5 44492.72 60202.5 44491.28 60203.06 44490 L 60223.04 44467 Z" fill="#ffd966" stroke="#000000" stroke-width="2" stroke-miterlimit="10" pointer-events="none"/>
touchpad: disable tapping for fingers exceeding the timeout/motion threshold The current code triggers multi-finger tapping even if the finger released was previously held on the touchpad for a while. For an event sequence of: 1. first finger down 2. first finger move past threshold/wait past timeout 3. second finger down 4. first finger up The second finger initiates the two-finger tap state, but the button event is sent when the first finger releases - despite that finger not meeting the usual tap constraints. This sequence can happen whenever a user swaps fingers. Add the finger state to the actual touchpoints and update them whenever the constrains are broken. Then, discard button events if the respective touch did not meet the conditions. http://bugs.freedesktop.org/76760 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2014-06-20 14:16:13 +10:00
<g fill="#000000" font-family="Helvetica" text-anchor="middle" font-size="12px">
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<text x="60250.75" y="44488.75">
touchpad: end tap-and-drag with an extra tap Currently for the tap-and-drag gesture to end user has to wait for a timeout to expire. Make it possible to end the drag gesture by just tapping. The allowed finger sequences to start and end a drag are thus: tap, down, .... move ...., up <wait for timeout> tap, down, .... move ...., up, tap https://bugs.freedesktop.org/show_bug.cgi?id=90255 Signed-off-by: Velimir Lisec <lisec.velimir@gmail.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> State diagram changes and a doc change squashed in. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-04-30 00:13:51 +02:00
first</text>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<text x="60250.75" y="44502.75">
touchpad: end tap-and-drag with an extra tap Currently for the tap-and-drag gesture to end user has to wait for a timeout to expire. Make it possible to end the drag gesture by just tapping. The allowed finger sequences to start and end a drag are thus: tap, down, .... move ...., up <wait for timeout> tap, down, .... move ...., up, tap https://bugs.freedesktop.org/show_bug.cgi?id=90255 Signed-off-by: Velimir Lisec <lisec.velimir@gmail.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> State diagram changes and a doc change squashed in. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-04-30 00:13:51 +02:00
finger up</text>
touchpad: disable tapping for fingers exceeding the timeout/motion threshold The current code triggers multi-finger tapping even if the finger released was previously held on the touchpad for a while. For an event sequence of: 1. first finger down 2. first finger move past threshold/wait past timeout 3. second finger down 4. first finger up The second finger initiates the two-finger tap state, but the button event is sent when the first finger releases - despite that finger not meeting the usual tap constraints. This sequence can happen whenever a user swaps fingers. Add the finger state to the actual touchpoints and update them whenever the constrains are broken. Then, discard button events if the respective touch did not meet the conditions. http://bugs.freedesktop.org/76760 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2014-06-20 14:16:13 +10:00
</g>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<path d="M 60339.22 44889.1 C 60340.36 44885.9 60342.22 44884.04 60344.18 44884.12 L 60412.64 44884.12 C 60414.2 44884.08 60415.7 44884.63 60416.67 44885.61 C 60417.65 44886.59 60417.99 44887.88 60417.6 44889.1 L 60398.75 44938.9 C 60397.61 44942.1 60395.75 44943.96 60393.79 44943.88 L 60324.34 44943.88 C 60322.95 44943.69 60321.73 44943.05 60320.97 44942.1 C 60320.22 44941.15 60320 44939.99 60320.37 44938.9 Z" fill="#ff6666" stroke="#000000" stroke-width="2" stroke-miterlimit="10" pointer-events="none"/>
touchpad: disable tapping for fingers exceeding the timeout/motion threshold The current code triggers multi-finger tapping even if the finger released was previously held on the touchpad for a while. For an event sequence of: 1. first finger down 2. first finger move past threshold/wait past timeout 3. second finger down 4. first finger up The second finger initiates the two-finger tap state, but the button event is sent when the first finger releases - despite that finger not meeting the usual tap constraints. This sequence can happen whenever a user swaps fingers. Add the finger state to the actual touchpoints and update them whenever the constrains are broken. Then, discard button events if the respective touch did not meet the conditions. http://bugs.freedesktop.org/76760 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2014-06-20 14:16:13 +10:00
<g fill="#000000" font-family="Helvetica" text-anchor="middle" font-size="12px">
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<text x="60368.75" y="44910.75">
touchpad: end tap-and-drag with an extra tap Currently for the tap-and-drag gesture to end user has to wait for a timeout to expire. Make it possible to end the drag gesture by just tapping. The allowed finger sequences to start and end a drag are thus: tap, down, .... move ...., up <wait for timeout> tap, down, .... move ...., up, tap https://bugs.freedesktop.org/show_bug.cgi?id=90255 Signed-off-by: Velimir Lisec <lisec.velimir@gmail.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> State diagram changes and a doc change squashed in. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-04-30 00:13:51 +02:00
btn1</text>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<text x="60368.75" y="44924.75">
touchpad: end tap-and-drag with an extra tap Currently for the tap-and-drag gesture to end user has to wait for a timeout to expire. Make it possible to end the drag gesture by just tapping. The allowed finger sequences to start and end a drag are thus: tap, down, .... move ...., up <wait for timeout> tap, down, .... move ...., up, tap https://bugs.freedesktop.org/show_bug.cgi?id=90255 Signed-off-by: Velimir Lisec <lisec.velimir@gmail.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> State diagram changes and a doc change squashed in. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-04-30 00:13:51 +02:00
release</text>
touchpad: disable tapping for fingers exceeding the timeout/motion threshold The current code triggers multi-finger tapping even if the finger released was previously held on the touchpad for a while. For an event sequence of: 1. first finger down 2. first finger move past threshold/wait past timeout 3. second finger down 4. first finger up The second finger initiates the two-finger tap state, but the button event is sent when the first finger releases - despite that finger not meeting the usual tap constraints. This sequence can happen whenever a user swaps fingers. Add the finger state to the actual touchpoints and update them whenever the constrains are broken. Then, discard button events if the respective touch did not meet the conditions. http://bugs.freedesktop.org/76760 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2014-06-20 14:16:13 +10:00
</g>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<path d="M 60372.81 44377 L 60287.41 44457.63" fill="none" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 60283.59 44461.23 L 60286.28 44453.88 L 60287.41 44457.63 L 60291.08 44458.97 Z" fill="#000000" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 60726.03 43620 L 60730.1 43738.64" fill="none" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 60730.28 43743.88 L 60726.54 43737.01 L 60730.1 43738.64 L 60733.53 43736.77 Z" fill="#000000" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 60910.77 43923 L 60931.58 43981.01" fill="none" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 60933.36 43985.95 L 60927.7 43980.54 L 60931.58 43981.01 L 60934.29 43978.18 Z" fill="#000000" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<ellipse cx="61841" cy="43660" rx="49.5" ry="30" fill="#ccccff" stroke="#000000" stroke-width="2" pointer-events="none"/>
touchpad: disable tapping for fingers exceeding the timeout/motion threshold The current code triggers multi-finger tapping even if the finger released was previously held on the touchpad for a while. For an event sequence of: 1. first finger down 2. first finger move past threshold/wait past timeout 3. second finger down 4. first finger up The second finger initiates the two-finger tap state, but the button event is sent when the first finger releases - despite that finger not meeting the usual tap constraints. This sequence can happen whenever a user swaps fingers. Add the finger state to the actual touchpoints and update them whenever the constrains are broken. Then, discard button events if the respective touch did not meet the conditions. http://bugs.freedesktop.org/76760 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2014-06-20 14:16:13 +10:00
<g fill="#000000" font-family="Helvetica" text-anchor="middle" font-size="12px">
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<text x="61840.25" y="43663.75">
touchpad: end tap-and-drag with an extra tap Currently for the tap-and-drag gesture to end user has to wait for a timeout to expire. Make it possible to end the drag gesture by just tapping. The allowed finger sequences to start and end a drag are thus: tap, down, .... move ...., up <wait for timeout> tap, down, .... move ...., up, tap https://bugs.freedesktop.org/show_bug.cgi?id=90255 Signed-off-by: Velimir Lisec <lisec.velimir@gmail.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> State diagram changes and a doc change squashed in. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-04-30 00:13:51 +02:00
IDLE</text>
touchpad: disable tapping for fingers exceeding the timeout/motion threshold The current code triggers multi-finger tapping even if the finger released was previously held on the touchpad for a while. For an event sequence of: 1. first finger down 2. first finger move past threshold/wait past timeout 3. second finger down 4. first finger up The second finger initiates the two-finger tap state, but the button event is sent when the first finger releases - despite that finger not meeting the usual tap constraints. This sequence can happen whenever a user swaps fingers. Add the finger state to the actual touchpoints and update them whenever the constrains are broken. Then, discard button events if the respective touch did not meet the conditions. http://bugs.freedesktop.org/76760 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2014-06-20 14:16:13 +10:00
</g>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<path d="M 61359.54 43848 C 61362.34 43844.86 61366.32 43843.05 61370.52 43843 L 61404.49 43843 C 61408.69 43843.05 61412.67 43844.86 61415.47 43848 L 61435.45 43871 C 61436.01 43872.28 61436.01 43873.72 61435.45 43875 L 61415.47 43898 C 61412.67 43901.14 61408.69 43902.95 61404.49 43903 L 61370.52 43903 C 61366.32 43902.95 61362.34 43901.14 61359.54 43898 L 61339.56 43875 C 61339 43873.72 61339 43872.28 61339.56 43871 L 61359.54 43848 Z" fill="#ffb570" stroke="#000000" stroke-width="2" stroke-miterlimit="10" pointer-events="none"/>
touchpad: disable tapping for fingers exceeding the timeout/motion threshold The current code triggers multi-finger tapping even if the finger released was previously held on the touchpad for a while. For an event sequence of: 1. first finger down 2. first finger move past threshold/wait past timeout 3. second finger down 4. first finger up The second finger initiates the two-finger tap state, but the button event is sent when the first finger releases - despite that finger not meeting the usual tap constraints. This sequence can happen whenever a user swaps fingers. Add the finger state to the actual touchpoints and update them whenever the constrains are broken. Then, discard button events if the respective touch did not meet the conditions. http://bugs.freedesktop.org/76760 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2014-06-20 14:16:13 +10:00
<g fill="#000000" font-family="Helvetica" text-anchor="middle" font-size="12px">
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<text x="61387.25" y="43869.75">
touchpad: end tap-and-drag with an extra tap Currently for the tap-and-drag gesture to end user has to wait for a timeout to expire. Make it possible to end the drag gesture by just tapping. The allowed finger sequences to start and end a drag are thus: tap, down, .... move ...., up <wait for timeout> tap, down, .... move ...., up, tap https://bugs.freedesktop.org/show_bug.cgi?id=90255 Signed-off-by: Velimir Lisec <lisec.velimir@gmail.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> State diagram changes and a doc change squashed in. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-04-30 00:13:51 +02:00
third</text>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<text x="61387.25" y="43883.75">
touchpad: end tap-and-drag with an extra tap Currently for the tap-and-drag gesture to end user has to wait for a timeout to expire. Make it possible to end the drag gesture by just tapping. The allowed finger sequences to start and end a drag are thus: tap, down, .... move ...., up <wait for timeout> tap, down, .... move ...., up, tap https://bugs.freedesktop.org/show_bug.cgi?id=90255 Signed-off-by: Velimir Lisec <lisec.velimir@gmail.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> State diagram changes and a doc change squashed in. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-04-30 00:13:51 +02:00
finger down</text>
touchpad: disable tapping for fingers exceeding the timeout/motion threshold The current code triggers multi-finger tapping even if the finger released was previously held on the touchpad for a while. For an event sequence of: 1. first finger down 2. first finger move past threshold/wait past timeout 3. second finger down 4. first finger up The second finger initiates the two-finger tap state, but the button event is sent when the first finger releases - despite that finger not meeting the usual tap constraints. This sequence can happen whenever a user swaps fingers. Add the finger state to the actual touchpoints and update them whenever the constrains are broken. Then, discard button events if the respective touch did not meet the conditions. http://bugs.freedesktop.org/76760 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2014-06-20 14:16:13 +10:00
</g>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<path d="M 61381.83 43737 L 61385.98 43836.64" fill="none" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 61386.2 43841.88 L 61382.42 43835.03 L 61385.98 43836.64 L 61389.41 43834.74 Z" fill="#000000" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<rect x="61285.5" y="44197" width="130" height="40" rx="2.4" ry="2.4" fill="#ccffcc" stroke="#000000" stroke-width="2" pointer-events="none"/>
touchpad: disable tapping for fingers exceeding the timeout/motion threshold The current code triggers multi-finger tapping even if the finger released was previously held on the touchpad for a while. For an event sequence of: 1. first finger down 2. first finger move past threshold/wait past timeout 3. second finger down 4. first finger up The second finger initiates the two-finger tap state, but the button event is sent when the first finger releases - despite that finger not meeting the usual tap constraints. This sequence can happen whenever a user swaps fingers. Add the finger state to the actual touchpoints and update them whenever the constrains are broken. Then, discard button events if the respective touch did not meet the conditions. http://bugs.freedesktop.org/76760 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2014-06-20 14:16:13 +10:00
<g fill="#000000" font-family="Helvetica" text-anchor="middle" font-size="12px">
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<text x="61350.25" y="44220.75">
touchpad: end tap-and-drag with an extra tap Currently for the tap-and-drag gesture to end user has to wait for a timeout to expire. Make it possible to end the drag gesture by just tapping. The allowed finger sequences to start and end a drag are thus: tap, down, .... move ...., up <wait for timeout> tap, down, .... move ...., up, tap https://bugs.freedesktop.org/show_bug.cgi?id=90255 Signed-off-by: Velimir Lisec <lisec.velimir@gmail.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> State diagram changes and a doc change squashed in. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-04-30 00:13:51 +02:00
TOUCH_3</text>
touchpad: disable tapping for fingers exceeding the timeout/motion threshold The current code triggers multi-finger tapping even if the finger released was previously held on the touchpad for a while. For an event sequence of: 1. first finger down 2. first finger move past threshold/wait past timeout 3. second finger down 4. first finger up The second finger initiates the two-finger tap state, but the button event is sent when the first finger releases - despite that finger not meeting the usual tap constraints. This sequence can happen whenever a user swaps fingers. Add the finger state to the actual touchpoints and update them whenever the constrains are broken. Then, discard button events if the respective touch did not meet the conditions. http://bugs.freedesktop.org/76760 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2014-06-20 14:16:13 +10:00
</g>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<path d="M 61358.33 44099.5 L 61352.26 44190.65" fill="none" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 61351.91 44195.88 L 61348.88 44188.67 L 61352.26 44190.65 L 61355.87 44189.13 Z" fill="#000000" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 61206.22 44703.1 C 61207.36 44699.9 61209.22 44698.04 61211.18 44698.12 L 61279.64 44698.12 C 61281.2 44698.08 61282.7 44698.63 61283.67 44699.61 C 61284.65 44700.59 61284.99 44701.88 61284.6 44703.1 L 61265.75 44752.9 C 61264.61 44756.1 61262.75 44757.96 61260.79 44757.88 L 61191.34 44757.88 C 61189.95 44757.69 61188.73 44757.05 61187.97 44756.1 C 61187.22 44755.15 61187 44753.99 61187.37 44752.9 Z" fill="#ff6666" stroke="#000000" stroke-width="2" stroke-miterlimit="10" pointer-events="none"/>
touchpad: disable tapping for fingers exceeding the timeout/motion threshold The current code triggers multi-finger tapping even if the finger released was previously held on the touchpad for a while. For an event sequence of: 1. first finger down 2. first finger move past threshold/wait past timeout 3. second finger down 4. first finger up The second finger initiates the two-finger tap state, but the button event is sent when the first finger releases - despite that finger not meeting the usual tap constraints. This sequence can happen whenever a user swaps fingers. Add the finger state to the actual touchpoints and update them whenever the constrains are broken. Then, discard button events if the respective touch did not meet the conditions. http://bugs.freedesktop.org/76760 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2014-06-20 14:16:13 +10:00
<g fill="#000000" font-family="Helvetica" text-anchor="middle" font-size="12px">
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<text x="61235.75" y="44724.75">
touchpad: end tap-and-drag with an extra tap Currently for the tap-and-drag gesture to end user has to wait for a timeout to expire. Make it possible to end the drag gesture by just tapping. The allowed finger sequences to start and end a drag are thus: tap, down, .... move ...., up <wait for timeout> tap, down, .... move ...., up, tap https://bugs.freedesktop.org/show_bug.cgi?id=90255 Signed-off-by: Velimir Lisec <lisec.velimir@gmail.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> State diagram changes and a doc change squashed in. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-04-30 00:13:51 +02:00
button 3</text>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<text x="61235.75" y="44738.75">
touchpad: end tap-and-drag with an extra tap Currently for the tap-and-drag gesture to end user has to wait for a timeout to expire. Make it possible to end the drag gesture by just tapping. The allowed finger sequences to start and end a drag are thus: tap, down, .... move ...., up <wait for timeout> tap, down, .... move ...., up, tap https://bugs.freedesktop.org/show_bug.cgi?id=90255 Signed-off-by: Velimir Lisec <lisec.velimir@gmail.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> State diagram changes and a doc change squashed in. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-04-30 00:13:51 +02:00
press</text>
touchpad: disable tapping for fingers exceeding the timeout/motion threshold The current code triggers multi-finger tapping even if the finger released was previously held on the touchpad for a while. For an event sequence of: 1. first finger down 2. first finger move past threshold/wait past timeout 3. second finger down 4. first finger up The second finger initiates the two-finger tap state, but the button event is sent when the first finger releases - despite that finger not meeting the usual tap constraints. This sequence can happen whenever a user swaps fingers. Add the finger state to the actual touchpoints and update them whenever the constrains are broken. Then, discard button events if the respective touch did not meet the conditions. http://bugs.freedesktop.org/76760 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2014-06-20 14:16:13 +10:00
</g>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<path d="M 61206.22 44800.1 C 61207.36 44796.9 61209.22 44795.04 61211.18 44795.12 L 61279.64 44795.12 C 61281.2 44795.08 61282.7 44795.63 61283.67 44796.61 C 61284.65 44797.59 61284.99 44798.88 61284.6 44800.1 L 61265.75 44849.9 C 61264.61 44853.1 61262.75 44854.96 61260.79 44854.88 L 61191.34 44854.88 C 61189.95 44854.69 61188.73 44854.05 61187.97 44853.1 C 61187.22 44852.15 61187 44850.99 61187.37 44849.9 Z" fill="#ff6666" stroke="#000000" stroke-width="2" stroke-miterlimit="10" pointer-events="none"/>
touchpad: disable tapping for fingers exceeding the timeout/motion threshold The current code triggers multi-finger tapping even if the finger released was previously held on the touchpad for a while. For an event sequence of: 1. first finger down 2. first finger move past threshold/wait past timeout 3. second finger down 4. first finger up The second finger initiates the two-finger tap state, but the button event is sent when the first finger releases - despite that finger not meeting the usual tap constraints. This sequence can happen whenever a user swaps fingers. Add the finger state to the actual touchpoints and update them whenever the constrains are broken. Then, discard button events if the respective touch did not meet the conditions. http://bugs.freedesktop.org/76760 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2014-06-20 14:16:13 +10:00
<g fill="#000000" font-family="Helvetica" text-anchor="middle" font-size="12px">
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<text x="61235.75" y="44821.75">
touchpad: end tap-and-drag with an extra tap Currently for the tap-and-drag gesture to end user has to wait for a timeout to expire. Make it possible to end the drag gesture by just tapping. The allowed finger sequences to start and end a drag are thus: tap, down, .... move ...., up <wait for timeout> tap, down, .... move ...., up, tap https://bugs.freedesktop.org/show_bug.cgi?id=90255 Signed-off-by: Velimir Lisec <lisec.velimir@gmail.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> State diagram changes and a doc change squashed in. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-04-30 00:13:51 +02:00
button 3</text>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<text x="61235.75" y="44835.75">
touchpad: end tap-and-drag with an extra tap Currently for the tap-and-drag gesture to end user has to wait for a timeout to expire. Make it possible to end the drag gesture by just tapping. The allowed finger sequences to start and end a drag are thus: tap, down, .... move ...., up <wait for timeout> tap, down, .... move ...., up, tap https://bugs.freedesktop.org/show_bug.cgi?id=90255 Signed-off-by: Velimir Lisec <lisec.velimir@gmail.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> State diagram changes and a doc change squashed in. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-04-30 00:13:51 +02:00
release</text>
touchpad: disable tapping for fingers exceeding the timeout/motion threshold The current code triggers multi-finger tapping even if the finger released was previously held on the touchpad for a while. For an event sequence of: 1. first finger down 2. first finger move past threshold/wait past timeout 3. second finger down 4. first finger up The second finger initiates the two-finger tap state, but the button event is sent when the first finger releases - despite that finger not meeting the usual tap constraints. This sequence can happen whenever a user swaps fingers. Add the finger state to the actual touchpoints and update them whenever the constrains are broken. Then, discard button events if the respective touch did not meet the conditions. http://bugs.freedesktop.org/76760 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2014-06-20 14:16:13 +10:00
</g>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<path d="M 61236 44758 L 61236 44788.63" fill="none" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 61236 44793.88 L 61232.5 44786.88 L 61236 44788.63 L 61239.5 44786.88 Z" fill="#000000" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 61409.04 44387 C 61411.84 44383.86 61415.82 44382.05 61420.02 44382 L 61453.99 44382 C 61458.19 44382.05 61462.17 44383.86 61464.97 44387 L 61484.95 44410 C 61485.51 44411.28 61485.51 44412.72 61484.95 44414 L 61464.97 44437 C 61462.17 44440.14 61458.19 44441.95 61453.99 44442 L 61420.02 44442 C 61415.82 44441.95 61411.84 44440.14 61409.04 44437 L 61389.06 44414 C 61388.5 44412.72 61388.5 44411.28 61389.06 44410 L 61409.04 44387 Z" fill="#67ab9f" stroke="#000000" stroke-width="2" stroke-miterlimit="10" pointer-events="none"/>
touchpad: disable tapping for fingers exceeding the timeout/motion threshold The current code triggers multi-finger tapping even if the finger released was previously held on the touchpad for a while. For an event sequence of: 1. first finger down 2. first finger move past threshold/wait past timeout 3. second finger down 4. first finger up The second finger initiates the two-finger tap state, but the button event is sent when the first finger releases - despite that finger not meeting the usual tap constraints. This sequence can happen whenever a user swaps fingers. Add the finger state to the actual touchpoints and update them whenever the constrains are broken. Then, discard button events if the respective touch did not meet the conditions. http://bugs.freedesktop.org/76760 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2014-06-20 14:16:13 +10:00
<g fill="#000000" font-family="Helvetica" text-anchor="middle" font-size="12px">
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<text x="61436.75" y="44408.75">
touchpad: end tap-and-drag with an extra tap Currently for the tap-and-drag gesture to end user has to wait for a timeout to expire. Make it possible to end the drag gesture by just tapping. The allowed finger sequences to start and end a drag are thus: tap, down, .... move ...., up <wait for timeout> tap, down, .... move ...., up, tap https://bugs.freedesktop.org/show_bug.cgi?id=90255 Signed-off-by: Velimir Lisec <lisec.velimir@gmail.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> State diagram changes and a doc change squashed in. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-04-30 00:13:51 +02:00
move &gt; </text>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<text x="61436.75" y="44422.75">
touchpad: end tap-and-drag with an extra tap Currently for the tap-and-drag gesture to end user has to wait for a timeout to expire. Make it possible to end the drag gesture by just tapping. The allowed finger sequences to start and end a drag are thus: tap, down, .... move ...., up <wait for timeout> tap, down, .... move ...., up, tap https://bugs.freedesktop.org/show_bug.cgi?id=90255 Signed-off-by: Velimir Lisec <lisec.velimir@gmail.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> State diagram changes and a doc change squashed in. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-04-30 00:13:51 +02:00
threshold</text>
touchpad: disable tapping for fingers exceeding the timeout/motion threshold The current code triggers multi-finger tapping even if the finger released was previously held on the touchpad for a while. For an event sequence of: 1. first finger down 2. first finger move past threshold/wait past timeout 3. second finger down 4. first finger up The second finger initiates the two-finger tap state, but the button event is sent when the first finger releases - despite that finger not meeting the usual tap constraints. This sequence can happen whenever a user swaps fingers. Add the finger state to the actual touchpoints and update them whenever the constrains are broken. Then, discard button events if the respective touch did not meet the conditions. http://bugs.freedesktop.org/76760 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2014-06-20 14:16:13 +10:00
</g>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<path d="M 61359.37 44237 L 61421.11 44376.18" fill="none" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 61423.24 44380.98 L 61417.2 44376 L 61421.11 44376.18 L 61423.6 44373.16 Z" fill="#000000" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<ellipse cx="60584" cy="44849" rx="49.5" ry="30" fill="#ccccff" stroke="#000000" stroke-width="2" pointer-events="none"/>
touchpad: disable tapping for fingers exceeding the timeout/motion threshold The current code triggers multi-finger tapping even if the finger released was previously held on the touchpad for a while. For an event sequence of: 1. first finger down 2. first finger move past threshold/wait past timeout 3. second finger down 4. first finger up The second finger initiates the two-finger tap state, but the button event is sent when the first finger releases - despite that finger not meeting the usual tap constraints. This sequence can happen whenever a user swaps fingers. Add the finger state to the actual touchpoints and update them whenever the constrains are broken. Then, discard button events if the respective touch did not meet the conditions. http://bugs.freedesktop.org/76760 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2014-06-20 14:16:13 +10:00
<g fill="#000000" font-family="Helvetica" text-anchor="middle" font-size="12px">
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<text x="60583.25" y="44852.75">
touchpad: end tap-and-drag with an extra tap Currently for the tap-and-drag gesture to end user has to wait for a timeout to expire. Make it possible to end the drag gesture by just tapping. The allowed finger sequences to start and end a drag are thus: tap, down, .... move ...., up <wait for timeout> tap, down, .... move ...., up, tap https://bugs.freedesktop.org/show_bug.cgi?id=90255 Signed-off-by: Velimir Lisec <lisec.velimir@gmail.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> State diagram changes and a doc change squashed in. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-04-30 00:13:51 +02:00
IDLE</text>
touchpad: disable tapping for fingers exceeding the timeout/motion threshold The current code triggers multi-finger tapping even if the finger released was previously held on the touchpad for a while. For an event sequence of: 1. first finger down 2. first finger move past threshold/wait past timeout 3. second finger down 4. first finger up The second finger initiates the two-finger tap state, but the button event is sent when the first finger releases - despite that finger not meeting the usual tap constraints. This sequence can happen whenever a user swaps fingers. Add the finger state to the actual touchpoints and update them whenever the constrains are broken. Then, discard button events if the respective touch did not meet the conditions. http://bugs.freedesktop.org/76760 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2014-06-20 14:16:13 +10:00
</g>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<path d="M 61537.54 44377 C 61540.34 44373.86 61544.32 44372.05 61548.52 44372 L 61582.49 44372 C 61586.69 44372.05 61590.67 44373.86 61593.47 44377 L 61613.45 44400 C 61614.01 44401.28 61614.01 44402.72 61613.45 44404 L 61593.47 44427 C 61590.67 44430.14 61586.69 44431.95 61582.49 44432 L 61548.52 44432 C 61544.32 44431.95 61540.34 44430.14 61537.54 44427 L 61517.56 44404 C 61517 44402.72 61517 44401.28 61517.56 44400 L 61537.54 44377 Z" fill="#99ffff" stroke="#000000" stroke-width="2" stroke-miterlimit="10" pointer-events="none"/>
touchpad: disable tapping for fingers exceeding the timeout/motion threshold The current code triggers multi-finger tapping even if the finger released was previously held on the touchpad for a while. For an event sequence of: 1. first finger down 2. first finger move past threshold/wait past timeout 3. second finger down 4. first finger up The second finger initiates the two-finger tap state, but the button event is sent when the first finger releases - despite that finger not meeting the usual tap constraints. This sequence can happen whenever a user swaps fingers. Add the finger state to the actual touchpoints and update them whenever the constrains are broken. Then, discard button events if the respective touch did not meet the conditions. http://bugs.freedesktop.org/76760 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2014-06-20 14:16:13 +10:00
<g fill="#000000" font-family="Helvetica" text-anchor="middle" font-size="12px">
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<text x="61565.25" y="44405.75">
touchpad: end tap-and-drag with an extra tap Currently for the tap-and-drag gesture to end user has to wait for a timeout to expire. Make it possible to end the drag gesture by just tapping. The allowed finger sequences to start and end a drag are thus: tap, down, .... move ...., up <wait for timeout> tap, down, .... move ...., up, tap https://bugs.freedesktop.org/show_bug.cgi?id=90255 Signed-off-by: Velimir Lisec <lisec.velimir@gmail.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> State diagram changes and a doc change squashed in. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-04-30 00:13:51 +02:00
timeout</text>
touchpad: disable tapping for fingers exceeding the timeout/motion threshold The current code triggers multi-finger tapping even if the finger released was previously held on the touchpad for a while. For an event sequence of: 1. first finger down 2. first finger move past threshold/wait past timeout 3. second finger down 4. first finger up The second finger initiates the two-finger tap state, but the button event is sent when the first finger releases - despite that finger not meeting the usual tap constraints. This sequence can happen whenever a user swaps fingers. Add the finger state to the actual touchpoints and update them whenever the constrains are broken. Then, discard button events if the respective touch did not meet the conditions. http://bugs.freedesktop.org/76760 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2014-06-20 14:16:13 +10:00
</g>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<path d="M 61373.74 44237 L 61525.81 44367.85" fill="none" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 61529.79 44371.27 L 61522.2 44369.36 L 61525.81 44367.85 L 61526.76 44364.05 Z" fill="#000000" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 60920.54 43738 C 60923.34 43734.86 60927.32 43733.05 60931.52 43733 L 60965.49 43733 C 60969.69 43733.05 60973.67 43734.86 60976.47 43738 L 60996.45 43761 C 60997.01 43762.28 60997.01 43763.72 60996.45 43765 L 60976.47 43788 C 60973.67 43791.14 60969.69 43792.95 60965.49 43793 L 60931.52 43793 C 60927.32 43792.95 60923.34 43791.14 60920.54 43788 L 60900.56 43765 C 60900 43763.72 60900 43762.28 60900.56 43761 L 60920.54 43738 Z" fill="#ffd966" stroke="#000000" stroke-width="2" stroke-miterlimit="10" pointer-events="none"/>
touchpad: disable tapping for fingers exceeding the timeout/motion threshold The current code triggers multi-finger tapping even if the finger released was previously held on the touchpad for a while. For an event sequence of: 1. first finger down 2. first finger move past threshold/wait past timeout 3. second finger down 4. first finger up The second finger initiates the two-finger tap state, but the button event is sent when the first finger releases - despite that finger not meeting the usual tap constraints. This sequence can happen whenever a user swaps fingers. Add the finger state to the actual touchpoints and update them whenever the constrains are broken. Then, discard button events if the respective touch did not meet the conditions. http://bugs.freedesktop.org/76760 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2014-06-20 14:16:13 +10:00
<g fill="#000000" font-family="Helvetica" text-anchor="middle" font-size="12px">
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<text x="60948.25" y="43759.75">
touchpad: end tap-and-drag with an extra tap Currently for the tap-and-drag gesture to end user has to wait for a timeout to expire. Make it possible to end the drag gesture by just tapping. The allowed finger sequences to start and end a drag are thus: tap, down, .... move ...., up <wait for timeout> tap, down, .... move ...., up, tap https://bugs.freedesktop.org/show_bug.cgi?id=90255 Signed-off-by: Velimir Lisec <lisec.velimir@gmail.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> State diagram changes and a doc change squashed in. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-04-30 00:13:51 +02:00
first</text>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<text x="60948.25" y="43773.75">
touchpad: end tap-and-drag with an extra tap Currently for the tap-and-drag gesture to end user has to wait for a timeout to expire. Make it possible to end the drag gesture by just tapping. The allowed finger sequences to start and end a drag are thus: tap, down, .... move ...., up <wait for timeout> tap, down, .... move ...., up, tap https://bugs.freedesktop.org/show_bug.cgi?id=90255 Signed-off-by: Velimir Lisec <lisec.velimir@gmail.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> State diagram changes and a doc change squashed in. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-04-30 00:13:51 +02:00
finger up</text>
touchpad: disable tapping for fingers exceeding the timeout/motion threshold The current code triggers multi-finger tapping even if the finger released was previously held on the touchpad for a while. For an event sequence of: 1. first finger down 2. first finger move past threshold/wait past timeout 3. second finger down 4. first finger up The second finger initiates the two-finger tap state, but the button event is sent when the first finger releases - despite that finger not meeting the usual tap constraints. This sequence can happen whenever a user swaps fingers. Add the finger state to the actual touchpoints and update them whenever the constrains are broken. Then, discard button events if the respective touch did not meet the conditions. http://bugs.freedesktop.org/76760 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2014-06-20 14:16:13 +10:00
</g>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<path d="M 61316 43723.91 L 61003.33 43757.17" fill="none" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 60998.11 43757.72 L 61004.7 43753.5 L 61003.33 43757.17 L 61005.44 43760.46 Z" fill="#000000" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<ellipse cx="60944" cy="44142" rx="49.5" ry="30" fill="#ccccff" stroke="#000000" stroke-width="2" pointer-events="none"/>
touchpad: disable tapping for fingers exceeding the timeout/motion threshold The current code triggers multi-finger tapping even if the finger released was previously held on the touchpad for a while. For an event sequence of: 1. first finger down 2. first finger move past threshold/wait past timeout 3. second finger down 4. first finger up The second finger initiates the two-finger tap state, but the button event is sent when the first finger releases - despite that finger not meeting the usual tap constraints. This sequence can happen whenever a user swaps fingers. Add the finger state to the actual touchpoints and update them whenever the constrains are broken. Then, discard button events if the respective touch did not meet the conditions. http://bugs.freedesktop.org/76760 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2014-06-20 14:16:13 +10:00
<g fill="#000000" font-family="Helvetica" text-anchor="middle" font-size="12px">
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<text x="60943.75" y="44145.75">
touchpad: end tap-and-drag with an extra tap Currently for the tap-and-drag gesture to end user has to wait for a timeout to expire. Make it possible to end the drag gesture by just tapping. The allowed finger sequences to start and end a drag are thus: tap, down, .... move ...., up <wait for timeout> tap, down, .... move ...., up, tap https://bugs.freedesktop.org/show_bug.cgi?id=90255 Signed-off-by: Velimir Lisec <lisec.velimir@gmail.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> State diagram changes and a doc change squashed in. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-04-30 00:13:51 +02:00
IDLE</text>
touchpad: disable tapping for fingers exceeding the timeout/motion threshold The current code triggers multi-finger tapping even if the finger released was previously held on the touchpad for a while. For an event sequence of: 1. first finger down 2. first finger move past threshold/wait past timeout 3. second finger down 4. first finger up The second finger initiates the two-finger tap state, but the button event is sent when the first finger releases - despite that finger not meeting the usual tap constraints. This sequence can happen whenever a user swaps fingers. Add the finger state to the actual touchpoints and update them whenever the constrains are broken. Then, discard button events if the respective touch did not meet the conditions. http://bugs.freedesktop.org/76760 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2014-06-20 14:16:13 +10:00
</g>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<path d="M 61122.04 44382 C 61124.84 44378.86 61128.82 44377.05 61133.02 44377 L 61166.99 44377 C 61171.19 44377.05 61175.17 44378.86 61177.97 44382 L 61197.95 44405 C 61198.51 44406.28 61198.51 44407.72 61197.95 44409 L 61177.97 44432 C 61175.17 44435.14 61171.19 44436.95 61166.99 44437 L 61133.02 44437 C 61128.82 44436.95 61124.84 44435.14 61122.04 44432 L 61102.06 44409 C 61101.5 44407.72 61101.5 44406.28 61102.06 44405 L 61122.04 44382 Z" fill="#ffffff" stroke="#000000" stroke-width="2" stroke-miterlimit="10" pointer-events="none"/>
touchpad: disable tapping for fingers exceeding the timeout/motion threshold The current code triggers multi-finger tapping even if the finger released was previously held on the touchpad for a while. For an event sequence of: 1. first finger down 2. first finger move past threshold/wait past timeout 3. second finger down 4. first finger up The second finger initiates the two-finger tap state, but the button event is sent when the first finger releases - despite that finger not meeting the usual tap constraints. This sequence can happen whenever a user swaps fingers. Add the finger state to the actual touchpoints and update them whenever the constrains are broken. Then, discard button events if the respective touch did not meet the conditions. http://bugs.freedesktop.org/76760 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2014-06-20 14:16:13 +10:00
<g fill="#000000" font-family="Helvetica" text-anchor="middle" font-size="12px">
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<text x="61149.75" y="44403.75">
touchpad: end tap-and-drag with an extra tap Currently for the tap-and-drag gesture to end user has to wait for a timeout to expire. Make it possible to end the drag gesture by just tapping. The allowed finger sequences to start and end a drag are thus: tap, down, .... move ...., up <wait for timeout> tap, down, .... move ...., up, tap https://bugs.freedesktop.org/show_bug.cgi?id=90255 Signed-off-by: Velimir Lisec <lisec.velimir@gmail.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> State diagram changes and a doc change squashed in. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-04-30 00:13:51 +02:00
fourth</text>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<text x="61149.75" y="44417.75">
touchpad: end tap-and-drag with an extra tap Currently for the tap-and-drag gesture to end user has to wait for a timeout to expire. Make it possible to end the drag gesture by just tapping. The allowed finger sequences to start and end a drag are thus: tap, down, .... move ...., up <wait for timeout> tap, down, .... move ...., up, tap https://bugs.freedesktop.org/show_bug.cgi?id=90255 Signed-off-by: Velimir Lisec <lisec.velimir@gmail.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> State diagram changes and a doc change squashed in. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-04-30 00:13:51 +02:00
finger down</text>
touchpad: introduce MULTITAP for multi-tap-and-drag Once we have a doubletap, enter a loop in the state machine where we can tap multiple times and either get a multi-click or a multi-click drag-and-drop. The sequence down/up down/up down/up produces a triple-click. The sequence down/up down/up down/up down produces a triple-click with a button down for dragging. Yes, that glorious octuple-tap-and-drag, it is now possible. World domination has been achieved, thank you for playing. We don't know when we finish tapping now, so add a timeout to send the last click event once the finger has been released for the last time. This guarantees that the timestamp of the last button down is later than the last release. This avoids the bug fixed in synaptics commit xf86-input-synaptics-1.8.0-21-g37d34f0 (some application don't handle doubletap correctly without the timestamps). This works for double-tap immediately, for multi-tap we need to remember the timestamp of the first press event and use it for the release event so that there's a forced gap between the release and the second press. https://bugs.freedesktop.org/show_bug.cgi?id=89511 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-04-16 10:19:11 +10:00
</g>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<path d="M 61329.39 44237 L 61186.28 44372.62" fill="none" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 61182.47 44376.23 L 61185.14 44368.88 L 61186.28 44372.62 L 61189.96 44373.96 Z" fill="#000000" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 60944.38 44047 L 60944.15 44105.63" fill="none" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 60944.12 44110.88 L 60940.65 44103.87 L 60944.15 44105.63 L 60947.65 44103.9 Z" fill="#000000" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<rect x="60569.5" y="44017" width="209" height="40" rx="2.4" ry="2.4" fill="#ccffcc" stroke="#000000" stroke-width="2" pointer-events="none"/>
touchpad: disable tapping for fingers exceeding the timeout/motion threshold The current code triggers multi-finger tapping even if the finger released was previously held on the touchpad for a while. For an event sequence of: 1. first finger down 2. first finger move past threshold/wait past timeout 3. second finger down 4. first finger up The second finger initiates the two-finger tap state, but the button event is sent when the first finger releases - despite that finger not meeting the usual tap constraints. This sequence can happen whenever a user swaps fingers. Add the finger state to the actual touchpoints and update them whenever the constrains are broken. Then, discard button events if the respective touch did not meet the conditions. http://bugs.freedesktop.org/76760 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2014-06-20 14:16:13 +10:00
<g fill="#000000" font-family="Helvetica" text-anchor="middle" font-size="12px">
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<text x="60673.75" y="44040.75">
touchpad: end tap-and-drag with an extra tap Currently for the tap-and-drag gesture to end user has to wait for a timeout to expire. Make it possible to end the drag gesture by just tapping. The allowed finger sequences to start and end a drag are thus: tap, down, .... move ...., up <wait for timeout> tap, down, .... move ...., up, tap https://bugs.freedesktop.org/show_bug.cgi?id=90255 Signed-off-by: Velimir Lisec <lisec.velimir@gmail.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> State diagram changes and a doc change squashed in. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-04-30 00:13:51 +02:00
DRAGGING_OR_DOUBLETAP</text>
touchpad: introduce MULTITAP for multi-tap-and-drag Once we have a doubletap, enter a loop in the state machine where we can tap multiple times and either get a multi-click or a multi-click drag-and-drop. The sequence down/up down/up down/up produces a triple-click. The sequence down/up down/up down/up down produces a triple-click with a button down for dragging. Yes, that glorious octuple-tap-and-drag, it is now possible. World domination has been achieved, thank you for playing. We don't know when we finish tapping now, so add a timeout to send the last click event once the finger has been released for the last time. This guarantees that the timestamp of the last button down is later than the last release. This avoids the bug fixed in synaptics commit xf86-input-synaptics-1.8.0-21-g37d34f0 (some application don't handle doubletap correctly without the timestamps). This works for double-tap immediately, for multi-tap we need to remember the timestamp of the first press event and use it for the release event so that there's a forced gap between the release and the second press. https://bugs.freedesktop.org/show_bug.cgi?id=89511 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-04-16 10:19:11 +10:00
</g>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<path d="M 60751.5 43994.45 L 60716.01 44013.94" fill="none" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 60711.41 44016.46 L 60715.86 44010.03 L 60716.01 44013.94 L 60719.23 44016.16 Z" fill="#000000" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 60446.54 44102 C 60449.34 44098.86 60453.32 44097.05 60457.52 44097 L 60491.49 44097 C 60495.69 44097.05 60499.67 44098.86 60502.47 44102 L 60522.45 44125 C 60523.01 44126.28 60523.01 44127.72 60522.45 44129 L 60502.47 44152 C 60499.67 44155.14 60495.69 44156.95 60491.49 44157 L 60457.52 44157 C 60453.32 44156.95 60449.34 44155.14 60446.54 44152 L 60426.56 44129 C 60426 44127.72 60426 44126.28 60426.56 44125 L 60446.54 44102 Z" fill="#99ffff" stroke="#000000" stroke-width="2" stroke-miterlimit="10" pointer-events="none"/>
touchpad: introduce MULTITAP for multi-tap-and-drag Once we have a doubletap, enter a loop in the state machine where we can tap multiple times and either get a multi-click or a multi-click drag-and-drop. The sequence down/up down/up down/up produces a triple-click. The sequence down/up down/up down/up down produces a triple-click with a button down for dragging. Yes, that glorious octuple-tap-and-drag, it is now possible. World domination has been achieved, thank you for playing. We don't know when we finish tapping now, so add a timeout to send the last click event once the finger has been released for the last time. This guarantees that the timestamp of the last button down is later than the last release. This avoids the bug fixed in synaptics commit xf86-input-synaptics-1.8.0-21-g37d34f0 (some application don't handle doubletap correctly without the timestamps). This works for double-tap immediately, for multi-tap we need to remember the timestamp of the first press event and use it for the release event so that there's a forced gap between the release and the second press. https://bugs.freedesktop.org/show_bug.cgi?id=89511 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-04-16 10:19:11 +10:00
<g fill="#000000" font-family="Helvetica" text-anchor="middle" font-size="12px">
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<text x="60474.25" y="44130.75">
touchpad: end tap-and-drag with an extra tap Currently for the tap-and-drag gesture to end user has to wait for a timeout to expire. Make it possible to end the drag gesture by just tapping. The allowed finger sequences to start and end a drag are thus: tap, down, .... move ...., up <wait for timeout> tap, down, .... move ...., up, tap https://bugs.freedesktop.org/show_bug.cgi?id=90255 Signed-off-by: Velimir Lisec <lisec.velimir@gmail.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> State diagram changes and a doc change squashed in. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-04-30 00:13:51 +02:00
timeout</text>
touchpad: introduce MULTITAP for multi-tap-and-drag Once we have a doubletap, enter a loop in the state machine where we can tap multiple times and either get a multi-click or a multi-click drag-and-drop. The sequence down/up down/up down/up produces a triple-click. The sequence down/up down/up down/up down produces a triple-click with a button down for dragging. Yes, that glorious octuple-tap-and-drag, it is now possible. World domination has been achieved, thank you for playing. We don't know when we finish tapping now, so add a timeout to send the last click event once the finger has been released for the last time. This guarantees that the timestamp of the last button down is later than the last release. This avoids the bug fixed in synaptics commit xf86-input-synaptics-1.8.0-21-g37d34f0 (some application don't handle doubletap correctly without the timestamps). This works for double-tap immediately, for multi-tap we need to remember the timestamp of the first press event and use it for the release event so that there's a forced gap between the release and the second press. https://bugs.freedesktop.org/show_bug.cgi?id=89511 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-04-16 10:19:11 +10:00
</g>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<path d="M 60629.67 44057 L 60528.8 44102.5" fill="none" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 60524.02 44104.66 L 60528.96 44098.59 L 60528.8 44102.5 L 60531.84 44104.97 Z" fill="#000000" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 60283.04 43868 C 60285.84 43864.86 60289.82 43863.05 60294.02 43863 L 60327.99 43863 C 60332.19 43863.05 60336.17 43864.86 60338.97 43868 L 60358.95 43891 C 60359.51 43892.28 60359.51 43893.72 60358.95 43895 L 60338.97 43918 C 60336.17 43921.14 60332.19 43922.95 60327.99 43923 L 60294.02 43923 C 60289.82 43922.95 60285.84 43921.14 60283.04 43918 L 60263.06 43895 C 60262.5 43893.72 60262.5 43892.28 60263.06 43891 L 60283.04 43868 Z" fill="#ffd966" stroke="#000000" stroke-width="2" stroke-miterlimit="10" pointer-events="none"/>
touchpad: disable tapping for fingers exceeding the timeout/motion threshold The current code triggers multi-finger tapping even if the finger released was previously held on the touchpad for a while. For an event sequence of: 1. first finger down 2. first finger move past threshold/wait past timeout 3. second finger down 4. first finger up The second finger initiates the two-finger tap state, but the button event is sent when the first finger releases - despite that finger not meeting the usual tap constraints. This sequence can happen whenever a user swaps fingers. Add the finger state to the actual touchpoints and update them whenever the constrains are broken. Then, discard button events if the respective touch did not meet the conditions. http://bugs.freedesktop.org/76760 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2014-06-20 14:16:13 +10:00
<g fill="#000000" font-family="Helvetica" text-anchor="middle" font-size="12px">
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<text x="60310.75" y="43889.75">
touchpad: end tap-and-drag with an extra tap Currently for the tap-and-drag gesture to end user has to wait for a timeout to expire. Make it possible to end the drag gesture by just tapping. The allowed finger sequences to start and end a drag are thus: tap, down, .... move ...., up <wait for timeout> tap, down, .... move ...., up, tap https://bugs.freedesktop.org/show_bug.cgi?id=90255 Signed-off-by: Velimir Lisec <lisec.velimir@gmail.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> State diagram changes and a doc change squashed in. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-04-30 00:13:51 +02:00
first</text>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<text x="60310.75" y="43903.75">
touchpad: end tap-and-drag with an extra tap Currently for the tap-and-drag gesture to end user has to wait for a timeout to expire. Make it possible to end the drag gesture by just tapping. The allowed finger sequences to start and end a drag are thus: tap, down, .... move ...., up <wait for timeout> tap, down, .... move ...., up, tap https://bugs.freedesktop.org/show_bug.cgi?id=90255 Signed-off-by: Velimir Lisec <lisec.velimir@gmail.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> State diagram changes and a doc change squashed in. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-04-30 00:13:51 +02:00
finger up</text>
touchpad: introduce MULTITAP for multi-tap-and-drag Once we have a doubletap, enter a loop in the state machine where we can tap multiple times and either get a multi-click or a multi-click drag-and-drop. The sequence down/up down/up down/up produces a triple-click. The sequence down/up down/up down/up down produces a triple-click with a button down for dragging. Yes, that glorious octuple-tap-and-drag, it is now possible. World domination has been achieved, thank you for playing. We don't know when we finish tapping now, so add a timeout to send the last click event once the finger has been released for the last time. This guarantees that the timestamp of the last button down is later than the last release. This avoids the bug fixed in synaptics commit xf86-input-synaptics-1.8.0-21-g37d34f0 (some application don't handle doubletap correctly without the timestamps). This works for double-tap immediately, for multi-tap we need to remember the timestamp of the first press event and use it for the release event so that there's a forced gap between the release and the second press. https://bugs.freedesktop.org/show_bug.cgi?id=89511 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-04-16 10:19:11 +10:00
</g>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<path d="M 60623.58 44017 L 60365.42 43914.59" fill="none" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 60360.54 43912.65 L 60368.34 43911.98 L 60365.42 43914.59 L 60365.76 43918.49 Z" fill="#000000" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 59970.22 43818.1 C 59971.36 43814.9 59973.22 43813.04 59975.18 43813.12 L 60043.64 43813.12 C 60045.2 43813.08 60046.7 43813.63 60047.67 43814.61 C 60048.65 43815.59 60048.99 43816.88 60048.6 43818.1 L 60029.75 43867.9 C 60028.61 43871.1 60026.75 43872.96 60024.79 43872.88 L 59955.34 43872.88 C 59953.95 43872.69 59952.73 43872.05 59951.97 43871.1 C 59951.22 43870.15 59951 43868.99 59951.37 43867.9 Z" fill="#ff6666" stroke="#000000" stroke-width="2" stroke-miterlimit="10" pointer-events="none"/>
touchpad: introduce MULTITAP for multi-tap-and-drag Once we have a doubletap, enter a loop in the state machine where we can tap multiple times and either get a multi-click or a multi-click drag-and-drop. The sequence down/up down/up down/up produces a triple-click. The sequence down/up down/up down/up down produces a triple-click with a button down for dragging. Yes, that glorious octuple-tap-and-drag, it is now possible. World domination has been achieved, thank you for playing. We don't know when we finish tapping now, so add a timeout to send the last click event once the finger has been released for the last time. This guarantees that the timestamp of the last button down is later than the last release. This avoids the bug fixed in synaptics commit xf86-input-synaptics-1.8.0-21-g37d34f0 (some application don't handle doubletap correctly without the timestamps). This works for double-tap immediately, for multi-tap we need to remember the timestamp of the first press event and use it for the release event so that there's a forced gap between the release and the second press. https://bugs.freedesktop.org/show_bug.cgi?id=89511 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-04-16 10:19:11 +10:00
<g fill="#000000" font-family="Helvetica" text-anchor="middle" font-size="12px">
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<text x="59999.75" y="43839.75">
touchpad: end tap-and-drag with an extra tap Currently for the tap-and-drag gesture to end user has to wait for a timeout to expire. Make it possible to end the drag gesture by just tapping. The allowed finger sequences to start and end a drag are thus: tap, down, .... move ...., up <wait for timeout> tap, down, .... move ...., up, tap https://bugs.freedesktop.org/show_bug.cgi?id=90255 Signed-off-by: Velimir Lisec <lisec.velimir@gmail.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> State diagram changes and a doc change squashed in. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-04-30 00:13:51 +02:00
button 1</text>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<text x="59999.75" y="43853.75">
touchpad: end tap-and-drag with an extra tap Currently for the tap-and-drag gesture to end user has to wait for a timeout to expire. Make it possible to end the drag gesture by just tapping. The allowed finger sequences to start and end a drag are thus: tap, down, .... move ...., up <wait for timeout> tap, down, .... move ...., up, tap https://bugs.freedesktop.org/show_bug.cgi?id=90255 Signed-off-by: Velimir Lisec <lisec.velimir@gmail.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> State diagram changes and a doc change squashed in. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-04-30 00:13:51 +02:00
release</text>
touchpad: introduce MULTITAP for multi-tap-and-drag Once we have a doubletap, enter a loop in the state machine where we can tap multiple times and either get a multi-click or a multi-click drag-and-drop. The sequence down/up down/up down/up produces a triple-click. The sequence down/up down/up down/up down produces a triple-click with a button down for dragging. Yes, that glorious octuple-tap-and-drag, it is now possible. World domination has been achieved, thank you for playing. We don't know when we finish tapping now, so add a timeout to send the last click event once the finger has been released for the last time. This guarantees that the timestamp of the last button down is later than the last release. This avoids the bug fixed in synaptics commit xf86-input-synaptics-1.8.0-21-g37d34f0 (some application don't handle doubletap correctly without the timestamps). This works for double-tap immediately, for multi-tap we need to remember the timestamp of the first press event and use it for the release event so that there's a forced gap between the release and the second press. https://bugs.freedesktop.org/show_bug.cgi?id=89511 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-04-16 10:19:11 +10:00
</g>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<path d="M 59721.22 44157.1 C 59722.36 44153.9 59724.22 44152.04 59726.18 44152.12 L 59794.64 44152.12 C 59796.2 44152.08 59797.7 44152.63 59798.67 44153.61 C 59799.65 44154.59 59799.99 44155.88 59799.6 44157.1 L 59780.75 44206.9 C 59779.61 44210.1 59777.75 44211.96 59775.79 44211.88 L 59706.34 44211.88 C 59704.95 44211.69 59703.73 44211.05 59702.97 44210.1 C 59702.22 44209.15 59702 44207.99 59702.37 44206.9 Z" fill="#ff6666" stroke="#000000" stroke-width="2" stroke-miterlimit="10" pointer-events="none"/>
touchpad: introduce MULTITAP for multi-tap-and-drag Once we have a doubletap, enter a loop in the state machine where we can tap multiple times and either get a multi-click or a multi-click drag-and-drop. The sequence down/up down/up down/up produces a triple-click. The sequence down/up down/up down/up down produces a triple-click with a button down for dragging. Yes, that glorious octuple-tap-and-drag, it is now possible. World domination has been achieved, thank you for playing. We don't know when we finish tapping now, so add a timeout to send the last click event once the finger has been released for the last time. This guarantees that the timestamp of the last button down is later than the last release. This avoids the bug fixed in synaptics commit xf86-input-synaptics-1.8.0-21-g37d34f0 (some application don't handle doubletap correctly without the timestamps). This works for double-tap immediately, for multi-tap we need to remember the timestamp of the first press event and use it for the release event so that there's a forced gap between the release and the second press. https://bugs.freedesktop.org/show_bug.cgi?id=89511 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-04-16 10:19:11 +10:00
<g fill="#000000" font-family="Helvetica" text-anchor="middle" font-size="12px">
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<text x="59750.75" y="44178.75">
touchpad: end tap-and-drag with an extra tap Currently for the tap-and-drag gesture to end user has to wait for a timeout to expire. Make it possible to end the drag gesture by just tapping. The allowed finger sequences to start and end a drag are thus: tap, down, .... move ...., up <wait for timeout> tap, down, .... move ...., up, tap https://bugs.freedesktop.org/show_bug.cgi?id=90255 Signed-off-by: Velimir Lisec <lisec.velimir@gmail.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> State diagram changes and a doc change squashed in. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-04-30 00:13:51 +02:00
button 1</text>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<text x="59750.75" y="44192.75">
touchpad: end tap-and-drag with an extra tap Currently for the tap-and-drag gesture to end user has to wait for a timeout to expire. Make it possible to end the drag gesture by just tapping. The allowed finger sequences to start and end a drag are thus: tap, down, .... move ...., up <wait for timeout> tap, down, .... move ...., up, tap https://bugs.freedesktop.org/show_bug.cgi?id=90255 Signed-off-by: Velimir Lisec <lisec.velimir@gmail.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> State diagram changes and a doc change squashed in. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-04-30 00:13:51 +02:00
press</text>
touchpad: introduce MULTITAP for multi-tap-and-drag Once we have a doubletap, enter a loop in the state machine where we can tap multiple times and either get a multi-click or a multi-click drag-and-drop. The sequence down/up down/up down/up produces a triple-click. The sequence down/up down/up down/up down produces a triple-click with a button down for dragging. Yes, that glorious octuple-tap-and-drag, it is now possible. World domination has been achieved, thank you for playing. We don't know when we finish tapping now, so add a timeout to send the last click event once the finger has been released for the last time. This guarantees that the timestamp of the last button down is later than the last release. This avoids the bug fixed in synaptics commit xf86-input-synaptics-1.8.0-21-g37d34f0 (some application don't handle doubletap correctly without the timestamps). This works for double-tap immediately, for multi-tap we need to remember the timestamp of the first press event and use it for the release event so that there's a forced gap between the release and the second press. https://bugs.freedesktop.org/show_bug.cgi?id=89511 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-04-16 10:19:11 +10:00
</g>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<path d="M 59721.72 44297.1 C 59722.86 44293.9 59724.72 44292.04 59726.68 44292.12 L 59795.14 44292.12 C 59796.7 44292.08 59798.2 44292.63 59799.17 44293.61 C 59800.15 44294.59 59800.49 44295.88 59800.1 44297.1 L 59781.25 44346.9 C 59780.11 44350.1 59778.25 44351.96 59776.29 44351.88 L 59706.84 44351.88 C 59705.45 44351.69 59704.23 44351.05 59703.47 44350.1 C 59702.72 44349.15 59702.5 44347.99 59702.87 44346.9 Z" fill="#ff6666" stroke="#000000" stroke-width="2" stroke-miterlimit="10" pointer-events="none"/>
touchpad: introduce MULTITAP for multi-tap-and-drag Once we have a doubletap, enter a loop in the state machine where we can tap multiple times and either get a multi-click or a multi-click drag-and-drop. The sequence down/up down/up down/up produces a triple-click. The sequence down/up down/up down/up down produces a triple-click with a button down for dragging. Yes, that glorious octuple-tap-and-drag, it is now possible. World domination has been achieved, thank you for playing. We don't know when we finish tapping now, so add a timeout to send the last click event once the finger has been released for the last time. This guarantees that the timestamp of the last button down is later than the last release. This avoids the bug fixed in synaptics commit xf86-input-synaptics-1.8.0-21-g37d34f0 (some application don't handle doubletap correctly without the timestamps). This works for double-tap immediately, for multi-tap we need to remember the timestamp of the first press event and use it for the release event so that there's a forced gap between the release and the second press. https://bugs.freedesktop.org/show_bug.cgi?id=89511 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-04-16 10:19:11 +10:00
<g fill="#000000" font-family="Helvetica" text-anchor="middle" font-size="12px">
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<text x="59751.25" y="44318.75">
touchpad: end tap-and-drag with an extra tap Currently for the tap-and-drag gesture to end user has to wait for a timeout to expire. Make it possible to end the drag gesture by just tapping. The allowed finger sequences to start and end a drag are thus: tap, down, .... move ...., up <wait for timeout> tap, down, .... move ...., up, tap https://bugs.freedesktop.org/show_bug.cgi?id=90255 Signed-off-by: Velimir Lisec <lisec.velimir@gmail.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> State diagram changes and a doc change squashed in. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-04-30 00:13:51 +02:00
btn1</text>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<text x="59751.25" y="44332.75">
touchpad: end tap-and-drag with an extra tap Currently for the tap-and-drag gesture to end user has to wait for a timeout to expire. Make it possible to end the drag gesture by just tapping. The allowed finger sequences to start and end a drag are thus: tap, down, .... move ...., up <wait for timeout> tap, down, .... move ...., up, tap https://bugs.freedesktop.org/show_bug.cgi?id=90255 Signed-off-by: Velimir Lisec <lisec.velimir@gmail.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> State diagram changes and a doc change squashed in. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-04-30 00:13:51 +02:00
release</text>
touchpad: introduce MULTITAP for multi-tap-and-drag Once we have a doubletap, enter a loop in the state machine where we can tap multiple times and either get a multi-click or a multi-click drag-and-drop. The sequence down/up down/up down/up produces a triple-click. The sequence down/up down/up down/up down produces a triple-click with a button down for dragging. Yes, that glorious octuple-tap-and-drag, it is now possible. World domination has been achieved, thank you for playing. We don't know when we finish tapping now, so add a timeout to send the last click event once the finger has been released for the last time. This guarantees that the timestamp of the last button down is later than the last release. This avoids the bug fixed in synaptics commit xf86-input-synaptics-1.8.0-21-g37d34f0 (some application don't handle doubletap correctly without the timestamps). This works for double-tap immediately, for multi-tap we need to remember the timestamp of the first press event and use it for the release event so that there's a forced gap between the release and the second press. https://bugs.freedesktop.org/show_bug.cgi?id=89511 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-04-16 10:19:11 +10:00
</g>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<path d="M 59751.11 44212 L 59751.37 44285.63" fill="none" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 59751.39 44290.88 L 59747.86 44283.89 L 59751.37 44285.63 L 59754.86 44283.87 Z" fill="#000000" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 60601.54 44102 C 60604.34 44098.86 60608.32 44097.05 60612.52 44097 L 60646.49 44097 C 60650.69 44097.05 60654.67 44098.86 60657.47 44102 L 60677.45 44125 C 60678.01 44126.28 60678.01 44127.72 60677.45 44129 L 60657.47 44152 C 60654.67 44155.14 60650.69 44156.95 60646.49 44157 L 60612.52 44157 C 60608.32 44156.95 60604.34 44155.14 60601.54 44152 L 60581.56 44129 C 60581 44127.72 60581 44126.28 60581.56 44125 L 60601.54 44102 Z" fill="#7ea6e0" stroke="#000000" stroke-width="2" stroke-miterlimit="10" pointer-events="none"/>
touchpad: introduce MULTITAP for multi-tap-and-drag Once we have a doubletap, enter a loop in the state machine where we can tap multiple times and either get a multi-click or a multi-click drag-and-drop. The sequence down/up down/up down/up produces a triple-click. The sequence down/up down/up down/up down produces a triple-click with a button down for dragging. Yes, that glorious octuple-tap-and-drag, it is now possible. World domination has been achieved, thank you for playing. We don't know when we finish tapping now, so add a timeout to send the last click event once the finger has been released for the last time. This guarantees that the timestamp of the last button down is later than the last release. This avoids the bug fixed in synaptics commit xf86-input-synaptics-1.8.0-21-g37d34f0 (some application don't handle doubletap correctly without the timestamps). This works for double-tap immediately, for multi-tap we need to remember the timestamp of the first press event and use it for the release event so that there's a forced gap between the release and the second press. https://bugs.freedesktop.org/show_bug.cgi?id=89511 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-04-16 10:19:11 +10:00
<g fill="#000000" font-family="Helvetica" text-anchor="middle" font-size="12px">
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<text x="60629.25" y="44123.75">
touchpad: end tap-and-drag with an extra tap Currently for the tap-and-drag gesture to end user has to wait for a timeout to expire. Make it possible to end the drag gesture by just tapping. The allowed finger sequences to start and end a drag are thus: tap, down, .... move ...., up <wait for timeout> tap, down, .... move ...., up, tap https://bugs.freedesktop.org/show_bug.cgi?id=90255 Signed-off-by: Velimir Lisec <lisec.velimir@gmail.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> State diagram changes and a doc change squashed in. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-04-30 00:13:51 +02:00
second</text>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<text x="60629.25" y="44137.75">
touchpad: end tap-and-drag with an extra tap Currently for the tap-and-drag gesture to end user has to wait for a timeout to expire. Make it possible to end the drag gesture by just tapping. The allowed finger sequences to start and end a drag are thus: tap, down, .... move ...., up <wait for timeout> tap, down, .... move ...., up, tap https://bugs.freedesktop.org/show_bug.cgi?id=90255 Signed-off-by: Velimir Lisec <lisec.velimir@gmail.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> State diagram changes and a doc change squashed in. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-04-30 00:13:51 +02:00
finger down</text>
touchpad: introduce MULTITAP for multi-tap-and-drag Once we have a doubletap, enter a loop in the state machine where we can tap multiple times and either get a multi-click or a multi-click drag-and-drop. The sequence down/up down/up down/up produces a triple-click. The sequence down/up down/up down/up down produces a triple-click with a button down for dragging. Yes, that glorious octuple-tap-and-drag, it is now possible. World domination has been achieved, thank you for playing. We don't know when we finish tapping now, so add a timeout to send the last click event once the finger has been released for the last time. This guarantees that the timestamp of the last button down is later than the last release. This avoids the bug fixed in synaptics commit xf86-input-synaptics-1.8.0-21-g37d34f0 (some application don't handle doubletap correctly without the timestamps). This works for double-tap immediately, for multi-tap we need to remember the timestamp of the first press event and use it for the release event so that there's a forced gap between the release and the second press. https://bugs.freedesktop.org/show_bug.cgi?id=89511 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-04-16 10:19:11 +10:00
</g>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<path d="M 60664.11 44057 L 60647.16 44091.29" fill="none" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 60644.83 44096 L 60644.79 44088.17 L 60647.16 44091.29 L 60651.07 44091.27 Z" fill="#000000" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 60241.54 44107 C 60244.34 44103.86 60248.32 44102.05 60252.52 44102 L 60286.49 44102 C 60290.69 44102.05 60294.67 44103.86 60297.47 44107 L 60317.45 44130 C 60318.01 44131.28 60318.01 44132.72 60317.45 44134 L 60297.47 44157 C 60294.67 44160.14 60290.69 44161.95 60286.49 44162 L 60252.52 44162 C 60248.32 44161.95 60244.34 44160.14 60241.54 44157 L 60221.56 44134 C 60221 44132.72 60221 44131.28 60221.56 44130 L 60241.54 44107 Z" fill="#67ab9f" stroke="#000000" stroke-width="2" stroke-miterlimit="10" pointer-events="none"/>
touchpad: introduce MULTITAP for multi-tap-and-drag Once we have a doubletap, enter a loop in the state machine where we can tap multiple times and either get a multi-click or a multi-click drag-and-drop. The sequence down/up down/up down/up produces a triple-click. The sequence down/up down/up down/up down produces a triple-click with a button down for dragging. Yes, that glorious octuple-tap-and-drag, it is now possible. World domination has been achieved, thank you for playing. We don't know when we finish tapping now, so add a timeout to send the last click event once the finger has been released for the last time. This guarantees that the timestamp of the last button down is later than the last release. This avoids the bug fixed in synaptics commit xf86-input-synaptics-1.8.0-21-g37d34f0 (some application don't handle doubletap correctly without the timestamps). This works for double-tap immediately, for multi-tap we need to remember the timestamp of the first press event and use it for the release event so that there's a forced gap between the release and the second press. https://bugs.freedesktop.org/show_bug.cgi?id=89511 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-04-16 10:19:11 +10:00
<g fill="#000000" font-family="Helvetica" text-anchor="middle" font-size="12px">
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<text x="60269.25" y="44128.75">
touchpad: end tap-and-drag with an extra tap Currently for the tap-and-drag gesture to end user has to wait for a timeout to expire. Make it possible to end the drag gesture by just tapping. The allowed finger sequences to start and end a drag are thus: tap, down, .... move ...., up <wait for timeout> tap, down, .... move ...., up, tap https://bugs.freedesktop.org/show_bug.cgi?id=90255 Signed-off-by: Velimir Lisec <lisec.velimir@gmail.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> State diagram changes and a doc change squashed in. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-04-30 00:13:51 +02:00
move &gt; </text>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<text x="60269.25" y="44142.75">
touchpad: end tap-and-drag with an extra tap Currently for the tap-and-drag gesture to end user has to wait for a timeout to expire. Make it possible to end the drag gesture by just tapping. The allowed finger sequences to start and end a drag are thus: tap, down, .... move ...., up <wait for timeout> tap, down, .... move ...., up, tap https://bugs.freedesktop.org/show_bug.cgi?id=90255 Signed-off-by: Velimir Lisec <lisec.velimir@gmail.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> State diagram changes and a doc change squashed in. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-04-30 00:13:51 +02:00
threshold</text>
touchpad: introduce MULTITAP for multi-tap-and-drag Once we have a doubletap, enter a loop in the state machine where we can tap multiple times and either get a multi-click or a multi-click drag-and-drop. The sequence down/up down/up down/up produces a triple-click. The sequence down/up down/up down/up down produces a triple-click with a button down for dragging. Yes, that glorious octuple-tap-and-drag, it is now possible. World domination has been achieved, thank you for playing. We don't know when we finish tapping now, so add a timeout to send the last click event once the finger has been released for the last time. This guarantees that the timestamp of the last button down is later than the last release. This avoids the bug fixed in synaptics commit xf86-input-synaptics-1.8.0-21-g37d34f0 (some application don't handle doubletap correctly without the timestamps). This works for double-tap immediately, for multi-tap we need to remember the timestamp of the first press event and use it for the release event so that there's a forced gap between the release and the second press. https://bugs.freedesktop.org/show_bug.cgi?id=89511 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-04-16 10:19:11 +10:00
</g>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<path d="M 60588.84 44057 L 60324.2 44119.15" fill="none" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 60319.09 44120.35 L 60325.1 44115.35 L 60324.2 44119.15 L 60326.7 44122.16 Z" fill="#000000" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 60405.53 44262.5 L 60397.21 44330.68" fill="none" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 60396.58 44335.89 L 60393.95 44328.52 L 60397.21 44330.68 L 60400.9 44329.37 Z" fill="#000000" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<rect x="61371" y="43427" width="130" height="40" rx="2.4" ry="2.4" fill="#ccffcc" stroke="#000000" stroke-width="2" pointer-events="none"/>
touchpad: introduce MULTITAP for multi-tap-and-drag Once we have a doubletap, enter a loop in the state machine where we can tap multiple times and either get a multi-click or a multi-click drag-and-drop. The sequence down/up down/up down/up produces a triple-click. The sequence down/up down/up down/up down produces a triple-click with a button down for dragging. Yes, that glorious octuple-tap-and-drag, it is now possible. World domination has been achieved, thank you for playing. We don't know when we finish tapping now, so add a timeout to send the last click event once the finger has been released for the last time. This guarantees that the timestamp of the last button down is later than the last release. This avoids the bug fixed in synaptics commit xf86-input-synaptics-1.8.0-21-g37d34f0 (some application don't handle doubletap correctly without the timestamps). This works for double-tap immediately, for multi-tap we need to remember the timestamp of the first press event and use it for the release event so that there's a forced gap between the release and the second press. https://bugs.freedesktop.org/show_bug.cgi?id=89511 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-04-16 10:19:11 +10:00
<g fill="#000000" font-family="Helvetica" text-anchor="middle" font-size="12px">
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<text x="61435.75" y="43450.75">
touchpad: end tap-and-drag with an extra tap Currently for the tap-and-drag gesture to end user has to wait for a timeout to expire. Make it possible to end the drag gesture by just tapping. The allowed finger sequences to start and end a drag are thus: tap, down, .... move ...., up <wait for timeout> tap, down, .... move ...., up, tap https://bugs.freedesktop.org/show_bug.cgi?id=90255 Signed-off-by: Velimir Lisec <lisec.velimir@gmail.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> State diagram changes and a doc change squashed in. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-04-30 00:13:51 +02:00
HOLD</text>
touchpad: introduce MULTITAP for multi-tap-and-drag Once we have a doubletap, enter a loop in the state machine where we can tap multiple times and either get a multi-click or a multi-click drag-and-drop. The sequence down/up down/up down/up produces a triple-click. The sequence down/up down/up down/up down produces a triple-click with a button down for dragging. Yes, that glorious octuple-tap-and-drag, it is now possible. World domination has been achieved, thank you for playing. We don't know when we finish tapping now, so add a timeout to send the last click event once the finger has been released for the last time. This guarantees that the timestamp of the last button down is later than the last release. This avoids the bug fixed in synaptics commit xf86-input-synaptics-1.8.0-21-g37d34f0 (some application don't handle doubletap correctly without the timestamps). This works for double-tap immediately, for multi-tap we need to remember the timestamp of the first press event and use it for the release event so that there's a forced gap between the release and the second press. https://bugs.freedesktop.org/show_bug.cgi?id=89511 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-04-16 10:19:11 +10:00
</g>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<path d="M 61594.04 43555 C 61596.84 43551.86 61600.82 43550.05 61605.02 43550 L 61638.99 43550 C 61643.19 43550.05 61647.17 43551.86 61649.97 43555 L 61669.95 43578 C 61670.51 43579.28 61670.51 43580.72 61669.95 43582 L 61649.97 43605 C 61647.17 43608.14 61643.19 43609.95 61638.99 43610 L 61605.02 43610 C 61600.82 43609.95 61596.84 43608.14 61594.04 43605 L 61574.06 43582 C 61573.5 43580.72 61573.5 43579.28 61574.06 43578 L 61594.04 43555 Z" fill="#ffd966" stroke="#000000" stroke-width="2" stroke-miterlimit="10" pointer-events="none"/>
touchpad: introduce MULTITAP for multi-tap-and-drag Once we have a doubletap, enter a loop in the state machine where we can tap multiple times and either get a multi-click or a multi-click drag-and-drop. The sequence down/up down/up down/up produces a triple-click. The sequence down/up down/up down/up down produces a triple-click with a button down for dragging. Yes, that glorious octuple-tap-and-drag, it is now possible. World domination has been achieved, thank you for playing. We don't know when we finish tapping now, so add a timeout to send the last click event once the finger has been released for the last time. This guarantees that the timestamp of the last button down is later than the last release. This avoids the bug fixed in synaptics commit xf86-input-synaptics-1.8.0-21-g37d34f0 (some application don't handle doubletap correctly without the timestamps). This works for double-tap immediately, for multi-tap we need to remember the timestamp of the first press event and use it for the release event so that there's a forced gap between the release and the second press. https://bugs.freedesktop.org/show_bug.cgi?id=89511 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-04-16 10:19:11 +10:00
<g fill="#000000" font-family="Helvetica" text-anchor="middle" font-size="12px">
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<text x="61621.75" y="43576.75">
touchpad: end tap-and-drag with an extra tap Currently for the tap-and-drag gesture to end user has to wait for a timeout to expire. Make it possible to end the drag gesture by just tapping. The allowed finger sequences to start and end a drag are thus: tap, down, .... move ...., up <wait for timeout> tap, down, .... move ...., up, tap https://bugs.freedesktop.org/show_bug.cgi?id=90255 Signed-off-by: Velimir Lisec <lisec.velimir@gmail.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> State diagram changes and a doc change squashed in. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-04-30 00:13:51 +02:00
first</text>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<text x="61621.75" y="43590.75">
touchpad: end tap-and-drag with an extra tap Currently for the tap-and-drag gesture to end user has to wait for a timeout to expire. Make it possible to end the drag gesture by just tapping. The allowed finger sequences to start and end a drag are thus: tap, down, .... move ...., up <wait for timeout> tap, down, .... move ...., up, tap https://bugs.freedesktop.org/show_bug.cgi?id=90255 Signed-off-by: Velimir Lisec <lisec.velimir@gmail.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> State diagram changes and a doc change squashed in. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-04-30 00:13:51 +02:00
finger up</text>
touchpad: introduce MULTITAP for multi-tap-and-drag Once we have a doubletap, enter a loop in the state machine where we can tap multiple times and either get a multi-click or a multi-click drag-and-drop. The sequence down/up down/up down/up produces a triple-click. The sequence down/up down/up down/up down produces a triple-click with a button down for dragging. Yes, that glorious octuple-tap-and-drag, it is now possible. World domination has been achieved, thank you for playing. We don't know when we finish tapping now, so add a timeout to send the last click event once the finger has been released for the last time. This guarantees that the timestamp of the last button down is later than the last release. This avoids the bug fixed in synaptics commit xf86-input-synaptics-1.8.0-21-g37d34f0 (some application don't handle doubletap correctly without the timestamps). This works for double-tap immediately, for multi-tap we need to remember the timestamp of the first press event and use it for the release event so that there's a forced gap between the release and the second press. https://bugs.freedesktop.org/show_bug.cgi?id=89511 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-04-16 10:19:11 +10:00
</g>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<path d="M 61463.97 43467 L 61574.87 43546.3" fill="none" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 61579.14 43549.35 L 61571.41 43548.13 L 61574.87 43546.3 L 61575.48 43542.43 Z" fill="#000000" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 61762.5 43656.95 L 61784.64 43657.82" fill="none" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 61789.88 43658.02 L 61782.75 43661.25 L 61784.64 43657.82 L 61783.02 43654.25 Z" fill="#000000" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 61378.54 43522 C 61381.34 43518.86 61385.32 43517.05 61389.52 43517 L 61423.49 43517 C 61427.69 43517.05 61431.67 43518.86 61434.47 43522 L 61454.45 43545 C 61455.01 43546.28 61455.01 43547.72 61454.45 43549 L 61434.47 43572 C 61431.67 43575.14 61427.69 43576.95 61423.49 43577 L 61389.52 43577 C 61385.32 43576.95 61381.34 43575.14 61378.54 43572 L 61358.56 43549 C 61358 43547.72 61358 43546.28 61358.56 43545 L 61378.54 43522 Z" fill="#7ea6e0" stroke="#000000" stroke-width="2" stroke-miterlimit="10" pointer-events="none"/>
touchpad: introduce MULTITAP for multi-tap-and-drag Once we have a doubletap, enter a loop in the state machine where we can tap multiple times and either get a multi-click or a multi-click drag-and-drop. The sequence down/up down/up down/up produces a triple-click. The sequence down/up down/up down/up down produces a triple-click with a button down for dragging. Yes, that glorious octuple-tap-and-drag, it is now possible. World domination has been achieved, thank you for playing. We don't know when we finish tapping now, so add a timeout to send the last click event once the finger has been released for the last time. This guarantees that the timestamp of the last button down is later than the last release. This avoids the bug fixed in synaptics commit xf86-input-synaptics-1.8.0-21-g37d34f0 (some application don't handle doubletap correctly without the timestamps). This works for double-tap immediately, for multi-tap we need to remember the timestamp of the first press event and use it for the release event so that there's a forced gap between the release and the second press. https://bugs.freedesktop.org/show_bug.cgi?id=89511 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-04-16 10:19:11 +10:00
<g fill="#000000" font-family="Helvetica" text-anchor="middle" font-size="12px">
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<text x="61406.25" y="43543.75">
touchpad: end tap-and-drag with an extra tap Currently for the tap-and-drag gesture to end user has to wait for a timeout to expire. Make it possible to end the drag gesture by just tapping. The allowed finger sequences to start and end a drag are thus: tap, down, .... move ...., up <wait for timeout> tap, down, .... move ...., up, tap https://bugs.freedesktop.org/show_bug.cgi?id=90255 Signed-off-by: Velimir Lisec <lisec.velimir@gmail.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> State diagram changes and a doc change squashed in. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-04-30 00:13:51 +02:00
second</text>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<text x="61406.25" y="43557.75">
touchpad: end tap-and-drag with an extra tap Currently for the tap-and-drag gesture to end user has to wait for a timeout to expire. Make it possible to end the drag gesture by just tapping. The allowed finger sequences to start and end a drag are thus: tap, down, .... move ...., up <wait for timeout> tap, down, .... move ...., up, tap https://bugs.freedesktop.org/show_bug.cgi?id=90255 Signed-off-by: Velimir Lisec <lisec.velimir@gmail.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> State diagram changes and a doc change squashed in. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-04-30 00:13:51 +02:00
finger down</text>
touchpad: introduce MULTITAP for multi-tap-and-drag Once we have a doubletap, enter a loop in the state machine where we can tap multiple times and either get a multi-click or a multi-click drag-and-drop. The sequence down/up down/up down/up produces a triple-click. The sequence down/up down/up down/up down produces a triple-click with a button down for dragging. Yes, that glorious octuple-tap-and-drag, it is now possible. World domination has been achieved, thank you for playing. We don't know when we finish tapping now, so add a timeout to send the last click event once the finger has been released for the last time. This guarantees that the timestamp of the last button down is later than the last release. This avoids the bug fixed in synaptics commit xf86-input-synaptics-1.8.0-21-g37d34f0 (some application don't handle doubletap correctly without the timestamps). This works for double-tap immediately, for multi-tap we need to remember the timestamp of the first press event and use it for the release event so that there's a forced gap between the release and the second press. https://bugs.freedesktop.org/show_bug.cgi?id=89511 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-04-16 10:19:11 +10:00
</g>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<path d="M 61430.1 43467 L 61417.15 43510.89" fill="none" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 61415.67 43515.93 L 61414.29 43508.22 L 61417.15 43510.89 L 61421 43510.2 Z" fill="#000000" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 61385.53 43667.5 L 61383.41 43690.66" fill="none" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 61382.93 43695.89 L 61380.08 43688.6 L 61383.41 43690.66 L 61387.05 43689.23 Z" fill="#000000" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<rect x="61712.25" y="43967" width="130" height="40" rx="2.4" ry="2.4" fill="#ccffcc" stroke="#000000" stroke-width="2" pointer-events="none"/>
touchpad: introduce MULTITAP for multi-tap-and-drag Once we have a doubletap, enter a loop in the state machine where we can tap multiple times and either get a multi-click or a multi-click drag-and-drop. The sequence down/up down/up down/up produces a triple-click. The sequence down/up down/up down/up down produces a triple-click with a button down for dragging. Yes, that glorious octuple-tap-and-drag, it is now possible. World domination has been achieved, thank you for playing. We don't know when we finish tapping now, so add a timeout to send the last click event once the finger has been released for the last time. This guarantees that the timestamp of the last button down is later than the last release. This avoids the bug fixed in synaptics commit xf86-input-synaptics-1.8.0-21-g37d34f0 (some application don't handle doubletap correctly without the timestamps). This works for double-tap immediately, for multi-tap we need to remember the timestamp of the first press event and use it for the release event so that there's a forced gap between the release and the second press. https://bugs.freedesktop.org/show_bug.cgi?id=89511 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-04-16 10:19:11 +10:00
<g fill="#000000" font-family="Helvetica" text-anchor="middle" font-size="12px">
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<text x="61777" y="43990.75">
touchpad: end tap-and-drag with an extra tap Currently for the tap-and-drag gesture to end user has to wait for a timeout to expire. Make it possible to end the drag gesture by just tapping. The allowed finger sequences to start and end a drag are thus: tap, down, .... move ...., up <wait for timeout> tap, down, .... move ...., up, tap https://bugs.freedesktop.org/show_bug.cgi?id=90255 Signed-off-by: Velimir Lisec <lisec.velimir@gmail.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> State diagram changes and a doc change squashed in. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-04-30 00:13:51 +02:00
TOUCH_2_HOLD</text>
touchpad: introduce MULTITAP for multi-tap-and-drag Once we have a doubletap, enter a loop in the state machine where we can tap multiple times and either get a multi-click or a multi-click drag-and-drop. The sequence down/up down/up down/up produces a triple-click. The sequence down/up down/up down/up down produces a triple-click with a button down for dragging. Yes, that glorious octuple-tap-and-drag, it is now possible. World domination has been achieved, thank you for playing. We don't know when we finish tapping now, so add a timeout to send the last click event once the finger has been released for the last time. This guarantees that the timestamp of the last button down is later than the last release. This avoids the bug fixed in synaptics commit xf86-input-synaptics-1.8.0-21-g37d34f0 (some application don't handle doubletap correctly without the timestamps). This works for double-tap immediately, for multi-tap we need to remember the timestamp of the first press event and use it for the release event so that there's a forced gap between the release and the second press. https://bugs.freedesktop.org/show_bug.cgi?id=89511 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-04-16 10:19:11 +10:00
</g>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<path d="M 61891.79 44072 C 61894.59 44068.86 61898.57 44067.05 61902.77 44067 L 61936.74 44067 C 61940.94 44067.05 61944.92 44068.86 61947.72 44072 L 61967.7 44095 C 61968.26 44096.28 61968.26 44097.72 61967.7 44099 L 61947.72 44122 C 61944.92 44125.14 61940.94 44126.95 61936.74 44127 L 61902.77 44127 C 61898.57 44126.95 61894.59 44125.14 61891.79 44122 L 61871.81 44099 C 61871.25 44097.72 61871.25 44096.28 61871.81 44095 L 61891.79 44072 Z" fill="#7ea6e0" stroke="#000000" stroke-width="2" stroke-miterlimit="10" pointer-events="none"/>
touchpad: introduce MULTITAP for multi-tap-and-drag Once we have a doubletap, enter a loop in the state machine where we can tap multiple times and either get a multi-click or a multi-click drag-and-drop. The sequence down/up down/up down/up produces a triple-click. The sequence down/up down/up down/up down produces a triple-click with a button down for dragging. Yes, that glorious octuple-tap-and-drag, it is now possible. World domination has been achieved, thank you for playing. We don't know when we finish tapping now, so add a timeout to send the last click event once the finger has been released for the last time. This guarantees that the timestamp of the last button down is later than the last release. This avoids the bug fixed in synaptics commit xf86-input-synaptics-1.8.0-21-g37d34f0 (some application don't handle doubletap correctly without the timestamps). This works for double-tap immediately, for multi-tap we need to remember the timestamp of the first press event and use it for the release event so that there's a forced gap between the release and the second press. https://bugs.freedesktop.org/show_bug.cgi?id=89511 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-04-16 10:19:11 +10:00
<g fill="#000000" font-family="Helvetica" text-anchor="middle" font-size="12px">
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<text x="61919.5" y="44093.75">
touchpad: end tap-and-drag with an extra tap Currently for the tap-and-drag gesture to end user has to wait for a timeout to expire. Make it possible to end the drag gesture by just tapping. The allowed finger sequences to start and end a drag are thus: tap, down, .... move ...., up <wait for timeout> tap, down, .... move ...., up, tap https://bugs.freedesktop.org/show_bug.cgi?id=90255 Signed-off-by: Velimir Lisec <lisec.velimir@gmail.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> State diagram changes and a doc change squashed in. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-04-30 00:13:51 +02:00
second</text>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<text x="61919.5" y="44107.75">
touchpad: end tap-and-drag with an extra tap Currently for the tap-and-drag gesture to end user has to wait for a timeout to expire. Make it possible to end the drag gesture by just tapping. The allowed finger sequences to start and end a drag are thus: tap, down, .... move ...., up <wait for timeout> tap, down, .... move ...., up, tap https://bugs.freedesktop.org/show_bug.cgi?id=90255 Signed-off-by: Velimir Lisec <lisec.velimir@gmail.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> State diagram changes and a doc change squashed in. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-04-30 00:13:51 +02:00
finger up</text>
touchpad: introduce MULTITAP for multi-tap-and-drag Once we have a doubletap, enter a loop in the state machine where we can tap multiple times and either get a multi-click or a multi-click drag-and-drop. The sequence down/up down/up down/up produces a triple-click. The sequence down/up down/up down/up down produces a triple-click with a button down for dragging. Yes, that glorious octuple-tap-and-drag, it is now possible. World domination has been achieved, thank you for playing. We don't know when we finish tapping now, so add a timeout to send the last click event once the finger has been released for the last time. This guarantees that the timestamp of the last button down is later than the last release. This avoids the bug fixed in synaptics commit xf86-input-synaptics-1.8.0-21-g37d34f0 (some application don't handle doubletap correctly without the timestamps). This works for double-tap immediately, for multi-tap we need to remember the timestamp of the first press event and use it for the release event so that there's a forced gap between the release and the second press. https://bugs.freedesktop.org/show_bug.cgi?id=89511 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-04-16 10:19:11 +10:00
</g>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<path d="M 61803.16 44007 L 61875.85 44063.11" fill="none" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 61880 44066.32 L 61872.32 44064.81 L 61875.85 44063.11 L 61876.6 44059.27 Z" fill="#000000" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 61587.29 44077 C 61590.09 44073.86 61594.07 44072.05 61598.27 44072 L 61632.24 44072 C 61636.44 44072.05 61640.42 44073.86 61643.22 44077 L 61663.2 44100 C 61663.76 44101.28 61663.76 44102.72 61663.2 44104 L 61643.22 44127 C 61640.42 44130.14 61636.44 44131.95 61632.24 44132 L 61598.27 44132 C 61594.07 44131.95 61590.09 44130.14 61587.29 44127 L 61567.31 44104 C 61566.75 44102.72 61566.75 44101.28 61567.31 44100 L 61587.29 44077 Z" fill="#ffd966" stroke="#000000" stroke-width="2" stroke-miterlimit="10" pointer-events="none"/>
touchpad: introduce MULTITAP for multi-tap-and-drag Once we have a doubletap, enter a loop in the state machine where we can tap multiple times and either get a multi-click or a multi-click drag-and-drop. The sequence down/up down/up down/up produces a triple-click. The sequence down/up down/up down/up down produces a triple-click with a button down for dragging. Yes, that glorious octuple-tap-and-drag, it is now possible. World domination has been achieved, thank you for playing. We don't know when we finish tapping now, so add a timeout to send the last click event once the finger has been released for the last time. This guarantees that the timestamp of the last button down is later than the last release. This avoids the bug fixed in synaptics commit xf86-input-synaptics-1.8.0-21-g37d34f0 (some application don't handle doubletap correctly without the timestamps). This works for double-tap immediately, for multi-tap we need to remember the timestamp of the first press event and use it for the release event so that there's a forced gap between the release and the second press. https://bugs.freedesktop.org/show_bug.cgi?id=89511 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-04-16 10:19:11 +10:00
<g fill="#000000" font-family="Helvetica" text-anchor="middle" font-size="12px">
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<text x="61615" y="44098.75">
touchpad: end tap-and-drag with an extra tap Currently for the tap-and-drag gesture to end user has to wait for a timeout to expire. Make it possible to end the drag gesture by just tapping. The allowed finger sequences to start and end a drag are thus: tap, down, .... move ...., up <wait for timeout> tap, down, .... move ...., up, tap https://bugs.freedesktop.org/show_bug.cgi?id=90255 Signed-off-by: Velimir Lisec <lisec.velimir@gmail.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> State diagram changes and a doc change squashed in. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-04-30 00:13:51 +02:00
first</text>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<text x="61615" y="44112.75">
touchpad: end tap-and-drag with an extra tap Currently for the tap-and-drag gesture to end user has to wait for a timeout to expire. Make it possible to end the drag gesture by just tapping. The allowed finger sequences to start and end a drag are thus: tap, down, .... move ...., up <wait for timeout> tap, down, .... move ...., up, tap https://bugs.freedesktop.org/show_bug.cgi?id=90255 Signed-off-by: Velimir Lisec <lisec.velimir@gmail.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> State diagram changes and a doc change squashed in. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-04-30 00:13:51 +02:00
finger up</text>
touchpad: introduce MULTITAP for multi-tap-and-drag Once we have a doubletap, enter a loop in the state machine where we can tap multiple times and either get a multi-click or a multi-click drag-and-drop. The sequence down/up down/up down/up produces a triple-click. The sequence down/up down/up down/up down produces a triple-click with a button down for dragging. Yes, that glorious octuple-tap-and-drag, it is now possible. World domination has been achieved, thank you for playing. We don't know when we finish tapping now, so add a timeout to send the last click event once the finger has been released for the last time. This guarantees that the timestamp of the last button down is later than the last release. This avoids the bug fixed in synaptics commit xf86-input-synaptics-1.8.0-21-g37d34f0 (some application don't handle doubletap correctly without the timestamps). This works for double-tap immediately, for multi-tap we need to remember the timestamp of the first press event and use it for the release event so that there's a forced gap between the release and the second press. https://bugs.freedesktop.org/show_bug.cgi?id=89511 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-04-16 10:19:11 +10:00
</g>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<path d="M 61749.08 44007 L 61662.7 44068.31" fill="none" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 61658.42 44071.35 L 61662.1 44064.45 L 61662.7 44068.31 L 61666.16 44070.15 Z" fill="#000000" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 61901 43722.5 L 61901 43457 Q 61901 43447 61891 43447 L 61507.37 43447" fill="none" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 61502.12 43447 L 61509.12 43443.5 L 61507.37 43447 L 61509.12 43450.5 Z" fill="#000000" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 61561 43883.5 L 61561 43457 Q 61561 43447 61551 43447 L 61507.37 43447" fill="none" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 61502.12 43447 L 61509.12 43443.5 L 61507.37 43447 L 61509.12 43450.5 Z" fill="#000000" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 61732.79 44082 C 61735.59 44078.86 61739.57 44077.05 61743.77 44077 L 61777.74 44077 C 61781.94 44077.05 61785.92 44078.86 61788.72 44082 L 61808.7 44105 C 61809.26 44106.28 61809.26 44107.72 61808.7 44109 L 61788.72 44132 C 61785.92 44135.14 61781.94 44136.95 61777.74 44137 L 61743.77 44137 C 61739.57 44136.95 61735.59 44135.14 61732.79 44132 L 61712.81 44109 C 61712.25 44107.72 61712.25 44106.28 61712.81 44105 L 61732.79 44082 Z" fill="#ffb570" stroke="#000000" stroke-width="2" stroke-miterlimit="10" pointer-events="none"/>
touchpad: introduce MULTITAP for multi-tap-and-drag Once we have a doubletap, enter a loop in the state machine where we can tap multiple times and either get a multi-click or a multi-click drag-and-drop. The sequence down/up down/up down/up produces a triple-click. The sequence down/up down/up down/up down produces a triple-click with a button down for dragging. Yes, that glorious octuple-tap-and-drag, it is now possible. World domination has been achieved, thank you for playing. We don't know when we finish tapping now, so add a timeout to send the last click event once the finger has been released for the last time. This guarantees that the timestamp of the last button down is later than the last release. This avoids the bug fixed in synaptics commit xf86-input-synaptics-1.8.0-21-g37d34f0 (some application don't handle doubletap correctly without the timestamps). This works for double-tap immediately, for multi-tap we need to remember the timestamp of the first press event and use it for the release event so that there's a forced gap between the release and the second press. https://bugs.freedesktop.org/show_bug.cgi?id=89511 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-04-16 10:19:11 +10:00
<g fill="#000000" font-family="Helvetica" text-anchor="middle" font-size="12px">
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<text x="61760.5" y="44103.75">
touchpad: end tap-and-drag with an extra tap Currently for the tap-and-drag gesture to end user has to wait for a timeout to expire. Make it possible to end the drag gesture by just tapping. The allowed finger sequences to start and end a drag are thus: tap, down, .... move ...., up <wait for timeout> tap, down, .... move ...., up, tap https://bugs.freedesktop.org/show_bug.cgi?id=90255 Signed-off-by: Velimir Lisec <lisec.velimir@gmail.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> State diagram changes and a doc change squashed in. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-04-30 00:13:51 +02:00
third</text>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<text x="61760.5" y="44117.75">
touchpad: end tap-and-drag with an extra tap Currently for the tap-and-drag gesture to end user has to wait for a timeout to expire. Make it possible to end the drag gesture by just tapping. The allowed finger sequences to start and end a drag are thus: tap, down, .... move ...., up <wait for timeout> tap, down, .... move ...., up, tap https://bugs.freedesktop.org/show_bug.cgi?id=90255 Signed-off-by: Velimir Lisec <lisec.velimir@gmail.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> State diagram changes and a doc change squashed in. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-04-30 00:13:51 +02:00
finger down</text>
touchpad: introduce MULTITAP for multi-tap-and-drag Once we have a doubletap, enter a loop in the state machine where we can tap multiple times and either get a multi-click or a multi-click drag-and-drop. The sequence down/up down/up down/up produces a triple-click. The sequence down/up down/up down/up down produces a triple-click with a button down for dragging. Yes, that glorious octuple-tap-and-drag, it is now possible. World domination has been achieved, thank you for playing. We don't know when we finish tapping now, so add a timeout to send the last click event once the finger has been released for the last time. This guarantees that the timestamp of the last button down is later than the last release. This avoids the bug fixed in synaptics commit xf86-input-synaptics-1.8.0-21-g37d34f0 (some application don't handle doubletap correctly without the timestamps). This works for double-tap immediately, for multi-tap we need to remember the timestamp of the first press event and use it for the release event so that there's a forced gap between the release and the second press. https://bugs.freedesktop.org/show_bug.cgi?id=89511 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-04-16 10:19:11 +10:00
</g>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<path d="M 61774.5 44007 L 61765.74 44070.69" fill="none" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 61765.03 44075.89 L 61762.51 44068.48 L 61765.74 44070.69 L 61769.45 44069.43 Z" fill="#000000" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 61485.5 44202.41 L 61421.83 44209.29" fill="none" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 61416.61 44209.85 L 61423.19 44205.62 L 61421.83 44209.29 L 61423.95 44212.58 Z" fill="#000000" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 61486.5 44834 L 61981 44834 Q 61991 44834 61991 44824 L 61991 43997 Q 61991 43987 61981 43987 L 61848.62 43987" fill="none" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 61843.37 43987 L 61850.37 43983.5 L 61848.62 43987 L 61850.37 43990.5 Z" fill="#000000" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<rect x="61451" y="45074" width="130" height="40" rx="2.4" ry="2.4" fill="#ccffcc" stroke="#000000" stroke-width="2" pointer-events="none"/>
touchpad: introduce MULTITAP for multi-tap-and-drag Once we have a doubletap, enter a loop in the state machine where we can tap multiple times and either get a multi-click or a multi-click drag-and-drop. The sequence down/up down/up down/up produces a triple-click. The sequence down/up down/up down/up down produces a triple-click with a button down for dragging. Yes, that glorious octuple-tap-and-drag, it is now possible. World domination has been achieved, thank you for playing. We don't know when we finish tapping now, so add a timeout to send the last click event once the finger has been released for the last time. This guarantees that the timestamp of the last button down is later than the last release. This avoids the bug fixed in synaptics commit xf86-input-synaptics-1.8.0-21-g37d34f0 (some application don't handle doubletap correctly without the timestamps). This works for double-tap immediately, for multi-tap we need to remember the timestamp of the first press event and use it for the release event so that there's a forced gap between the release and the second press. https://bugs.freedesktop.org/show_bug.cgi?id=89511 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-04-16 10:19:11 +10:00
<g fill="#000000" font-family="Helvetica" text-anchor="middle" font-size="12px">
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<text x="61515.75" y="45097.75">
touchpad: end tap-and-drag with an extra tap Currently for the tap-and-drag gesture to end user has to wait for a timeout to expire. Make it possible to end the drag gesture by just tapping. The allowed finger sequences to start and end a drag are thus: tap, down, .... move ...., up <wait for timeout> tap, down, .... move ...., up, tap https://bugs.freedesktop.org/show_bug.cgi?id=90255 Signed-off-by: Velimir Lisec <lisec.velimir@gmail.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> State diagram changes and a doc change squashed in. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-04-30 00:13:51 +02:00
TOUCH_3_HOLD</text>
touchpad: introduce MULTITAP for multi-tap-and-drag Once we have a doubletap, enter a loop in the state machine where we can tap multiple times and either get a multi-click or a multi-click drag-and-drop. The sequence down/up down/up down/up produces a triple-click. The sequence down/up down/up down/up down produces a triple-click with a button down for dragging. Yes, that glorious octuple-tap-and-drag, it is now possible. World domination has been achieved, thank you for playing. We don't know when we finish tapping now, so add a timeout to send the last click event once the finger has been released for the last time. This guarantees that the timestamp of the last button down is later than the last release. This avoids the bug fixed in synaptics commit xf86-input-synaptics-1.8.0-21-g37d34f0 (some application don't handle doubletap correctly without the timestamps). This works for double-tap immediately, for multi-tap we need to remember the timestamp of the first press event and use it for the release event so that there's a forced gap between the release and the second press. https://bugs.freedesktop.org/show_bug.cgi?id=89511 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-04-16 10:19:11 +10:00
</g>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<path d="M 61508.11 44673.5 L 61515.51 45067.63" fill="none" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 61515.6 45072.88 L 61511.97 45065.95 L 61515.51 45067.63 L 61518.97 45065.82 Z" fill="#000000" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 61212.04 45212 C 61214.84 45208.86 61218.82 45207.05 61223.02 45207 L 61256.99 45207 C 61261.19 45207.05 61265.17 45208.86 61267.97 45212 L 61287.95 45235 C 61288.51 45236.28 61288.51 45237.72 61287.95 45239 L 61267.97 45262 C 61265.17 45265.14 61261.19 45266.95 61256.99 45267 L 61223.02 45267 C 61218.82 45266.95 61214.84 45265.14 61212.04 45262 L 61192.06 45239 C 61191.5 45237.72 61191.5 45236.28 61192.06 45235 L 61212.04 45212 Z" fill="#ffffff" stroke="#000000" stroke-width="2" stroke-miterlimit="10" pointer-events="none"/>
touchpad: introduce MULTITAP for multi-tap-and-drag Once we have a doubletap, enter a loop in the state machine where we can tap multiple times and either get a multi-click or a multi-click drag-and-drop. The sequence down/up down/up down/up produces a triple-click. The sequence down/up down/up down/up down produces a triple-click with a button down for dragging. Yes, that glorious octuple-tap-and-drag, it is now possible. World domination has been achieved, thank you for playing. We don't know when we finish tapping now, so add a timeout to send the last click event once the finger has been released for the last time. This guarantees that the timestamp of the last button down is later than the last release. This avoids the bug fixed in synaptics commit xf86-input-synaptics-1.8.0-21-g37d34f0 (some application don't handle doubletap correctly without the timestamps). This works for double-tap immediately, for multi-tap we need to remember the timestamp of the first press event and use it for the release event so that there's a forced gap between the release and the second press. https://bugs.freedesktop.org/show_bug.cgi?id=89511 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-04-16 10:19:11 +10:00
<g fill="#000000" font-family="Helvetica" text-anchor="middle" font-size="12px">
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<text x="61239.75" y="45233.75">
touchpad: end tap-and-drag with an extra tap Currently for the tap-and-drag gesture to end user has to wait for a timeout to expire. Make it possible to end the drag gesture by just tapping. The allowed finger sequences to start and end a drag are thus: tap, down, .... move ...., up <wait for timeout> tap, down, .... move ...., up, tap https://bugs.freedesktop.org/show_bug.cgi?id=90255 Signed-off-by: Velimir Lisec <lisec.velimir@gmail.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> State diagram changes and a doc change squashed in. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-04-30 00:13:51 +02:00
fourth</text>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<text x="61239.75" y="45247.75">
touchpad: end tap-and-drag with an extra tap Currently for the tap-and-drag gesture to end user has to wait for a timeout to expire. Make it possible to end the drag gesture by just tapping. The allowed finger sequences to start and end a drag are thus: tap, down, .... move ...., up <wait for timeout> tap, down, .... move ...., up, tap https://bugs.freedesktop.org/show_bug.cgi?id=90255 Signed-off-by: Velimir Lisec <lisec.velimir@gmail.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> State diagram changes and a doc change squashed in. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-04-30 00:13:51 +02:00
finger down</text>
touchpad: introduce MULTITAP for multi-tap-and-drag Once we have a doubletap, enter a loop in the state machine where we can tap multiple times and either get a multi-click or a multi-click drag-and-drop. The sequence down/up down/up down/up produces a triple-click. The sequence down/up down/up down/up down produces a triple-click with a button down for dragging. Yes, that glorious octuple-tap-and-drag, it is now possible. World domination has been achieved, thank you for playing. We don't know when we finish tapping now, so add a timeout to send the last click event once the finger has been released for the last time. This guarantees that the timestamp of the last button down is later than the last release. This avoids the bug fixed in synaptics commit xf86-input-synaptics-1.8.0-21-g37d34f0 (some application don't handle doubletap correctly without the timestamps). This works for double-tap immediately, for multi-tap we need to remember the timestamp of the first press event and use it for the release event so that there's a forced gap between the release and the second press. https://bugs.freedesktop.org/show_bug.cgi?id=89511 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-04-16 10:19:11 +10:00
</g>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<rect x="60971" y="45332" width="130" height="40" rx="2.4" ry="2.4" fill="#ccffcc" stroke="#000000" stroke-width="2" pointer-events="none"/>
touchpad: introduce MULTITAP for multi-tap-and-drag Once we have a doubletap, enter a loop in the state machine where we can tap multiple times and either get a multi-click or a multi-click drag-and-drop. The sequence down/up down/up down/up produces a triple-click. The sequence down/up down/up down/up down produces a triple-click with a button down for dragging. Yes, that glorious octuple-tap-and-drag, it is now possible. World domination has been achieved, thank you for playing. We don't know when we finish tapping now, so add a timeout to send the last click event once the finger has been released for the last time. This guarantees that the timestamp of the last button down is later than the last release. This avoids the bug fixed in synaptics commit xf86-input-synaptics-1.8.0-21-g37d34f0 (some application don't handle doubletap correctly without the timestamps). This works for double-tap immediately, for multi-tap we need to remember the timestamp of the first press event and use it for the release event so that there's a forced gap between the release and the second press. https://bugs.freedesktop.org/show_bug.cgi?id=89511 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-04-16 10:19:11 +10:00
<g fill="#000000" font-family="Helvetica" text-anchor="middle" font-size="12px">
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<text x="61035.75" y="45355.75">
touchpad: end tap-and-drag with an extra tap Currently for the tap-and-drag gesture to end user has to wait for a timeout to expire. Make it possible to end the drag gesture by just tapping. The allowed finger sequences to start and end a drag are thus: tap, down, .... move ...., up <wait for timeout> tap, down, .... move ...., up, tap https://bugs.freedesktop.org/show_bug.cgi?id=90255 Signed-off-by: Velimir Lisec <lisec.velimir@gmail.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> State diagram changes and a doc change squashed in. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-04-30 00:13:51 +02:00
DEAD</text>
touchpad: introduce MULTITAP for multi-tap-and-drag Once we have a doubletap, enter a loop in the state machine where we can tap multiple times and either get a multi-click or a multi-click drag-and-drop. The sequence down/up down/up down/up produces a triple-click. The sequence down/up down/up down/up down produces a triple-click with a button down for dragging. Yes, that glorious octuple-tap-and-drag, it is now possible. World domination has been achieved, thank you for playing. We don't know when we finish tapping now, so add a timeout to send the last click event once the finger has been released for the last time. This guarantees that the timestamp of the last button down is later than the last release. This avoids the bug fixed in synaptics commit xf86-input-synaptics-1.8.0-21-g37d34f0 (some application don't handle doubletap correctly without the timestamps). This works for double-tap immediately, for multi-tap we need to remember the timestamp of the first press event and use it for the release event so that there's a forced gap between the release and the second press. https://bugs.freedesktop.org/show_bug.cgi?id=89511 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-04-16 10:19:11 +10:00
</g>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<path d="M 61477.4 45114 L 61294.15 45208.94" fill="none" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 61289.49 45211.36 L 61294.1 45205.03 L 61294.15 45208.94 L 61297.32 45211.24 Z" fill="#000000" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 61191.5 45264.34 L 61077.03 45328.87" fill="none" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 61072.45 45331.45 L 61076.83 45324.96 L 61077.03 45328.87 L 61080.27 45331.06 Z" fill="#000000" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 61146.38 44437 L 61039.18 45325.68" fill="none" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 61038.55 45330.89 L 61035.91 45323.52 L 61039.18 45325.68 L 61042.86 45324.36 Z" fill="#000000" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 60952.04 45427 C 60954.84 45423.86 60958.82 45422.05 60963.02 45422 L 60996.99 45422 C 61001.19 45422.05 61005.17 45423.86 61007.97 45427 L 61027.95 45450 C 61028.51 45451.28 61028.51 45452.72 61027.95 45454 L 61007.97 45477 C 61005.17 45480.14 61001.19 45481.95 60996.99 45482 L 60963.02 45482 C 60958.82 45481.95 60954.84 45480.14 60952.04 45477 L 60932.06 45454 C 60931.5 45452.72 60931.5 45451.28 60932.06 45450 L 60952.04 45427 Z" fill="#e1d5e7" stroke="#000000" stroke-width="2" stroke-miterlimit="10" pointer-events="none"/>
touchpad: introduce MULTITAP for multi-tap-and-drag Once we have a doubletap, enter a loop in the state machine where we can tap multiple times and either get a multi-click or a multi-click drag-and-drop. The sequence down/up down/up down/up produces a triple-click. The sequence down/up down/up down/up down produces a triple-click with a button down for dragging. Yes, that glorious octuple-tap-and-drag, it is now possible. World domination has been achieved, thank you for playing. We don't know when we finish tapping now, so add a timeout to send the last click event once the finger has been released for the last time. This guarantees that the timestamp of the last button down is later than the last release. This avoids the bug fixed in synaptics commit xf86-input-synaptics-1.8.0-21-g37d34f0 (some application don't handle doubletap correctly without the timestamps). This works for double-tap immediately, for multi-tap we need to remember the timestamp of the first press event and use it for the release event so that there's a forced gap between the release and the second press. https://bugs.freedesktop.org/show_bug.cgi?id=89511 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-04-16 10:19:11 +10:00
<g fill="#000000" font-family="Helvetica" text-anchor="middle" font-size="12px">
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<text x="60979.75" y="45455.75">
touchpad: end tap-and-drag with an extra tap Currently for the tap-and-drag gesture to end user has to wait for a timeout to expire. Make it possible to end the drag gesture by just tapping. The allowed finger sequences to start and end a drag are thus: tap, down, .... move ...., up <wait for timeout> tap, down, .... move ...., up, tap https://bugs.freedesktop.org/show_bug.cgi?id=90255 Signed-off-by: Velimir Lisec <lisec.velimir@gmail.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> State diagram changes and a doc change squashed in. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-04-30 00:13:51 +02:00
any finger up</text>
touchpad: introduce MULTITAP for multi-tap-and-drag Once we have a doubletap, enter a loop in the state machine where we can tap multiple times and either get a multi-click or a multi-click drag-and-drop. The sequence down/up down/up down/up produces a triple-click. The sequence down/up down/up down/up down produces a triple-click with a button down for dragging. Yes, that glorious octuple-tap-and-drag, it is now possible. World domination has been achieved, thank you for playing. We don't know when we finish tapping now, so add a timeout to send the last click event once the finger has been released for the last time. This guarantees that the timestamp of the last button down is later than the last release. This avoids the bug fixed in synaptics commit xf86-input-synaptics-1.8.0-21-g37d34f0 (some application don't handle doubletap correctly without the timestamps). This works for double-tap immediately, for multi-tap we need to remember the timestamp of the first press event and use it for the release event so that there's a forced gap between the release and the second press. https://bugs.freedesktop.org/show_bug.cgi?id=89511 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-04-16 10:19:11 +10:00
</g>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<path d="M 61094.54 45456 C 61097.34 45452.86 61101.32 45451.05 61105.52 45451 L 61139.49 45451 C 61143.69 45451.05 61147.67 45452.86 61150.47 45456 L 61170.45 45479 C 61171.01 45480.28 61171.01 45481.72 61170.45 45483 L 61150.47 45506 C 61147.67 45509.14 61143.69 45510.95 61139.49 45511 L 61105.52 45511 C 61101.32 45510.95 61097.34 45509.14 61094.54 45506 L 61074.56 45483 C 61074 45481.72 61074 45480.28 61074.56 45479 L 61094.54 45456 Z" fill="#ffffff" stroke="#000000" stroke-width="2" stroke-miterlimit="10" pointer-events="none"/>
touchpad: introduce MULTITAP for multi-tap-and-drag Once we have a doubletap, enter a loop in the state machine where we can tap multiple times and either get a multi-click or a multi-click drag-and-drop. The sequence down/up down/up down/up produces a triple-click. The sequence down/up down/up down/up down produces a triple-click with a button down for dragging. Yes, that glorious octuple-tap-and-drag, it is now possible. World domination has been achieved, thank you for playing. We don't know when we finish tapping now, so add a timeout to send the last click event once the finger has been released for the last time. This guarantees that the timestamp of the last button down is later than the last release. This avoids the bug fixed in synaptics commit xf86-input-synaptics-1.8.0-21-g37d34f0 (some application don't handle doubletap correctly without the timestamps). This works for double-tap immediately, for multi-tap we need to remember the timestamp of the first press event and use it for the release event so that there's a forced gap between the release and the second press. https://bugs.freedesktop.org/show_bug.cgi?id=89511 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-04-16 10:19:11 +10:00
<g fill="#000000" font-family="Helvetica" text-anchor="middle" font-size="12px">
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<text x="61122.25" y="45477.75">
touchpad: end tap-and-drag with an extra tap Currently for the tap-and-drag gesture to end user has to wait for a timeout to expire. Make it possible to end the drag gesture by just tapping. The allowed finger sequences to start and end a drag are thus: tap, down, .... move ...., up <wait for timeout> tap, down, .... move ...., up, tap https://bugs.freedesktop.org/show_bug.cgi?id=90255 Signed-off-by: Velimir Lisec <lisec.velimir@gmail.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> State diagram changes and a doc change squashed in. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-04-30 00:13:51 +02:00
fourth</text>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<text x="61122.25" y="45491.75">
touchpad: end tap-and-drag with an extra tap Currently for the tap-and-drag gesture to end user has to wait for a timeout to expire. Make it possible to end the drag gesture by just tapping. The allowed finger sequences to start and end a drag are thus: tap, down, .... move ...., up <wait for timeout> tap, down, .... move ...., up, tap https://bugs.freedesktop.org/show_bug.cgi?id=90255 Signed-off-by: Velimir Lisec <lisec.velimir@gmail.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> State diagram changes and a doc change squashed in. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-04-30 00:13:51 +02:00
finger up</text>
touchpad: introduce MULTITAP for multi-tap-and-drag Once we have a doubletap, enter a loop in the state machine where we can tap multiple times and either get a multi-click or a multi-click drag-and-drop. The sequence down/up down/up down/up produces a triple-click. The sequence down/up down/up down/up down produces a triple-click with a button down for dragging. Yes, that glorious octuple-tap-and-drag, it is now possible. World domination has been achieved, thank you for playing. We don't know when we finish tapping now, so add a timeout to send the last click event once the finger has been released for the last time. This guarantees that the timestamp of the last button down is later than the last release. This avoids the bug fixed in synaptics commit xf86-input-synaptics-1.8.0-21-g37d34f0 (some application don't handle doubletap correctly without the timestamps). This works for double-tap immediately, for multi-tap we need to remember the timestamp of the first press event and use it for the release event so that there's a forced gap between the release and the second press. https://bugs.freedesktop.org/show_bug.cgi?id=89511 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-04-16 10:19:11 +10:00
</g>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<path d="M 61274.54 44387 C 61277.34 44383.86 61281.32 44382.05 61285.52 44382 L 61319.49 44382 C 61323.69 44382.05 61327.67 44383.86 61330.47 44387 L 61350.45 44410 C 61351.01 44411.28 61351.01 44412.72 61350.45 44414 L 61330.47 44437 C 61327.67 44440.14 61323.69 44441.95 61319.49 44442 L 61285.52 44442 C 61281.32 44441.95 61277.34 44440.14 61274.54 44437 L 61254.56 44414 C 61254 44412.72 61254 44411.28 61254.56 44410 L 61274.54 44387 Z" fill="#e1d5e7" stroke="#000000" stroke-width="2" stroke-miterlimit="10" pointer-events="none"/>
touchpad: introduce MULTITAP for multi-tap-and-drag Once we have a doubletap, enter a loop in the state machine where we can tap multiple times and either get a multi-click or a multi-click drag-and-drop. The sequence down/up down/up down/up produces a triple-click. The sequence down/up down/up down/up down produces a triple-click with a button down for dragging. Yes, that glorious octuple-tap-and-drag, it is now possible. World domination has been achieved, thank you for playing. We don't know when we finish tapping now, so add a timeout to send the last click event once the finger has been released for the last time. This guarantees that the timestamp of the last button down is later than the last release. This avoids the bug fixed in synaptics commit xf86-input-synaptics-1.8.0-21-g37d34f0 (some application don't handle doubletap correctly without the timestamps). This works for double-tap immediately, for multi-tap we need to remember the timestamp of the first press event and use it for the release event so that there's a forced gap between the release and the second press. https://bugs.freedesktop.org/show_bug.cgi?id=89511 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-04-16 10:19:11 +10:00
<g fill="#000000" font-family="Helvetica" text-anchor="middle" font-size="12px">
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<text x="61302.25" y="44415.75">
touchpad: end tap-and-drag with an extra tap Currently for the tap-and-drag gesture to end user has to wait for a timeout to expire. Make it possible to end the drag gesture by just tapping. The allowed finger sequences to start and end a drag are thus: tap, down, .... move ...., up <wait for timeout> tap, down, .... move ...., up, tap https://bugs.freedesktop.org/show_bug.cgi?id=90255 Signed-off-by: Velimir Lisec <lisec.velimir@gmail.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> State diagram changes and a doc change squashed in. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-04-30 00:13:51 +02:00
any finger up</text>
touchpad: introduce MULTITAP for multi-tap-and-drag Once we have a doubletap, enter a loop in the state machine where we can tap multiple times and either get a multi-click or a multi-click drag-and-drop. The sequence down/up down/up down/up produces a triple-click. The sequence down/up down/up down/up down produces a triple-click with a button down for dragging. Yes, that glorious octuple-tap-and-drag, it is now possible. World domination has been achieved, thank you for playing. We don't know when we finish tapping now, so add a timeout to send the last click event once the finger has been released for the last time. This guarantees that the timestamp of the last button down is later than the last release. This avoids the bug fixed in synaptics commit xf86-input-synaptics-1.8.0-21-g37d34f0 (some application don't handle doubletap correctly without the timestamps). This works for double-tap immediately, for multi-tap we need to remember the timestamp of the first press event and use it for the release event so that there's a forced gap between the release and the second press. https://bugs.freedesktop.org/show_bug.cgi?id=89511 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-04-16 10:19:11 +10:00
</g>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<path d="M 61345.58 44237 L 61311.41 44375.82" fill="none" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 61310.15 44380.91 L 61308.43 44373.28 L 61311.41 44375.82 L 61315.22 44374.95 Z" fill="#000000" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 61283.82 44600 L 61249.44 44692.03" fill="none" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 61247.6 44696.95 L 61246.77 44689.17 L 61249.44 44692.03 L 61253.33 44691.62 Z" fill="#000000" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
touchpad: disable tapping for fingers exceeding the timeout/motion threshold The current code triggers multi-finger tapping even if the finger released was previously held on the touchpad for a while. For an event sequence of: 1. first finger down 2. first finger move past threshold/wait past timeout 3. second finger down 4. first finger up The second finger initiates the two-finger tap state, but the button event is sent when the first finger releases - despite that finger not meeting the usual tap constraints. This sequence can happen whenever a user swaps fingers. Add the finger state to the actual touchpoints and update them whenever the constrains are broken. Then, discard button events if the respective touch did not meet the conditions. http://bugs.freedesktop.org/76760 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2014-06-20 14:16:13 +10:00
<g fill="#000000" font-family="Helvetica" text-anchor="middle" font-size="11px">
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<rect fill="#ffffff" stroke="none" x="61256" y="44636" width="20" height="27" stroke-width="0"/>
<text x="61265.62" y="44658.71">
touchpad: end tap-and-drag with an extra tap Currently for the tap-and-drag gesture to end user has to wait for a timeout to expire. Make it possible to end the drag gesture by just tapping. The allowed finger sequences to start and end a drag are thus: tap, down, .... move ...., up <wait for timeout> tap, down, .... move ...., up, tap https://bugs.freedesktop.org/show_bug.cgi?id=90255 Signed-off-by: Velimir Lisec <lisec.velimir@gmail.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> State diagram changes and a doc change squashed in. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-04-30 00:13:51 +02:00
yes</text>
touchpad: introduce MULTITAP for multi-tap-and-drag Once we have a doubletap, enter a loop in the state machine where we can tap multiple times and either get a multi-click or a multi-click drag-and-drop. The sequence down/up down/up down/up produces a triple-click. The sequence down/up down/up down/up down produces a triple-click with a button down for dragging. Yes, that glorious octuple-tap-and-drag, it is now possible. World domination has been achieved, thank you for playing. We don't know when we finish tapping now, so add a timeout to send the last click event once the finger has been released for the last time. This guarantees that the timestamp of the last button down is later than the last release. This avoids the bug fixed in synaptics commit xf86-input-synaptics-1.8.0-21-g37d34f0 (some application don't handle doubletap correctly without the timestamps). This works for double-tap immediately, for multi-tap we need to remember the timestamp of the first press event and use it for the release event so that there's a forced gap between the release and the second press. https://bugs.freedesktop.org/show_bug.cgi?id=89511 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-04-16 10:19:11 +10:00
</g>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<path d="M 61508.04 45182 C 61510.84 45178.86 61514.82 45177.05 61519.02 45177 L 61552.99 45177 C 61557.19 45177.05 61561.17 45178.86 61563.97 45182 L 61583.95 45205 C 61584.51 45206.28 61584.51 45207.72 61583.95 45209 L 61563.97 45232 C 61561.17 45235.14 61557.19 45236.95 61552.99 45237 L 61519.02 45237 C 61514.82 45236.95 61510.84 45235.14 61508.04 45232 L 61488.06 45209 C 61487.5 45207.72 61487.5 45206.28 61488.06 45205 L 61508.04 45182 Z" fill="#e1d5e7" stroke="#000000" stroke-width="2" stroke-miterlimit="10" pointer-events="none"/>
touchpad: introduce MULTITAP for multi-tap-and-drag Once we have a doubletap, enter a loop in the state machine where we can tap multiple times and either get a multi-click or a multi-click drag-and-drop. The sequence down/up down/up down/up produces a triple-click. The sequence down/up down/up down/up down produces a triple-click with a button down for dragging. Yes, that glorious octuple-tap-and-drag, it is now possible. World domination has been achieved, thank you for playing. We don't know when we finish tapping now, so add a timeout to send the last click event once the finger has been released for the last time. This guarantees that the timestamp of the last button down is later than the last release. This avoids the bug fixed in synaptics commit xf86-input-synaptics-1.8.0-21-g37d34f0 (some application don't handle doubletap correctly without the timestamps). This works for double-tap immediately, for multi-tap we need to remember the timestamp of the first press event and use it for the release event so that there's a forced gap between the release and the second press. https://bugs.freedesktop.org/show_bug.cgi?id=89511 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-04-16 10:19:11 +10:00
<g fill="#000000" font-family="Helvetica" text-anchor="middle" font-size="12px">
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<text x="61535.75" y="45210.75">
touchpad: end tap-and-drag with an extra tap Currently for the tap-and-drag gesture to end user has to wait for a timeout to expire. Make it possible to end the drag gesture by just tapping. The allowed finger sequences to start and end a drag are thus: tap, down, .... move ...., up <wait for timeout> tap, down, .... move ...., up, tap https://bugs.freedesktop.org/show_bug.cgi?id=90255 Signed-off-by: Velimir Lisec <lisec.velimir@gmail.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> State diagram changes and a doc change squashed in. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-04-30 00:13:51 +02:00
any finger up</text>
touchpad: introduce MULTITAP for multi-tap-and-drag Once we have a doubletap, enter a loop in the state machine where we can tap multiple times and either get a multi-click or a multi-click drag-and-drop. The sequence down/up down/up down/up produces a triple-click. The sequence down/up down/up down/up down produces a triple-click with a button down for dragging. Yes, that glorious octuple-tap-and-drag, it is now possible. World domination has been achieved, thank you for playing. We don't know when we finish tapping now, so add a timeout to send the last click event once the finger has been released for the last time. This guarantees that the timestamp of the last button down is later than the last release. This avoids the bug fixed in synaptics commit xf86-input-synaptics-1.8.0-21-g37d34f0 (some application don't handle doubletap correctly without the timestamps). This works for double-tap immediately, for multi-tap we need to remember the timestamp of the first press event and use it for the release event so that there's a forced gap between the release and the second press. https://bugs.freedesktop.org/show_bug.cgi?id=89511 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-04-16 10:19:11 +10:00
</g>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<path d="M 61519.54 45114 L 61529.58 45170.73" fill="none" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 61530.5 45175.9 L 61525.83 45169.62 L 61529.58 45170.73 L 61532.72 45168.4 Z" fill="#000000" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 61874.5 45202 L 61981 45202 Q 61991 45202 61991 45192 L 61991 43997 Q 61991 43987 61981 43987 L 61848.62 43987" fill="none" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 61843.37 43987 L 61850.37 43983.5 L 61848.62 43987 L 61850.37 43990.5 Z" fill="#000000" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 61024.8 45372 L 60999.91 45416.44" fill="none" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 60997.35 45421.02 L 60997.71 45413.21 L 60999.91 45416.44 L 61003.82 45416.63 Z" fill="#000000" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 61049.41 45372 L 61098.84 45445.71" fill="none" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 61101.76 45450.07 L 61094.96 45446.21 L 61098.84 45445.71 L 61100.77 45442.31 Z" fill="#000000" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<ellipse cx="61043" cy="45832" rx="49.5" ry="30" fill="#ccccff" stroke="#000000" stroke-width="2" pointer-events="none"/>
<g fill="#000000" font-family="Helvetica" text-anchor="middle" font-size="12px">
<text x="61042.75" y="45835.75">
touchpad: end tap-and-drag with an extra tap Currently for the tap-and-drag gesture to end user has to wait for a timeout to expire. Make it possible to end the drag gesture by just tapping. The allowed finger sequences to start and end a drag are thus: tap, down, .... move ...., up <wait for timeout> tap, down, .... move ...., up, tap https://bugs.freedesktop.org/show_bug.cgi?id=90255 Signed-off-by: Velimir Lisec <lisec.velimir@gmail.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> State diagram changes and a doc change squashed in. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-04-30 00:13:51 +02:00
IDLE</text>
touchpad: introduce MULTITAP for multi-tap-and-drag Once we have a doubletap, enter a loop in the state machine where we can tap multiple times and either get a multi-click or a multi-click drag-and-drop. The sequence down/up down/up down/up produces a triple-click. The sequence down/up down/up down/up down produces a triple-click with a button down for dragging. Yes, that glorious octuple-tap-and-drag, it is now possible. World domination has been achieved, thank you for playing. We don't know when we finish tapping now, so add a timeout to send the last click event once the finger has been released for the last time. This guarantees that the timestamp of the last button down is later than the last release. This avoids the bug fixed in synaptics commit xf86-input-synaptics-1.8.0-21-g37d34f0 (some application don't handle doubletap correctly without the timestamps). This works for double-tap immediately, for multi-tap we need to remember the timestamp of the first press event and use it for the release event so that there's a forced gap between the release and the second press. https://bugs.freedesktop.org/show_bug.cgi?id=89511 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-04-16 10:19:11 +10:00
</g>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<path d="M 61038.4 45672 L 61090 45717 L 61038.4 45762 L 60986.8 45717 Z" fill="#ffffff" stroke="#000000" stroke-width="2" stroke-miterlimit="10" pointer-events="none"/>
touchpad: introduce MULTITAP for multi-tap-and-drag Once we have a doubletap, enter a loop in the state machine where we can tap multiple times and either get a multi-click or a multi-click drag-and-drop. The sequence down/up down/up down/up produces a triple-click. The sequence down/up down/up down/up down produces a triple-click with a button down for dragging. Yes, that glorious octuple-tap-and-drag, it is now possible. World domination has been achieved, thank you for playing. We don't know when we finish tapping now, so add a timeout to send the last click event once the finger has been released for the last time. This guarantees that the timestamp of the last button down is later than the last release. This avoids the bug fixed in synaptics commit xf86-input-synaptics-1.8.0-21-g37d34f0 (some application don't handle doubletap correctly without the timestamps). This works for double-tap immediately, for multi-tap we need to remember the timestamp of the first press event and use it for the release event so that there's a forced gap between the release and the second press. https://bugs.freedesktop.org/show_bug.cgi?id=89511 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-04-16 10:19:11 +10:00
<g fill="#000000" font-family="Helvetica" text-anchor="middle" font-size="12px">
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<text x="61038.15" y="45713.75">
touchpad: end tap-and-drag with an extra tap Currently for the tap-and-drag gesture to end user has to wait for a timeout to expire. Make it possible to end the drag gesture by just tapping. The allowed finger sequences to start and end a drag are thus: tap, down, .... move ...., up <wait for timeout> tap, down, .... move ...., up, tap https://bugs.freedesktop.org/show_bug.cgi?id=90255 Signed-off-by: Velimir Lisec <lisec.velimir@gmail.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> State diagram changes and a doc change squashed in. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-04-30 00:13:51 +02:00
if finger</text>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<text x="61038.15" y="45727.75">
touchpad: end tap-and-drag with an extra tap Currently for the tap-and-drag gesture to end user has to wait for a timeout to expire. Make it possible to end the drag gesture by just tapping. The allowed finger sequences to start and end a drag are thus: tap, down, .... move ...., up <wait for timeout> tap, down, .... move ...., up, tap https://bugs.freedesktop.org/show_bug.cgi?id=90255 Signed-off-by: Velimir Lisec <lisec.velimir@gmail.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> State diagram changes and a doc change squashed in. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-04-30 00:13:51 +02:00
count == 0</text>
touchpad: introduce MULTITAP for multi-tap-and-drag Once we have a doubletap, enter a loop in the state machine where we can tap multiple times and either get a multi-click or a multi-click drag-and-drop. The sequence down/up down/up down/up produces a triple-click. The sequence down/up down/up down/up down produces a triple-click with a button down for dragging. Yes, that glorious octuple-tap-and-drag, it is now possible. World domination has been achieved, thank you for playing. We don't know when we finish tapping now, so add a timeout to send the last click event once the finger has been released for the last time. This guarantees that the timestamp of the last button down is later than the last release. This avoids the bug fixed in synaptics commit xf86-input-synaptics-1.8.0-21-g37d34f0 (some application don't handle doubletap correctly without the timestamps). This works for double-tap immediately, for multi-tap we need to remember the timestamp of the first press event and use it for the release event so that there's a forced gap between the release and the second press. https://bugs.freedesktop.org/show_bug.cgi?id=89511 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-04-16 10:19:11 +10:00
</g>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<path d="M 60996.19 45575.5 L 61023.16 45665.9" fill="none" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 61024.66 45670.93 L 61019.3 45665.22 L 61023.16 45665.9 L 61026.01 45663.22 Z" fill="#000000" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 61111.81 45511 L 61056.57 45666" fill="none" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 61054.81 45670.95 L 61053.86 45663.18 L 61056.57 45666 L 61060.46 45665.53 Z" fill="#000000" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 61040.2 45762 L 61041.55 45795.64" fill="none" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 61041.76 45800.88 L 61037.98 45794.03 L 61041.55 45795.64 L 61044.97 45793.75 Z" fill="#000000" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 60575.54 44495 C 60578.34 44491.86 60582.32 44490.05 60586.52 44490 L 60620.49 44490 C 60624.69 44490.05 60628.67 44491.86 60631.47 44495 L 60651.45 44518 C 60652.01 44519.28 60652.01 44520.72 60651.45 44522 L 60631.47 44545 C 60628.67 44548.14 60624.69 44549.95 60620.49 44550 L 60586.52 44550 C 60582.32 44549.95 60578.34 44548.14 60575.54 44545 L 60555.56 44522 C 60555 44520.72 60555 44519.28 60555.56 44518 L 60575.54 44495 Z" fill="#7ea6e0" stroke="#000000" stroke-width="2" stroke-miterlimit="10" pointer-events="none"/>
touchpad: introduce MULTITAP for multi-tap-and-drag Once we have a doubletap, enter a loop in the state machine where we can tap multiple times and either get a multi-click or a multi-click drag-and-drop. The sequence down/up down/up down/up produces a triple-click. The sequence down/up down/up down/up down produces a triple-click with a button down for dragging. Yes, that glorious octuple-tap-and-drag, it is now possible. World domination has been achieved, thank you for playing. We don't know when we finish tapping now, so add a timeout to send the last click event once the finger has been released for the last time. This guarantees that the timestamp of the last button down is later than the last release. This avoids the bug fixed in synaptics commit xf86-input-synaptics-1.8.0-21-g37d34f0 (some application don't handle doubletap correctly without the timestamps). This works for double-tap immediately, for multi-tap we need to remember the timestamp of the first press event and use it for the release event so that there's a forced gap between the release and the second press. https://bugs.freedesktop.org/show_bug.cgi?id=89511 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-04-16 10:19:11 +10:00
<g fill="#000000" font-family="Helvetica" text-anchor="middle" font-size="12px">
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<text x="60603.25" y="44516.75">
touchpad: end tap-and-drag with an extra tap Currently for the tap-and-drag gesture to end user has to wait for a timeout to expire. Make it possible to end the drag gesture by just tapping. The allowed finger sequences to start and end a drag are thus: tap, down, .... move ...., up <wait for timeout> tap, down, .... move ...., up, tap https://bugs.freedesktop.org/show_bug.cgi?id=90255 Signed-off-by: Velimir Lisec <lisec.velimir@gmail.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> State diagram changes and a doc change squashed in. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-04-30 00:13:51 +02:00
second</text>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<text x="60603.25" y="44530.75">
touchpad: end tap-and-drag with an extra tap Currently for the tap-and-drag gesture to end user has to wait for a timeout to expire. Make it possible to end the drag gesture by just tapping. The allowed finger sequences to start and end a drag are thus: tap, down, .... move ...., up <wait for timeout> tap, down, .... move ...., up, tap https://bugs.freedesktop.org/show_bug.cgi?id=90255 Signed-off-by: Velimir Lisec <lisec.velimir@gmail.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> State diagram changes and a doc change squashed in. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-04-30 00:13:51 +02:00
finger up</text>
touchpad: introduce MULTITAP for multi-tap-and-drag Once we have a doubletap, enter a loop in the state machine where we can tap multiple times and either get a multi-click or a multi-click drag-and-drop. The sequence down/up down/up down/up produces a triple-click. The sequence down/up down/up down/up down produces a triple-click with a button down for dragging. Yes, that glorious octuple-tap-and-drag, it is now possible. World domination has been achieved, thank you for playing. We don't know when we finish tapping now, so add a timeout to send the last click event once the finger has been released for the last time. This guarantees that the timestamp of the last button down is later than the last release. This avoids the bug fixed in synaptics commit xf86-input-synaptics-1.8.0-21-g37d34f0 (some application don't handle doubletap correctly without the timestamps). This works for double-tap immediately, for multi-tap we need to remember the timestamp of the first press event and use it for the release event so that there's a forced gap between the release and the second press. https://bugs.freedesktop.org/show_bug.cgi?id=89511 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-04-16 10:19:11 +10:00
</g>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<rect x="60516" y="44337" width="130" height="40" rx="2.4" ry="2.4" fill="#ccffcc" stroke="#000000" stroke-width="2" pointer-events="none"/>
touchpad: introduce MULTITAP for multi-tap-and-drag Once we have a doubletap, enter a loop in the state machine where we can tap multiple times and either get a multi-click or a multi-click drag-and-drop. The sequence down/up down/up down/up produces a triple-click. The sequence down/up down/up down/up down produces a triple-click with a button down for dragging. Yes, that glorious octuple-tap-and-drag, it is now possible. World domination has been achieved, thank you for playing. We don't know when we finish tapping now, so add a timeout to send the last click event once the finger has been released for the last time. This guarantees that the timestamp of the last button down is later than the last release. This avoids the bug fixed in synaptics commit xf86-input-synaptics-1.8.0-21-g37d34f0 (some application don't handle doubletap correctly without the timestamps). This works for double-tap immediately, for multi-tap we need to remember the timestamp of the first press event and use it for the release event so that there's a forced gap between the release and the second press. https://bugs.freedesktop.org/show_bug.cgi?id=89511 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-04-16 10:19:11 +10:00
<g fill="#000000" font-family="Helvetica" text-anchor="middle" font-size="12px">
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<text x="60580.75" y="44360.75">
touchpad: end tap-and-drag with an extra tap Currently for the tap-and-drag gesture to end user has to wait for a timeout to expire. Make it possible to end the drag gesture by just tapping. The allowed finger sequences to start and end a drag are thus: tap, down, .... move ...., up <wait for timeout> tap, down, .... move ...., up, tap https://bugs.freedesktop.org/show_bug.cgi?id=90255 Signed-off-by: Velimir Lisec <lisec.velimir@gmail.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> State diagram changes and a doc change squashed in. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-04-30 00:13:51 +02:00
DRAGGING_2</text>
touchpad: introduce MULTITAP for multi-tap-and-drag Once we have a doubletap, enter a loop in the state machine where we can tap multiple times and either get a multi-click or a multi-click drag-and-drop. The sequence down/up down/up down/up produces a triple-click. The sequence down/up down/up down/up down produces a triple-click with a button down for dragging. Yes, that glorious octuple-tap-and-drag, it is now possible. World domination has been achieved, thank you for playing. We don't know when we finish tapping now, so add a timeout to send the last click event once the finger has been released for the last time. This guarantees that the timestamp of the last button down is later than the last release. This avoids the bug fixed in synaptics commit xf86-input-synaptics-1.8.0-21-g37d34f0 (some application don't handle doubletap correctly without the timestamps). This works for double-tap immediately, for multi-tap we need to remember the timestamp of the first press event and use it for the release event so that there's a forced gap between the release and the second press. https://bugs.freedesktop.org/show_bug.cgi?id=89511 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-04-16 10:19:11 +10:00
</g>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<path d="M 60595.27 44282.5 L 60586.03 44330.75" fill="none" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 60585.04 44335.9 L 60582.92 44328.37 L 60586.03 44330.75 L 60589.8 44329.69 Z" fill="#000000" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 60583.76 44377 L 60598.49 44483.69" fill="none" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 60599.21 44488.89 L 60594.78 44482.44 L 60598.49 44483.69 L 60601.72 44481.48 Z" fill="#000000" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 60402.54 44559 C 60405.34 44555.86 60409.32 44554.05 60413.52 44554 L 60447.49 44554 C 60451.69 44554.05 60455.67 44555.86 60458.47 44559 L 60478.45 44582 C 60479.01 44583.28 60479.01 44584.72 60478.45 44586 L 60458.47 44609 C 60455.67 44612.14 60451.69 44613.95 60447.49 44614 L 60413.52 44614 C 60409.32 44613.95 60405.34 44612.14 60402.54 44609 L 60382.56 44586 C 60382 44584.72 60382 44583.28 60382.56 44582 L 60402.54 44559 Z" fill="#ffd966" stroke="#000000" stroke-width="2" stroke-miterlimit="10" pointer-events="none"/>
touchpad: introduce MULTITAP for multi-tap-and-drag Once we have a doubletap, enter a loop in the state machine where we can tap multiple times and either get a multi-click or a multi-click drag-and-drop. The sequence down/up down/up down/up produces a triple-click. The sequence down/up down/up down/up down produces a triple-click with a button down for dragging. Yes, that glorious octuple-tap-and-drag, it is now possible. World domination has been achieved, thank you for playing. We don't know when we finish tapping now, so add a timeout to send the last click event once the finger has been released for the last time. This guarantees that the timestamp of the last button down is later than the last release. This avoids the bug fixed in synaptics commit xf86-input-synaptics-1.8.0-21-g37d34f0 (some application don't handle doubletap correctly without the timestamps). This works for double-tap immediately, for multi-tap we need to remember the timestamp of the first press event and use it for the release event so that there's a forced gap between the release and the second press. https://bugs.freedesktop.org/show_bug.cgi?id=89511 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-04-16 10:19:11 +10:00
<g fill="#000000" font-family="Helvetica" text-anchor="middle" font-size="12px">
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<text x="60430.25" y="44580.75">
touchpad: end tap-and-drag with an extra tap Currently for the tap-and-drag gesture to end user has to wait for a timeout to expire. Make it possible to end the drag gesture by just tapping. The allowed finger sequences to start and end a drag are thus: tap, down, .... move ...., up <wait for timeout> tap, down, .... move ...., up, tap https://bugs.freedesktop.org/show_bug.cgi?id=90255 Signed-off-by: Velimir Lisec <lisec.velimir@gmail.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> State diagram changes and a doc change squashed in. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-04-30 00:13:51 +02:00
first</text>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<text x="60430.25" y="44594.75">
touchpad: end tap-and-drag with an extra tap Currently for the tap-and-drag gesture to end user has to wait for a timeout to expire. Make it possible to end the drag gesture by just tapping. The allowed finger sequences to start and end a drag are thus: tap, down, .... move ...., up <wait for timeout> tap, down, .... move ...., up, tap https://bugs.freedesktop.org/show_bug.cgi?id=90255 Signed-off-by: Velimir Lisec <lisec.velimir@gmail.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> State diagram changes and a doc change squashed in. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-04-30 00:13:51 +02:00
finger up</text>
touchpad: introduce MULTITAP for multi-tap-and-drag Once we have a doubletap, enter a loop in the state machine where we can tap multiple times and either get a multi-click or a multi-click drag-and-drop. The sequence down/up down/up down/up produces a triple-click. The sequence down/up down/up down/up down produces a triple-click with a button down for dragging. Yes, that glorious octuple-tap-and-drag, it is now possible. World domination has been achieved, thank you for playing. We don't know when we finish tapping now, so add a timeout to send the last click event once the finger has been released for the last time. This guarantees that the timestamp of the last button down is later than the last release. This avoids the bug fixed in synaptics commit xf86-input-synaptics-1.8.0-21-g37d34f0 (some application don't handle doubletap correctly without the timestamps). This works for double-tap immediately, for multi-tap we need to remember the timestamp of the first press event and use it for the release event so that there's a forced gap between the release and the second press. https://bugs.freedesktop.org/show_bug.cgi?id=89511 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-04-16 10:19:11 +10:00
</g>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<path d="M 60567.74 44377 L 60453.91 44548.69" fill="none" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 60451.01 44553.07 L 60451.96 44545.3 L 60453.91 44548.69 L 60457.79 44549.17 Z" fill="#000000" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 60411.08 44459.5 L 60398.38 44383.28" fill="none" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 60397.52 44378.1 L 60402.12 44384.43 L 60398.38 44383.28 L 60395.22 44385.58 Z" fill="#000000" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 60557.22 44575.5 L 60412.75 44382.1" fill="none" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 60409.61 44377.9 L 60416.6 44381.41 L 60412.75 44382.1 L 60410.99 44385.6 Z" fill="#000000" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 60289.54 44589 C 60292.34 44585.86 60296.32 44584.05 60300.52 44584 L 60334.49 44584 C 60338.69 44584.05 60342.67 44585.86 60345.47 44589 L 60365.45 44612 C 60366.01 44613.28 60366.01 44614.72 60365.45 44616 L 60345.47 44639 C 60342.67 44642.14 60338.69 44643.95 60334.49 44644 L 60300.52 44644 C 60296.32 44643.95 60292.34 44642.14 60289.54 44639 L 60269.56 44616 C 60269 44614.72 60269 44613.28 60269.56 44612 L 60289.54 44589 Z" fill="#7ea6e0" stroke="#000000" stroke-width="2" stroke-miterlimit="10" pointer-events="none"/>
touchpad: introduce MULTITAP for multi-tap-and-drag Once we have a doubletap, enter a loop in the state machine where we can tap multiple times and either get a multi-click or a multi-click drag-and-drop. The sequence down/up down/up down/up produces a triple-click. The sequence down/up down/up down/up down produces a triple-click with a button down for dragging. Yes, that glorious octuple-tap-and-drag, it is now possible. World domination has been achieved, thank you for playing. We don't know when we finish tapping now, so add a timeout to send the last click event once the finger has been released for the last time. This guarantees that the timestamp of the last button down is later than the last release. This avoids the bug fixed in synaptics commit xf86-input-synaptics-1.8.0-21-g37d34f0 (some application don't handle doubletap correctly without the timestamps). This works for double-tap immediately, for multi-tap we need to remember the timestamp of the first press event and use it for the release event so that there's a forced gap between the release and the second press. https://bugs.freedesktop.org/show_bug.cgi?id=89511 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-04-16 10:19:11 +10:00
<g fill="#000000" font-family="Helvetica" text-anchor="middle" font-size="12px">
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<text x="60317.25" y="44610.75">
touchpad: end tap-and-drag with an extra tap Currently for the tap-and-drag gesture to end user has to wait for a timeout to expire. Make it possible to end the drag gesture by just tapping. The allowed finger sequences to start and end a drag are thus: tap, down, .... move ...., up <wait for timeout> tap, down, .... move ...., up, tap https://bugs.freedesktop.org/show_bug.cgi?id=90255 Signed-off-by: Velimir Lisec <lisec.velimir@gmail.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> State diagram changes and a doc change squashed in. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-04-30 00:13:51 +02:00
second</text>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<text x="60317.25" y="44624.75">
touchpad: end tap-and-drag with an extra tap Currently for the tap-and-drag gesture to end user has to wait for a timeout to expire. Make it possible to end the drag gesture by just tapping. The allowed finger sequences to start and end a drag are thus: tap, down, .... move ...., up <wait for timeout> tap, down, .... move ...., up, tap https://bugs.freedesktop.org/show_bug.cgi?id=90255 Signed-off-by: Velimir Lisec <lisec.velimir@gmail.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> State diagram changes and a doc change squashed in. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-04-30 00:13:51 +02:00
finger down</text>
touchpad: introduce MULTITAP for multi-tap-and-drag Once we have a doubletap, enter a loop in the state machine where we can tap multiple times and either get a multi-click or a multi-click drag-and-drop. The sequence down/up down/up down/up produces a triple-click. The sequence down/up down/up down/up down produces a triple-click with a button down for dragging. Yes, that glorious octuple-tap-and-drag, it is now possible. World domination has been achieved, thank you for playing. We don't know when we finish tapping now, so add a timeout to send the last click event once the finger has been released for the last time. This guarantees that the timestamp of the last button down is later than the last release. This avoids the bug fixed in synaptics commit xf86-input-synaptics-1.8.0-21-g37d34f0 (some application don't handle doubletap correctly without the timestamps). This works for double-tap immediately, for multi-tap we need to remember the timestamp of the first press event and use it for the release event so that there's a forced gap between the release and the second press. https://bugs.freedesktop.org/show_bug.cgi?id=89511 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-04-16 10:19:11 +10:00
</g>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<path d="M 60388.05 44377 L 60328.25 44577.9" fill="none" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 60326.75 44582.93 L 60325.39 44575.22 L 60328.25 44577.9 L 60332.1 44577.22 Z" fill="#000000" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 60478.35 44664.5 L 60572.31 44383.04" fill="none" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 60573.97 44378.06 L 60575.07 44385.81 L 60572.31 44383.04 L 60568.43 44383.59 Z" fill="#000000" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 60418 44899.15 L 60527.91 44865.85" fill="none" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 60532.93 44864.32 L 60527.25 44869.7 L 60527.91 44865.85 L 60525.22 44863 Z" fill="#000000" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 60666.54 44467 C 60669.34 44463.86 60673.32 44462.05 60677.52 44462 L 60711.49 44462 C 60715.69 44462.05 60719.67 44463.86 60722.47 44467 L 60742.45 44490 C 60743.01 44491.28 60743.01 44492.72 60742.45 44494 L 60722.47 44517 C 60719.67 44520.14 60715.69 44521.95 60711.49 44522 L 60677.52 44522 C 60673.32 44521.95 60669.34 44520.14 60666.54 44517 L 60646.56 44494 C 60646 44492.72 60646 44491.28 60646.56 44490 L 60666.54 44467 Z" fill="#ffb570" stroke="#000000" stroke-width="2" stroke-miterlimit="10" pointer-events="none"/>
touchpad: introduce MULTITAP for multi-tap-and-drag Once we have a doubletap, enter a loop in the state machine where we can tap multiple times and either get a multi-click or a multi-click drag-and-drop. The sequence down/up down/up down/up produces a triple-click. The sequence down/up down/up down/up down produces a triple-click with a button down for dragging. Yes, that glorious octuple-tap-and-drag, it is now possible. World domination has been achieved, thank you for playing. We don't know when we finish tapping now, so add a timeout to send the last click event once the finger has been released for the last time. This guarantees that the timestamp of the last button down is later than the last release. This avoids the bug fixed in synaptics commit xf86-input-synaptics-1.8.0-21-g37d34f0 (some application don't handle doubletap correctly without the timestamps). This works for double-tap immediately, for multi-tap we need to remember the timestamp of the first press event and use it for the release event so that there's a forced gap between the release and the second press. https://bugs.freedesktop.org/show_bug.cgi?id=89511 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-04-16 10:19:11 +10:00
<g fill="#000000" font-family="Helvetica" text-anchor="middle" font-size="12px">
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<text x="60694.25" y="44488.75">
touchpad: end tap-and-drag with an extra tap Currently for the tap-and-drag gesture to end user has to wait for a timeout to expire. Make it possible to end the drag gesture by just tapping. The allowed finger sequences to start and end a drag are thus: tap, down, .... move ...., up <wait for timeout> tap, down, .... move ...., up, tap https://bugs.freedesktop.org/show_bug.cgi?id=90255 Signed-off-by: Velimir Lisec <lisec.velimir@gmail.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> State diagram changes and a doc change squashed in. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-04-30 00:13:51 +02:00
third</text>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<text x="60694.25" y="44502.75">
touchpad: end tap-and-drag with an extra tap Currently for the tap-and-drag gesture to end user has to wait for a timeout to expire. Make it possible to end the drag gesture by just tapping. The allowed finger sequences to start and end a drag are thus: tap, down, .... move ...., up <wait for timeout> tap, down, .... move ...., up, tap https://bugs.freedesktop.org/show_bug.cgi?id=90255 Signed-off-by: Velimir Lisec <lisec.velimir@gmail.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> State diagram changes and a doc change squashed in. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-04-30 00:13:51 +02:00
finger down</text>
touchpad: introduce MULTITAP for multi-tap-and-drag Once we have a doubletap, enter a loop in the state machine where we can tap multiple times and either get a multi-click or a multi-click drag-and-drop. The sequence down/up down/up down/up produces a triple-click. The sequence down/up down/up down/up down produces a triple-click with a button down for dragging. Yes, that glorious octuple-tap-and-drag, it is now possible. World domination has been achieved, thank you for playing. We don't know when we finish tapping now, so add a timeout to send the last click event once the finger has been released for the last time. This guarantees that the timestamp of the last button down is later than the last release. This avoids the bug fixed in synaptics commit xf86-input-synaptics-1.8.0-21-g37d34f0 (some application don't handle doubletap correctly without the timestamps). This works for double-tap immediately, for multi-tap we need to remember the timestamp of the first press event and use it for the release event so that there's a forced gap between the release and the second press. https://bugs.freedesktop.org/show_bug.cgi?id=89511 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-04-16 10:19:11 +10:00
</g>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<path d="M 60597.81 44377 L 60665.18 44457.13" fill="none" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 60668.56 44461.14 L 60661.37 44458.04 L 60665.18 44457.13 L 60666.73 44453.53 Z" fill="#000000" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 60849.72 44951.1 C 60850.86 44947.9 60852.72 44946.04 60854.68 44946.12 L 60923.14 44946.12 C 60924.7 44946.08 60926.2 44946.63 60927.17 44947.61 C 60928.15 44948.59 60928.49 44949.88 60928.1 44951.1 L 60909.25 45000.9 C 60908.11 45004.1 60906.25 45005.96 60904.29 45005.88 L 60834.84 45005.88 C 60833.45 45005.69 60832.23 45005.05 60831.47 45004.1 C 60830.72 45003.15 60830.5 45001.99 60830.87 45000.9 Z" fill="#ff6666" stroke="#000000" stroke-width="2" stroke-miterlimit="10" pointer-events="none"/>
touchpad: introduce MULTITAP for multi-tap-and-drag Once we have a doubletap, enter a loop in the state machine where we can tap multiple times and either get a multi-click or a multi-click drag-and-drop. The sequence down/up down/up down/up produces a triple-click. The sequence down/up down/up down/up down produces a triple-click with a button down for dragging. Yes, that glorious octuple-tap-and-drag, it is now possible. World domination has been achieved, thank you for playing. We don't know when we finish tapping now, so add a timeout to send the last click event once the finger has been released for the last time. This guarantees that the timestamp of the last button down is later than the last release. This avoids the bug fixed in synaptics commit xf86-input-synaptics-1.8.0-21-g37d34f0 (some application don't handle doubletap correctly without the timestamps). This works for double-tap immediately, for multi-tap we need to remember the timestamp of the first press event and use it for the release event so that there's a forced gap between the release and the second press. https://bugs.freedesktop.org/show_bug.cgi?id=89511 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-04-16 10:19:11 +10:00
<g fill="#000000" font-family="Helvetica" text-anchor="middle" font-size="12px">
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<text x="60879.25" y="44972.75">
touchpad: end tap-and-drag with an extra tap Currently for the tap-and-drag gesture to end user has to wait for a timeout to expire. Make it possible to end the drag gesture by just tapping. The allowed finger sequences to start and end a drag are thus: tap, down, .... move ...., up <wait for timeout> tap, down, .... move ...., up, tap https://bugs.freedesktop.org/show_bug.cgi?id=90255 Signed-off-by: Velimir Lisec <lisec.velimir@gmail.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> State diagram changes and a doc change squashed in. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-04-30 00:13:51 +02:00
btn1</text>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<text x="60879.25" y="44986.75">
touchpad: end tap-and-drag with an extra tap Currently for the tap-and-drag gesture to end user has to wait for a timeout to expire. Make it possible to end the drag gesture by just tapping. The allowed finger sequences to start and end a drag are thus: tap, down, .... move ...., up <wait for timeout> tap, down, .... move ...., up, tap https://bugs.freedesktop.org/show_bug.cgi?id=90255 Signed-off-by: Velimir Lisec <lisec.velimir@gmail.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> State diagram changes and a doc change squashed in. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-04-30 00:13:51 +02:00
release</text>
touchpad: introduce MULTITAP for multi-tap-and-drag Once we have a doubletap, enter a loop in the state machine where we can tap multiple times and either get a multi-click or a multi-click drag-and-drop. The sequence down/up down/up down/up produces a triple-click. The sequence down/up down/up down/up down produces a triple-click with a button down for dragging. Yes, that glorious octuple-tap-and-drag, it is now possible. World domination has been achieved, thank you for playing. We don't know when we finish tapping now, so add a timeout to send the last click event once the finger has been released for the last time. This guarantees that the timestamp of the last button down is later than the last release. This avoids the bug fixed in synaptics commit xf86-input-synaptics-1.8.0-21-g37d34f0 (some application don't handle doubletap correctly without the timestamps). This works for double-tap immediately, for multi-tap we need to remember the timestamp of the first press event and use it for the release event so that there's a forced gap between the release and the second press. https://bugs.freedesktop.org/show_bug.cgi?id=89511 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-04-16 10:19:11 +10:00
</g>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<path d="M 60891.99 45006 L 61025.23 45326.12" fill="none" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 61027.25 45330.97 L 61021.32 45325.85 L 61025.23 45326.12 L 61027.79 45323.16 Z" fill="#000000" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 62141.54 43682 C 62144.34 43678.86 62148.32 43677.05 62152.52 43677 L 62186.49 43677 C 62190.69 43677.05 62194.67 43678.86 62197.47 43682 L 62217.45 43705 C 62218.01 43706.28 62218.01 43707.72 62217.45 43709 L 62197.47 43732 C 62194.67 43735.14 62190.69 43736.95 62186.49 43737 L 62152.52 43737 C 62148.32 43736.95 62144.34 43735.14 62141.54 43732 L 62121.56 43709 C 62121 43707.72 62121 43706.28 62121.56 43705 L 62141.54 43682 Z" fill="#000000" stroke="#ffffff" stroke-width="2" stroke-miterlimit="10" pointer-events="none"/>
touchpad: disable tapping for fingers exceeding the timeout/motion threshold The current code triggers multi-finger tapping even if the finger released was previously held on the touchpad for a while. For an event sequence of: 1. first finger down 2. first finger move past threshold/wait past timeout 3. second finger down 4. first finger up The second finger initiates the two-finger tap state, but the button event is sent when the first finger releases - despite that finger not meeting the usual tap constraints. This sequence can happen whenever a user swaps fingers. Add the finger state to the actual touchpoints and update them whenever the constrains are broken. Then, discard button events if the respective touch did not meet the conditions. http://bugs.freedesktop.org/76760 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2014-06-20 14:16:13 +10:00
<g fill="#FFFFFF" font-family="Helvetica" text-anchor="middle" font-size="12px">
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<text x="62169.25" y="43696.75">
touchpad: end tap-and-drag with an extra tap Currently for the tap-and-drag gesture to end user has to wait for a timeout to expire. Make it possible to end the drag gesture by just tapping. The allowed finger sequences to start and end a drag are thus: tap, down, .... move ...., up <wait for timeout> tap, down, .... move ...., up, tap https://bugs.freedesktop.org/show_bug.cgi?id=90255 Signed-off-by: Velimir Lisec <lisec.velimir@gmail.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> State diagram changes and a doc change squashed in. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-04-30 00:13:51 +02:00
phys</text>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<text x="62169.25" y="43710.75">
touchpad: end tap-and-drag with an extra tap Currently for the tap-and-drag gesture to end user has to wait for a timeout to expire. Make it possible to end the drag gesture by just tapping. The allowed finger sequences to start and end a drag are thus: tap, down, .... move ...., up <wait for timeout> tap, down, .... move ...., up, tap https://bugs.freedesktop.org/show_bug.cgi?id=90255 Signed-off-by: Velimir Lisec <lisec.velimir@gmail.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> State diagram changes and a doc change squashed in. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-04-30 00:13:51 +02:00
button</text>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<text x="62169.25" y="43724.75">
touchpad: end tap-and-drag with an extra tap Currently for the tap-and-drag gesture to end user has to wait for a timeout to expire. Make it possible to end the drag gesture by just tapping. The allowed finger sequences to start and end a drag are thus: tap, down, .... move ...., up <wait for timeout> tap, down, .... move ...., up, tap https://bugs.freedesktop.org/show_bug.cgi?id=90255 Signed-off-by: Velimir Lisec <lisec.velimir@gmail.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> State diagram changes and a doc change squashed in. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-04-30 00:13:51 +02:00
press</text>
touchpad: introduce MULTITAP for multi-tap-and-drag Once we have a doubletap, enter a loop in the state machine where we can tap multiple times and either get a multi-click or a multi-click drag-and-drop. The sequence down/up down/up down/up produces a triple-click. The sequence down/up down/up down/up down produces a triple-click with a button down for dragging. Yes, that glorious octuple-tap-and-drag, it is now possible. World domination has been achieved, thank you for playing. We don't know when we finish tapping now, so add a timeout to send the last click event once the finger has been released for the last time. This guarantees that the timestamp of the last button down is later than the last release. This avoids the bug fixed in synaptics commit xf86-input-synaptics-1.8.0-21-g37d34f0 (some application don't handle doubletap correctly without the timestamps). This works for double-tap immediately, for multi-tap we need to remember the timestamp of the first press event and use it for the release event so that there's a forced gap between the release and the second press. https://bugs.freedesktop.org/show_bug.cgi?id=89511 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-04-16 10:19:11 +10:00
</g>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<path d="M 61492.42 43467 L 62115 43687.68" fill="none" stroke="#000000" stroke-miterlimit="10" stroke-dasharray="3 3" pointer-events="none"/>
<path d="M 62119.95 43689.43 L 62112.18 43690.4 L 62115 43687.68 L 62114.52 43683.8 Z" fill="#000000" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 61446 43716.18 L 62114.63 43707.7" fill="none" stroke="#000000" stroke-miterlimit="10" stroke-dasharray="3 3" pointer-events="none"/>
<path d="M 62119.88 43707.63 L 62112.93 43711.22 L 62114.63 43707.7 L 62112.84 43704.22 Z" fill="#000000" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 61805.27 43967 L 62122.29 43740.7" fill="none" stroke="#000000" stroke-miterlimit="10" stroke-dasharray="3 3" pointer-events="none"/>
<path d="M 62126.56 43737.65 L 62122.9 43744.57 L 62122.29 43740.7 L 62118.83 43738.87 Z" fill="#000000" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 61525.42 45074 L 62152.65 43742.76" fill="none" stroke="#000000" stroke-miterlimit="10" stroke-dasharray="3 3" pointer-events="none"/>
<path d="M 62154.89 43738.01 L 62155.07 43745.84 L 62152.65 43742.76 L 62148.74 43742.85 Z" fill="#000000" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 62169 44860.5 L 62169 45342 Q 62169 45352 62159 45352 L 61107.37 45352" fill="none" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 61102.12 45352 L 61109.12 45348.5 L 61107.37 45352 L 61109.12 45355.5 Z" fill="#000000" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 61263.2 42912 L 62130.51 43672.8" fill="none" stroke="#000000" stroke-miterlimit="10" stroke-dasharray="3 3" pointer-events="none"/>
<path d="M 62134.46 43676.26 L 62126.89 43674.28 L 62130.51 43672.8 L 62131.51 43669.02 Z" fill="#000000" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 59941.54 44052 C 59944.34 44048.86 59948.32 44047.05 59952.52 44047 L 59986.49 44047 C 59990.69 44047.05 59994.67 44048.86 59997.47 44052 L 60017.45 44075 C 60018.01 44076.28 60018.01 44077.72 60017.45 44079 L 59997.47 44102 C 59994.67 44105.14 59990.69 44106.95 59986.49 44107 L 59952.52 44107 C 59948.32 44106.95 59944.34 44105.14 59941.54 44102 L 59921.56 44079 C 59921 44077.72 59921 44076.28 59921.56 44075 L 59941.54 44052 Z" fill="#000000" stroke="#ffffff" stroke-width="2" stroke-miterlimit="10" pointer-events="none"/>
touchpad: disable tapping for fingers exceeding the timeout/motion threshold The current code triggers multi-finger tapping even if the finger released was previously held on the touchpad for a while. For an event sequence of: 1. first finger down 2. first finger move past threshold/wait past timeout 3. second finger down 4. first finger up The second finger initiates the two-finger tap state, but the button event is sent when the first finger releases - despite that finger not meeting the usual tap constraints. This sequence can happen whenever a user swaps fingers. Add the finger state to the actual touchpoints and update them whenever the constrains are broken. Then, discard button events if the respective touch did not meet the conditions. http://bugs.freedesktop.org/76760 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2014-06-20 14:16:13 +10:00
<g fill="#FFFFFF" font-family="Helvetica" text-anchor="middle" font-size="12px">
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<text x="59969.25" y="44066.75">
touchpad: end tap-and-drag with an extra tap Currently for the tap-and-drag gesture to end user has to wait for a timeout to expire. Make it possible to end the drag gesture by just tapping. The allowed finger sequences to start and end a drag are thus: tap, down, .... move ...., up <wait for timeout> tap, down, .... move ...., up, tap https://bugs.freedesktop.org/show_bug.cgi?id=90255 Signed-off-by: Velimir Lisec <lisec.velimir@gmail.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> State diagram changes and a doc change squashed in. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-04-30 00:13:51 +02:00
phys</text>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<text x="59969.25" y="44080.75">
touchpad: end tap-and-drag with an extra tap Currently for the tap-and-drag gesture to end user has to wait for a timeout to expire. Make it possible to end the drag gesture by just tapping. The allowed finger sequences to start and end a drag are thus: tap, down, .... move ...., up <wait for timeout> tap, down, .... move ...., up, tap https://bugs.freedesktop.org/show_bug.cgi?id=90255 Signed-off-by: Velimir Lisec <lisec.velimir@gmail.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> State diagram changes and a doc change squashed in. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-04-30 00:13:51 +02:00
button</text>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<text x="59969.25" y="44094.75">
touchpad: end tap-and-drag with an extra tap Currently for the tap-and-drag gesture to end user has to wait for a timeout to expire. Make it possible to end the drag gesture by just tapping. The allowed finger sequences to start and end a drag are thus: tap, down, .... move ...., up <wait for timeout> tap, down, .... move ...., up, tap https://bugs.freedesktop.org/show_bug.cgi?id=90255 Signed-off-by: Velimir Lisec <lisec.velimir@gmail.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> State diagram changes and a doc change squashed in. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-04-30 00:13:51 +02:00
press</text>
touchpad: introduce MULTITAP for multi-tap-and-drag Once we have a doubletap, enter a loop in the state machine where we can tap multiple times and either get a multi-click or a multi-click drag-and-drop. The sequence down/up down/up down/up produces a triple-click. The sequence down/up down/up down/up down produces a triple-click with a button down for dragging. Yes, that glorious octuple-tap-and-drag, it is now possible. World domination has been achieved, thank you for playing. We don't know when we finish tapping now, so add a timeout to send the last click event once the finger has been released for the last time. This guarantees that the timestamp of the last button down is later than the last release. This avoids the bug fixed in synaptics commit xf86-input-synaptics-1.8.0-21-g37d34f0 (some application don't handle doubletap correctly without the timestamps). This works for double-tap immediately, for multi-tap we need to remember the timestamp of the first press event and use it for the release event so that there's a forced gap between the release and the second press. https://bugs.freedesktop.org/show_bug.cgi?id=89511 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-04-16 10:19:11 +10:00
</g>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<path d="M 60682.19 43785 L 60023.89 44054.71" fill="none" stroke="#000000" stroke-miterlimit="10" stroke-dasharray="3 3" pointer-events="none"/>
<path d="M 60019.03 44056.7 L 60024.18 44050.81 L 60023.89 44054.71 L 60026.84 44057.29 Z" fill="#000000" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 59740.22 44967.1 C 59741.36 44963.9 59743.22 44962.04 59745.18 44962.12 L 59813.64 44962.12 C 59815.2 44962.08 59816.7 44962.63 59817.67 44963.61 C 59818.65 44964.59 59818.99 44965.88 59818.6 44967.1 L 59799.75 45016.9 C 59798.61 45020.1 59796.75 45021.96 59794.79 45021.88 L 59725.34 45021.88 C 59723.95 45021.69 59722.73 45021.05 59721.97 45020.1 C 59721.22 45019.15 59721 45017.99 59721.37 45016.9 Z" fill="#ff6666" stroke="#000000" stroke-width="2" stroke-miterlimit="10" pointer-events="none"/>
touchpad: introduce MULTITAP for multi-tap-and-drag Once we have a doubletap, enter a loop in the state machine where we can tap multiple times and either get a multi-click or a multi-click drag-and-drop. The sequence down/up down/up down/up produces a triple-click. The sequence down/up down/up down/up down produces a triple-click with a button down for dragging. Yes, that glorious octuple-tap-and-drag, it is now possible. World domination has been achieved, thank you for playing. We don't know when we finish tapping now, so add a timeout to send the last click event once the finger has been released for the last time. This guarantees that the timestamp of the last button down is later than the last release. This avoids the bug fixed in synaptics commit xf86-input-synaptics-1.8.0-21-g37d34f0 (some application don't handle doubletap correctly without the timestamps). This works for double-tap immediately, for multi-tap we need to remember the timestamp of the first press event and use it for the release event so that there's a forced gap between the release and the second press. https://bugs.freedesktop.org/show_bug.cgi?id=89511 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-04-16 10:19:11 +10:00
<g fill="#000000" font-family="Helvetica" text-anchor="middle" font-size="12px">
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<text x="59769.75" y="44988.75">
touchpad: end tap-and-drag with an extra tap Currently for the tap-and-drag gesture to end user has to wait for a timeout to expire. Make it possible to end the drag gesture by just tapping. The allowed finger sequences to start and end a drag are thus: tap, down, .... move ...., up <wait for timeout> tap, down, .... move ...., up, tap https://bugs.freedesktop.org/show_bug.cgi?id=90255 Signed-off-by: Velimir Lisec <lisec.velimir@gmail.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> State diagram changes and a doc change squashed in. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-04-30 00:13:51 +02:00
button 1</text>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<text x="59769.75" y="45002.75">
touchpad: end tap-and-drag with an extra tap Currently for the tap-and-drag gesture to end user has to wait for a timeout to expire. Make it possible to end the drag gesture by just tapping. The allowed finger sequences to start and end a drag are thus: tap, down, .... move ...., up <wait for timeout> tap, down, .... move ...., up, tap https://bugs.freedesktop.org/show_bug.cgi?id=90255 Signed-off-by: Velimir Lisec <lisec.velimir@gmail.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> State diagram changes and a doc change squashed in. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-04-30 00:13:51 +02:00
release</text>
touchpad: introduce MULTITAP for multi-tap-and-drag Once we have a doubletap, enter a loop in the state machine where we can tap multiple times and either get a multi-click or a multi-click drag-and-drop. The sequence down/up down/up down/up produces a triple-click. The sequence down/up down/up down/up down produces a triple-click with a button down for dragging. Yes, that glorious octuple-tap-and-drag, it is now possible. World domination has been achieved, thank you for playing. We don't know when we finish tapping now, so add a timeout to send the last click event once the finger has been released for the last time. This guarantees that the timestamp of the last button down is later than the last release. This avoids the bug fixed in synaptics commit xf86-input-synaptics-1.8.0-21-g37d34f0 (some application don't handle doubletap correctly without the timestamps). This works for double-tap immediately, for multi-tap we need to remember the timestamp of the first press event and use it for the release event so that there's a forced gap between the release and the second press. https://bugs.freedesktop.org/show_bug.cgi?id=89511 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-04-16 10:19:11 +10:00
</g>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<path d="M 59962.96 44107 L 59777.9 44955.78" fill="none" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 59776.78 44960.91 L 59774.85 44953.32 L 59777.9 44955.78 L 59781.69 44954.81 Z" fill="#000000" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 60569.5 45130.72 L 60988.08 45329.27" fill="none" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 60992.83 45331.52 L 60985 45331.68 L 60988.08 45329.27 L 60988 45325.36 Z" fill="#000000" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 60569.5 44042.93 L 60024.36 44073.89" fill="none" stroke="#000000" stroke-miterlimit="10" stroke-dasharray="3 3" pointer-events="none"/>
<path d="M 60019.12 44074.18 L 60025.91 44070.29 L 60024.36 44073.89 L 60026.3 44077.28 Z" fill="#000000" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 60363.68 44337 L 60020.3 44110.51" fill="none" stroke="#000000" stroke-miterlimit="10" stroke-dasharray="3 3" pointer-events="none"/>
<path d="M 60015.92 44107.62 L 60023.69 44108.55 L 60020.3 44110.51 L 60019.83 44114.39 Z" fill="#000000" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 60537.32 44337 L 60023.79 44101.86" fill="none" stroke="#000000" stroke-miterlimit="10" stroke-dasharray="3 3" pointer-events="none"/>
<path d="M 60019.02 44099.67 L 60026.84 44099.41 L 60023.79 44101.86 L 60023.92 44105.77 Z" fill="#000000" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<rect x="60159.5" y="44779" width="130" height="40" rx="2.4" ry="2.4" fill="#ccffcc" stroke="#000000" stroke-width="2" pointer-events="none"/>
<g fill="#000000" font-family="Helvetica" text-anchor="middle" font-size="12px">
<text x="60224.25" y="44802.75">
touchpad: end tap-and-drag with an extra tap Currently for the tap-and-drag gesture to end user has to wait for a timeout to expire. Make it possible to end the drag gesture by just tapping. The allowed finger sequences to start and end a drag are thus: tap, down, .... move ...., up <wait for timeout> tap, down, .... move ...., up, tap https://bugs.freedesktop.org/show_bug.cgi?id=90255 Signed-off-by: Velimir Lisec <lisec.velimir@gmail.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> State diagram changes and a doc change squashed in. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-04-30 00:13:51 +02:00
DRAGGING_WAIT</text>
touchpad: introduce MULTITAP for multi-tap-and-drag Once we have a doubletap, enter a loop in the state machine where we can tap multiple times and either get a multi-click or a multi-click drag-and-drop. The sequence down/up down/up down/up produces a triple-click. The sequence down/up down/up down/up down produces a triple-click with a button down for dragging. Yes, that glorious octuple-tap-and-drag, it is now possible. World domination has been achieved, thank you for playing. We don't know when we finish tapping now, so add a timeout to send the last click event once the finger has been released for the last time. This guarantees that the timestamp of the last button down is later than the last release. This avoids the bug fixed in synaptics commit xf86-input-synaptics-1.8.0-21-g37d34f0 (some application don't handle doubletap correctly without the timestamps). This works for double-tap immediately, for multi-tap we need to remember the timestamp of the first press event and use it for the release event so that there's a forced gap between the release and the second press. https://bugs.freedesktop.org/show_bug.cgi?id=89511 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-04-16 10:19:11 +10:00
</g>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<path d="M 60223.04 44839 C 60225.84 44835.86 60229.82 44834.05 60234.02 44834 L 60267.99 44834 C 60272.19 44834.05 60276.17 44835.86 60278.97 44839 L 60298.95 44862 C 60299.51 44863.28 60299.51 44864.72 60298.95 44866 L 60278.97 44889 C 60276.17 44892.14 60272.19 44893.95 60267.99 44894 L 60234.02 44894 C 60229.82 44893.95 60225.84 44892.14 60223.04 44889 L 60203.06 44866 C 60202.5 44864.72 60202.5 44863.28 60203.06 44862 L 60223.04 44839 Z" fill="#99ffff" stroke="#000000" stroke-width="2" stroke-miterlimit="10" pointer-events="none"/>
touchpad: introduce MULTITAP for multi-tap-and-drag Once we have a doubletap, enter a loop in the state machine where we can tap multiple times and either get a multi-click or a multi-click drag-and-drop. The sequence down/up down/up down/up produces a triple-click. The sequence down/up down/up down/up down produces a triple-click with a button down for dragging. Yes, that glorious octuple-tap-and-drag, it is now possible. World domination has been achieved, thank you for playing. We don't know when we finish tapping now, so add a timeout to send the last click event once the finger has been released for the last time. This guarantees that the timestamp of the last button down is later than the last release. This avoids the bug fixed in synaptics commit xf86-input-synaptics-1.8.0-21-g37d34f0 (some application don't handle doubletap correctly without the timestamps). This works for double-tap immediately, for multi-tap we need to remember the timestamp of the first press event and use it for the release event so that there's a forced gap between the release and the second press. https://bugs.freedesktop.org/show_bug.cgi?id=89511 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-04-16 10:19:11 +10:00
<g fill="#000000" font-family="Helvetica" text-anchor="middle" font-size="12px">
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<text x="60250.75" y="44867.75">
touchpad: end tap-and-drag with an extra tap Currently for the tap-and-drag gesture to end user has to wait for a timeout to expire. Make it possible to end the drag gesture by just tapping. The allowed finger sequences to start and end a drag are thus: tap, down, .... move ...., up <wait for timeout> tap, down, .... move ...., up, tap https://bugs.freedesktop.org/show_bug.cgi?id=90255 Signed-off-by: Velimir Lisec <lisec.velimir@gmail.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> State diagram changes and a doc change squashed in. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-04-30 00:13:51 +02:00
timeout</text>
touchpad: introduce MULTITAP for multi-tap-and-drag Once we have a doubletap, enter a loop in the state machine where we can tap multiple times and either get a multi-click or a multi-click drag-and-drop. The sequence down/up down/up down/up produces a triple-click. The sequence down/up down/up down/up down produces a triple-click with a button down for dragging. Yes, that glorious octuple-tap-and-drag, it is now possible. World domination has been achieved, thank you for playing. We don't know when we finish tapping now, so add a timeout to send the last click event once the finger has been released for the last time. This guarantees that the timestamp of the last button down is later than the last release. This avoids the bug fixed in synaptics commit xf86-input-synaptics-1.8.0-21-g37d34f0 (some application don't handle doubletap correctly without the timestamps). This works for double-tap immediately, for multi-tap we need to remember the timestamp of the first press event and use it for the release event so that there's a forced gap between the release and the second press. https://bugs.freedesktop.org/show_bug.cgi?id=89511 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-04-16 10:19:11 +10:00
</g>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<path d="M 60206.57 44634.5 L 60220.65 44664.89" fill="none" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 60222.86 44669.65 L 60216.74 44664.78 L 60220.65 44664.89 L 60223.09 44661.83 Z" fill="#000000" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 60232.65 44819 L 60236.37 44828.1" fill="none" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 60238.35 44832.96 L 60232.46 44827.8 L 60236.37 44828.1 L 60238.95 44825.16 Z" fill="#000000" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 60299.5 44884.55 L 60314.14 44890.75" fill="none" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 60318.97 44892.8 L 60311.16 44893.29 L 60314.14 44890.75 L 60313.89 44886.85 Z" fill="#000000" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 60046.54 44786 C 60049.34 44782.86 60053.32 44781.05 60057.52 44781 L 60091.49 44781 C 60095.69 44781.05 60099.67 44782.86 60102.47 44786 L 60122.45 44809 C 60123.01 44810.28 60123.01 44811.72 60122.45 44813 L 60102.47 44836 C 60099.67 44839.14 60095.69 44840.95 60091.49 44841 L 60057.52 44841 C 60053.32 44840.95 60049.34 44839.14 60046.54 44836 L 60026.56 44813 C 60026 44811.72 60026 44810.28 60026.56 44809 L 60046.54 44786 Z" fill="#ffd966" stroke="#000000" stroke-width="2" stroke-miterlimit="10" pointer-events="none"/>
touchpad: introduce MULTITAP for multi-tap-and-drag Once we have a doubletap, enter a loop in the state machine where we can tap multiple times and either get a multi-click or a multi-click drag-and-drop. The sequence down/up down/up down/up produces a triple-click. The sequence down/up down/up down/up down produces a triple-click with a button down for dragging. Yes, that glorious octuple-tap-and-drag, it is now possible. World domination has been achieved, thank you for playing. We don't know when we finish tapping now, so add a timeout to send the last click event once the finger has been released for the last time. This guarantees that the timestamp of the last button down is later than the last release. This avoids the bug fixed in synaptics commit xf86-input-synaptics-1.8.0-21-g37d34f0 (some application don't handle doubletap correctly without the timestamps). This works for double-tap immediately, for multi-tap we need to remember the timestamp of the first press event and use it for the release event so that there's a forced gap between the release and the second press. https://bugs.freedesktop.org/show_bug.cgi?id=89511 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-04-16 10:19:11 +10:00
<g fill="#000000" font-family="Helvetica" text-anchor="middle" font-size="12px">
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<text x="60074.25" y="44807.75">
touchpad: end tap-and-drag with an extra tap Currently for the tap-and-drag gesture to end user has to wait for a timeout to expire. Make it possible to end the drag gesture by just tapping. The allowed finger sequences to start and end a drag are thus: tap, down, .... move ...., up <wait for timeout> tap, down, .... move ...., up, tap https://bugs.freedesktop.org/show_bug.cgi?id=90255 Signed-off-by: Velimir Lisec <lisec.velimir@gmail.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> State diagram changes and a doc change squashed in. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-04-30 00:13:51 +02:00
first</text>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<text x="60074.25" y="44821.75">
touchpad: end tap-and-drag with an extra tap Currently for the tap-and-drag gesture to end user has to wait for a timeout to expire. Make it possible to end the drag gesture by just tapping. The allowed finger sequences to start and end a drag are thus: tap, down, .... move ...., up <wait for timeout> tap, down, .... move ...., up, tap https://bugs.freedesktop.org/show_bug.cgi?id=90255 Signed-off-by: Velimir Lisec <lisec.velimir@gmail.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> State diagram changes and a doc change squashed in. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-04-30 00:13:51 +02:00
finger down</text>
touchpad: introduce MULTITAP for multi-tap-and-drag Once we have a doubletap, enter a loop in the state machine where we can tap multiple times and either get a multi-click or a multi-click drag-and-drop. The sequence down/up down/up down/up produces a triple-click. The sequence down/up down/up down/up down produces a triple-click with a button down for dragging. Yes, that glorious octuple-tap-and-drag, it is now possible. World domination has been achieved, thank you for playing. We don't know when we finish tapping now, so add a timeout to send the last click event once the finger has been released for the last time. This guarantees that the timestamp of the last button down is later than the last release. This avoids the bug fixed in synaptics commit xf86-input-synaptics-1.8.0-21-g37d34f0 (some application don't handle doubletap correctly without the timestamps). This works for double-tap immediately, for multi-tap we need to remember the timestamp of the first press event and use it for the release event so that there's a forced gap between the release and the second press. https://bugs.freedesktop.org/show_bug.cgi?id=89511 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-04-16 10:19:11 +10:00
</g>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<path d="M 60159.5 44804.2 L 60129.35 44806.61" fill="none" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 60124.11 44807.03 L 60130.81 44802.98 L 60129.35 44806.61 L 60131.37 44809.96 Z" fill="#000000" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 61181.5 43051.7 C 61197.62 43057.91 61215.38 43057.91 61231.5 43051.7 C 61247.62 43045.5 61265.38 43045.5 61281.5 43051.7 L 61281.5 43104.28 C 61265.38 43098.08 61247.62 43098.08 61231.5 43104.28 C 61215.38 43110.49 61197.62 43110.49 61181.5 43104.28 L 61181.5 43051.7 Z" fill="#ffd966" stroke="#000000" stroke-width="2" stroke-miterlimit="10" pointer-events="none"/>
touchpad: introduce MULTITAP for multi-tap-and-drag Once we have a doubletap, enter a loop in the state machine where we can tap multiple times and either get a multi-click or a multi-click drag-and-drop. The sequence down/up down/up down/up produces a triple-click. The sequence down/up down/up down/up down produces a triple-click with a button down for dragging. Yes, that glorious octuple-tap-and-drag, it is now possible. World domination has been achieved, thank you for playing. We don't know when we finish tapping now, so add a timeout to send the last click event once the finger has been released for the last time. This guarantees that the timestamp of the last button down is later than the last release. This avoids the bug fixed in synaptics commit xf86-input-synaptics-1.8.0-21-g37d34f0 (some application don't handle doubletap correctly without the timestamps). This works for double-tap immediately, for multi-tap we need to remember the timestamp of the first press event and use it for the release event so that there's a forced gap between the release and the second press. https://bugs.freedesktop.org/show_bug.cgi?id=89511 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-04-16 10:19:11 +10:00
<g fill="#000000" font-family="Helvetica" text-anchor="middle" font-size="12px">
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<text x="61231.25" y="43081.75">
touchpad: end tap-and-drag with an extra tap Currently for the tap-and-drag gesture to end user has to wait for a timeout to expire. Make it possible to end the drag gesture by just tapping. The allowed finger sequences to start and end a drag are thus: tap, down, .... move ...., up <wait for timeout> tap, down, .... move ...., up, tap https://bugs.freedesktop.org/show_bug.cgi?id=90255 Signed-off-by: Velimir Lisec <lisec.velimir@gmail.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> State diagram changes and a doc change squashed in. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-04-30 00:13:51 +02:00
TOUCH_TOUCH</text>
touchpad: introduce MULTITAP for multi-tap-and-drag Once we have a doubletap, enter a loop in the state machine where we can tap multiple times and either get a multi-click or a multi-click drag-and-drop. The sequence down/up down/up down/up produces a triple-click. The sequence down/up down/up down/up down produces a triple-click with a button down for dragging. Yes, that glorious octuple-tap-and-drag, it is now possible. World domination has been achieved, thank you for playing. We don't know when we finish tapping now, so add a timeout to send the last click event once the finger has been released for the last time. This guarantees that the timestamp of the last button down is later than the last release. This avoids the bug fixed in synaptics commit xf86-input-synaptics-1.8.0-21-g37d34f0 (some application don't handle doubletap correctly without the timestamps). This works for double-tap immediately, for multi-tap we need to remember the timestamp of the first press event and use it for the release event so that there's a forced gap between the release and the second press. https://bugs.freedesktop.org/show_bug.cgi?id=89511 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-04-16 10:19:11 +10:00
</g>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<path d="M 60674.5 43448.7 C 60690.62 43454.91 60708.38 43454.91 60724.5 43448.7 C 60740.62 43442.5 60758.38 43442.5 60774.5 43448.7 L 60774.5 43501.28 C 60758.38 43495.08 60740.62 43495.08 60724.5 43501.28 C 60708.38 43507.49 60690.62 43507.49 60674.5 43501.28 L 60674.5 43448.7 Z" fill="#ffd966" stroke="#000000" stroke-width="2" stroke-miterlimit="10" pointer-events="none"/>
touchpad: introduce MULTITAP for multi-tap-and-drag Once we have a doubletap, enter a loop in the state machine where we can tap multiple times and either get a multi-click or a multi-click drag-and-drop. The sequence down/up down/up down/up produces a triple-click. The sequence down/up down/up down/up down produces a triple-click with a button down for dragging. Yes, that glorious octuple-tap-and-drag, it is now possible. World domination has been achieved, thank you for playing. We don't know when we finish tapping now, so add a timeout to send the last click event once the finger has been released for the last time. This guarantees that the timestamp of the last button down is later than the last release. This avoids the bug fixed in synaptics commit xf86-input-synaptics-1.8.0-21-g37d34f0 (some application don't handle doubletap correctly without the timestamps). This works for double-tap immediately, for multi-tap we need to remember the timestamp of the first press event and use it for the release event so that there's a forced gap between the release and the second press. https://bugs.freedesktop.org/show_bug.cgi?id=89511 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-04-16 10:19:11 +10:00
<g fill="#000000" font-family="Helvetica" text-anchor="middle" font-size="12px">
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<text x="60724.25" y="43478.75">
touchpad: end tap-and-drag with an extra tap Currently for the tap-and-drag gesture to end user has to wait for a timeout to expire. Make it possible to end the drag gesture by just tapping. The allowed finger sequences to start and end a drag are thus: tap, down, .... move ...., up <wait for timeout> tap, down, .... move ...., up, tap https://bugs.freedesktop.org/show_bug.cgi?id=90255 Signed-off-by: Velimir Lisec <lisec.velimir@gmail.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> State diagram changes and a doc change squashed in. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-04-30 00:13:51 +02:00
TOUCH_IDLE</text>
touchpad: introduce MULTITAP for multi-tap-and-drag Once we have a doubletap, enter a loop in the state machine where we can tap multiple times and either get a multi-click or a multi-click drag-and-drop. The sequence down/up down/up down/up produces a triple-click. The sequence down/up down/up down/up down produces a triple-click with a button down for dragging. Yes, that glorious octuple-tap-and-drag, it is now possible. World domination has been achieved, thank you for playing. We don't know when we finish tapping now, so add a timeout to send the last click event once the finger has been released for the last time. This guarantees that the timestamp of the last button down is later than the last release. This avoids the bug fixed in synaptics commit xf86-input-synaptics-1.8.0-21-g37d34f0 (some application don't handle doubletap correctly without the timestamps). This works for double-tap immediately, for multi-tap we need to remember the timestamp of the first press event and use it for the release event so that there's a forced gap between the release and the second press. https://bugs.freedesktop.org/show_bug.cgi?id=89511 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-04-16 10:19:11 +10:00
</g>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<path d="M 60925.93 43312 L 60769.61 43438.49" fill="none" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 60765.53 43441.8 L 60768.77 43434.67 L 60769.61 43438.49 L 60773.17 43440.11 Z" fill="#000000" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 60724.64 43507.5 L 60724.84 43553.63" fill="none" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 60724.86 43558.88 L 60721.33 43551.9 L 60724.84 43553.63 L 60728.33 43551.87 Z" fill="#000000" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 61232.53 43012 L 61232.11 43039.13" fill="none" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 61232.03 43044.38 L 61228.64 43037.33 L 61232.11 43039.13 L 61235.63 43037.44 Z" fill="#000000" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 61233.24 43110.5 L 61234.59 43135.64" fill="none" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 61234.87 43140.88 L 61231 43134.08 L 61234.59 43135.64 L 61237.99 43133.71 Z" fill="#000000" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 61378.5 43351.7 C 61394.62 43357.91 61412.38 43357.91 61428.5 43351.7 C 61444.62 43345.5 61462.38 43345.5 61478.5 43351.7 L 61478.5 43404.28 C 61462.38 43398.08 61444.62 43398.08 61428.5 43404.28 C 61412.38 43410.49 61394.62 43410.49 61378.5 43404.28 L 61378.5 43351.7 Z" fill="#ffd966" stroke="#000000" stroke-width="2" stroke-miterlimit="10" pointer-events="none"/>
<g fill="#000000" font-family="Helvetica" text-anchor="middle" font-size="12px">
<text x="61428.25" y="43381.75">
touchpad: end tap-and-drag with an extra tap Currently for the tap-and-drag gesture to end user has to wait for a timeout to expire. Make it possible to end the drag gesture by just tapping. The allowed finger sequences to start and end a drag are thus: tap, down, .... move ...., up <wait for timeout> tap, down, .... move ...., up, tap https://bugs.freedesktop.org/show_bug.cgi?id=90255 Signed-off-by: Velimir Lisec <lisec.velimir@gmail.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> State diagram changes and a doc change squashed in. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-04-30 00:13:51 +02:00
TOUCH_DEAD</text>
touchpad: introduce MULTITAP for multi-tap-and-drag Once we have a doubletap, enter a loop in the state machine where we can tap multiple times and either get a multi-click or a multi-click drag-and-drop. The sequence down/up down/up down/up produces a triple-click. The sequence down/up down/up down/up down produces a triple-click with a button down for dragging. Yes, that glorious octuple-tap-and-drag, it is now possible. World domination has been achieved, thank you for playing. We don't know when we finish tapping now, so add a timeout to send the last click event once the finger has been released for the last time. This guarantees that the timestamp of the last button down is later than the last release. This avoids the bug fixed in synaptics commit xf86-input-synaptics-1.8.0-21-g37d34f0 (some application don't handle doubletap correctly without the timestamps). This works for double-tap immediately, for multi-tap we need to remember the timestamp of the first press event and use it for the release event so that there's a forced gap between the release and the second press. https://bugs.freedesktop.org/show_bug.cgi?id=89511 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-04-16 10:19:11 +10:00
</g>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<path d="M 61360.44 43312 L 61390.41 43341.07" fill="none" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 61394.18 43344.72 L 61386.72 43342.36 L 61390.41 43341.07 L 61391.59 43337.34 Z" fill="#000000" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 61484.88 43312 L 61460.4 43340.66" fill="none" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 61456.99 43344.65 L 61458.87 43337.05 L 61460.4 43340.66 L 61464.19 43341.6 Z" fill="#000000" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 61432.03 43410.5 L 61433.14 43420.67" fill="none" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 61433.71 43425.89 L 61429.47 43419.31 L 61433.14 43420.67 L 61436.43 43418.55 Z" fill="#000000" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 60947.8 43733 L 60946.41 43673.87" fill="none" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 60946.29 43668.62 L 60949.95 43675.53 L 60946.41 43673.87 L 60942.95 43675.7 Z" fill="#000000" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 61710.5 43798.7 C 61726.62 43804.91 61744.38 43804.91 61760.5 43798.7 C 61776.62 43792.5 61794.38 43792.5 61810.5 43798.7 L 61810.5 43851.28 C 61794.38 43845.08 61776.62 43845.08 61760.5 43851.28 C 61744.38 43857.49 61726.62 43857.49 61710.5 43851.28 L 61710.5 43798.7 Z" fill="#7ea6e0" stroke="#000000" stroke-width="2" stroke-miterlimit="10" pointer-events="none"/>
<g fill="#000000" font-family="Helvetica" text-anchor="middle" font-size="12px">
<text x="61760.25" y="43828.75">
touchpad: end tap-and-drag with an extra tap Currently for the tap-and-drag gesture to end user has to wait for a timeout to expire. Make it possible to end the drag gesture by just tapping. The allowed finger sequences to start and end a drag are thus: tap, down, .... move ...., up <wait for timeout> tap, down, .... move ...., up, tap https://bugs.freedesktop.org/show_bug.cgi?id=90255 Signed-off-by: Velimir Lisec <lisec.velimir@gmail.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> State diagram changes and a doc change squashed in. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-04-30 00:13:51 +02:00
TOUCH_DEAD</text>
touchpad: introduce MULTITAP for multi-tap-and-drag Once we have a doubletap, enter a loop in the state machine where we can tap multiple times and either get a multi-click or a multi-click drag-and-drop. The sequence down/up down/up down/up produces a triple-click. The sequence down/up down/up down/up down produces a triple-click with a button down for dragging. Yes, that glorious octuple-tap-and-drag, it is now possible. World domination has been achieved, thank you for playing. We don't know when we finish tapping now, so add a timeout to send the last click event once the finger has been released for the last time. This guarantees that the timestamp of the last button down is later than the last release. This avoids the bug fixed in synaptics commit xf86-input-synaptics-1.8.0-21-g37d34f0 (some application don't handle doubletap correctly without the timestamps). This works for double-tap immediately, for multi-tap we need to remember the timestamp of the first press event and use it for the release event so that there's a forced gap between the release and the second press. https://bugs.freedesktop.org/show_bug.cgi?id=89511 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-04-16 10:19:11 +10:00
</g>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<path d="M 61767.44 43922.5 L 61773.25 43960.7" fill="none" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 61774.04 43965.89 L 61769.53 43959.5 L 61773.25 43960.7 L 61776.45 43958.45 Z" fill="#000000" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 61678 43794.77 L 61704.52 43804.49" fill="none" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 61709.45 43806.29 L 61701.67 43807.17 L 61704.52 43804.49 L 61704.08 43800.6 Z" fill="#000000" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 61552 43834.74 L 61704.14 43827.63" fill="none" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 61709.38 43827.39 L 61702.55 43831.21 L 61704.14 43827.63 L 61702.23 43824.22 Z" fill="#000000" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 61861.5 43728.7 C 61877.62 43734.91 61895.38 43734.91 61911.5 43728.7 C 61927.62 43722.5 61945.38 43722.5 61961.5 43728.7 L 61961.5 43781.28 C 61945.38 43775.08 61927.62 43775.08 61911.5 43781.28 C 61895.38 43787.49 61877.62 43787.49 61861.5 43781.28 L 61861.5 43728.7 Z" fill="#7ea6e0" stroke="#000000" stroke-width="2" stroke-miterlimit="10" pointer-events="none"/>
touchpad: introduce MULTITAP for multi-tap-and-drag Once we have a doubletap, enter a loop in the state machine where we can tap multiple times and either get a multi-click or a multi-click drag-and-drop. The sequence down/up down/up down/up produces a triple-click. The sequence down/up down/up down/up down produces a triple-click with a button down for dragging. Yes, that glorious octuple-tap-and-drag, it is now possible. World domination has been achieved, thank you for playing. We don't know when we finish tapping now, so add a timeout to send the last click event once the finger has been released for the last time. This guarantees that the timestamp of the last button down is later than the last release. This avoids the bug fixed in synaptics commit xf86-input-synaptics-1.8.0-21-g37d34f0 (some application don't handle doubletap correctly without the timestamps). This works for double-tap immediately, for multi-tap we need to remember the timestamp of the first press event and use it for the release event so that there's a forced gap between the release and the second press. https://bugs.freedesktop.org/show_bug.cgi?id=89511 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-04-16 10:19:11 +10:00
<g fill="#000000" font-family="Helvetica" text-anchor="middle" font-size="12px">
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<text x="61911.25" y="43758.75">
touchpad: end tap-and-drag with an extra tap Currently for the tap-and-drag gesture to end user has to wait for a timeout to expire. Make it possible to end the drag gesture by just tapping. The allowed finger sequences to start and end a drag are thus: tap, down, .... move ...., up <wait for timeout> tap, down, .... move ...., up, tap https://bugs.freedesktop.org/show_bug.cgi?id=90255 Signed-off-by: Velimir Lisec <lisec.velimir@gmail.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> State diagram changes and a doc change squashed in. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-04-30 00:13:51 +02:00
TOUCH_IDLE</text>
touchpad: introduce MULTITAP for multi-tap-and-drag Once we have a doubletap, enter a loop in the state machine where we can tap multiple times and either get a multi-click or a multi-click drag-and-drop. The sequence down/up down/up down/up produces a triple-click. The sequence down/up down/up down/up down produces a triple-click with a button down for dragging. Yes, that glorious octuple-tap-and-drag, it is now possible. World domination has been achieved, thank you for playing. We don't know when we finish tapping now, so add a timeout to send the last click event once the finger has been released for the last time. This guarantees that the timestamp of the last button down is later than the last release. This avoids the bug fixed in synaptics commit xf86-input-synaptics-1.8.0-21-g37d34f0 (some application don't handle doubletap correctly without the timestamps). This works for double-tap immediately, for multi-tap we need to remember the timestamp of the first press event and use it for the release event so that there's a forced gap between the release and the second press. https://bugs.freedesktop.org/show_bug.cgi?id=89511 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-04-16 10:19:11 +10:00
</g>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<path d="M 61919.03 44067 L 61912.44 43793.87" fill="none" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 61912.31 43788.62 L 61915.98 43795.53 L 61912.44 43793.87 L 61908.98 43795.7 Z" fill="#000000" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 61338.5 43608.7 C 61354.62 43614.91 61372.38 43614.91 61388.5 43608.7 C 61404.62 43602.5 61422.38 43602.5 61438.5 43608.7 L 61438.5 43661.28 C 61422.38 43655.08 61404.62 43655.08 61388.5 43661.28 C 61372.38 43667.49 61354.62 43667.49 61338.5 43661.28 L 61338.5 43608.7 Z" fill="#7ea6e0" stroke="#000000" stroke-width="2" stroke-miterlimit="10" pointer-events="none"/>
touchpad: introduce MULTITAP for multi-tap-and-drag Once we have a doubletap, enter a loop in the state machine where we can tap multiple times and either get a multi-click or a multi-click drag-and-drop. The sequence down/up down/up down/up produces a triple-click. The sequence down/up down/up down/up down produces a triple-click with a button down for dragging. Yes, that glorious octuple-tap-and-drag, it is now possible. World domination has been achieved, thank you for playing. We don't know when we finish tapping now, so add a timeout to send the last click event once the finger has been released for the last time. This guarantees that the timestamp of the last button down is later than the last release. This avoids the bug fixed in synaptics commit xf86-input-synaptics-1.8.0-21-g37d34f0 (some application don't handle doubletap correctly without the timestamps). This works for double-tap immediately, for multi-tap we need to remember the timestamp of the first press event and use it for the release event so that there's a forced gap between the release and the second press. https://bugs.freedesktop.org/show_bug.cgi?id=89511 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-04-16 10:19:11 +10:00
<g fill="#000000" font-family="Helvetica" text-anchor="middle" font-size="12px">
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<text x="61388.25" y="43638.75">
touchpad: end tap-and-drag with an extra tap Currently for the tap-and-drag gesture to end user has to wait for a timeout to expire. Make it possible to end the drag gesture by just tapping. The allowed finger sequences to start and end a drag are thus: tap, down, .... move ...., up <wait for timeout> tap, down, .... move ...., up, tap https://bugs.freedesktop.org/show_bug.cgi?id=90255 Signed-off-by: Velimir Lisec <lisec.velimir@gmail.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> State diagram changes and a doc change squashed in. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-04-30 00:13:51 +02:00
TOUCH_TOUCH</text>
touchpad: introduce MULTITAP for multi-tap-and-drag Once we have a doubletap, enter a loop in the state machine where we can tap multiple times and either get a multi-click or a multi-click drag-and-drop. The sequence down/up down/up down/up produces a triple-click. The sequence down/up down/up down/up down produces a triple-click with a button down for dragging. Yes, that glorious octuple-tap-and-drag, it is now possible. World domination has been achieved, thank you for playing. We don't know when we finish tapping now, so add a timeout to send the last click event once the finger has been released for the last time. This guarantees that the timestamp of the last button down is later than the last release. This avoids the bug fixed in synaptics commit xf86-input-synaptics-1.8.0-21-g37d34f0 (some application don't handle doubletap correctly without the timestamps). This works for double-tap immediately, for multi-tap we need to remember the timestamp of the first press event and use it for the release event so that there's a forced gap between the release and the second press. https://bugs.freedesktop.org/show_bug.cgi?id=89511 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-04-16 10:19:11 +10:00
</g>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<path d="M 61400.36 43577 L 61396.42 43596.26" fill="none" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 61395.37 43601.4 L 61393.35 43593.85 L 61396.42 43596.26 L 61400.2 43595.25 Z" fill="#000000" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 61161.58 43312 L 61362.01 43597.29" fill="none" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 61365.02 43601.59 L 61358.14 43597.87 L 61362.01 43597.29 L 61363.86 43593.85 Z" fill="#000000" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 61105.5 43603.7 C 61121.62 43609.91 61139.38 43609.91 61155.5 43603.7 C 61171.62 43597.5 61189.38 43597.5 61205.5 43603.7 L 61205.5 43656.28 C 61189.38 43650.08 61171.62 43650.08 61155.5 43656.28 C 61139.38 43662.49 61121.62 43662.49 61105.5 43656.28 L 61105.5 43603.7 Z" fill="#7ea6e0" stroke="#000000" stroke-width="2" stroke-miterlimit="10" pointer-events="none"/>
touchpad: introduce MULTITAP for multi-tap-and-drag Once we have a doubletap, enter a loop in the state machine where we can tap multiple times and either get a multi-click or a multi-click drag-and-drop. The sequence down/up down/up down/up produces a triple-click. The sequence down/up down/up down/up down produces a triple-click with a button down for dragging. Yes, that glorious octuple-tap-and-drag, it is now possible. World domination has been achieved, thank you for playing. We don't know when we finish tapping now, so add a timeout to send the last click event once the finger has been released for the last time. This guarantees that the timestamp of the last button down is later than the last release. This avoids the bug fixed in synaptics commit xf86-input-synaptics-1.8.0-21-g37d34f0 (some application don't handle doubletap correctly without the timestamps). This works for double-tap immediately, for multi-tap we need to remember the timestamp of the first press event and use it for the release event so that there's a forced gap between the release and the second press. https://bugs.freedesktop.org/show_bug.cgi?id=89511 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-04-16 10:19:11 +10:00
<g fill="#000000" font-family="Helvetica" text-anchor="middle" font-size="12px">
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<text x="61155.25" y="43633.75">
touchpad: end tap-and-drag with an extra tap Currently for the tap-and-drag gesture to end user has to wait for a timeout to expire. Make it possible to end the drag gesture by just tapping. The allowed finger sequences to start and end a drag are thus: tap, down, .... move ...., up <wait for timeout> tap, down, .... move ...., up, tap https://bugs.freedesktop.org/show_bug.cgi?id=90255 Signed-off-by: Velimir Lisec <lisec.velimir@gmail.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> State diagram changes and a doc change squashed in. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-04-30 00:13:51 +02:00
TOUCH_IDLE</text>
touchpad: introduce MULTITAP for multi-tap-and-drag Once we have a doubletap, enter a loop in the state machine where we can tap multiple times and either get a multi-click or a multi-click drag-and-drop. The sequence down/up down/up down/up produces a triple-click. The sequence down/up down/up down/up down produces a triple-click with a button down for dragging. Yes, that glorious octuple-tap-and-drag, it is now possible. World domination has been achieved, thank you for playing. We don't know when we finish tapping now, so add a timeout to send the last click event once the finger has been released for the last time. This guarantees that the timestamp of the last button down is later than the last release. This avoids the bug fixed in synaptics commit xf86-input-synaptics-1.8.0-21-g37d34f0 (some application don't handle doubletap correctly without the timestamps). This works for double-tap immediately, for multi-tap we need to remember the timestamp of the first press event and use it for the release event so that there's a forced gap between the release and the second press. https://bugs.freedesktop.org/show_bug.cgi?id=89511 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-04-16 10:19:11 +10:00
</g>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<path d="M 61195.07 43763 L 61166.99 43668.6" fill="none" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 61165.49 43663.57 L 61170.84 43669.28 L 61166.99 43668.6 L 61164.13 43671.28 Z" fill="#000000" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 61502.5 43889.7 C 61518.62 43895.91 61536.38 43895.91 61552.5 43889.7 C 61568.62 43883.5 61586.38 43883.5 61602.5 43889.7 L 61602.5 43942.28 C 61586.38 43936.08 61568.62 43936.08 61552.5 43942.28 C 61536.38 43948.49 61518.62 43948.49 61502.5 43942.28 L 61502.5 43889.7 Z" fill="#ffd966" stroke="#000000" stroke-width="2" stroke-miterlimit="10" pointer-events="none"/>
touchpad: introduce MULTITAP for multi-tap-and-drag Once we have a doubletap, enter a loop in the state machine where we can tap multiple times and either get a multi-click or a multi-click drag-and-drop. The sequence down/up down/up down/up produces a triple-click. The sequence down/up down/up down/up down produces a triple-click with a button down for dragging. Yes, that glorious octuple-tap-and-drag, it is now possible. World domination has been achieved, thank you for playing. We don't know when we finish tapping now, so add a timeout to send the last click event once the finger has been released for the last time. This guarantees that the timestamp of the last button down is later than the last release. This avoids the bug fixed in synaptics commit xf86-input-synaptics-1.8.0-21-g37d34f0 (some application don't handle doubletap correctly without the timestamps). This works for double-tap immediately, for multi-tap we need to remember the timestamp of the first press event and use it for the release event so that there's a forced gap between the release and the second press. https://bugs.freedesktop.org/show_bug.cgi?id=89511 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-04-16 10:19:11 +10:00
<g fill="#000000" font-family="Helvetica" text-anchor="middle" font-size="12px">
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<text x="61552.25" y="43919.75">
touchpad: end tap-and-drag with an extra tap Currently for the tap-and-drag gesture to end user has to wait for a timeout to expire. Make it possible to end the drag gesture by just tapping. The allowed finger sequences to start and end a drag are thus: tap, down, .... move ...., up <wait for timeout> tap, down, .... move ...., up, tap https://bugs.freedesktop.org/show_bug.cgi?id=90255 Signed-off-by: Velimir Lisec <lisec.velimir@gmail.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> State diagram changes and a doc change squashed in. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-04-30 00:13:51 +02:00
TOUCH_IDLE</text>
touchpad: introduce MULTITAP for multi-tap-and-drag Once we have a doubletap, enter a loop in the state machine where we can tap multiple times and either get a multi-click or a multi-click drag-and-drop. The sequence down/up down/up down/up produces a triple-click. The sequence down/up down/up down/up down produces a triple-click with a button down for dragging. Yes, that glorious octuple-tap-and-drag, it is now possible. World domination has been achieved, thank you for playing. We don't know when we finish tapping now, so add a timeout to send the last click event once the finger has been released for the last time. This guarantees that the timestamp of the last button down is later than the last release. This avoids the bug fixed in synaptics commit xf86-input-synaptics-1.8.0-21-g37d34f0 (some application don't handle doubletap correctly without the timestamps). This works for double-tap immediately, for multi-tap we need to remember the timestamp of the first press event and use it for the release event so that there's a forced gap between the release and the second press. https://bugs.freedesktop.org/show_bug.cgi?id=89511 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-04-16 10:19:11 +10:00
</g>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<path d="M 61605.13 44072 L 61565.5 43954.53" fill="none" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 61563.82 43949.56 L 61569.38 43955.07 L 61565.5 43954.53 L 61562.74 43957.31 Z" fill="#000000" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 61485.5 44170.7 C 61501.62 44176.91 61519.38 44176.91 61535.5 44170.7 C 61551.62 44164.5 61569.38 44164.5 61585.5 44170.7 L 61585.5 44223.28 C 61569.38 44217.08 61551.62 44217.08 61535.5 44223.28 C 61519.38 44229.49 61501.62 44229.49 61485.5 44223.28 L 61485.5 44170.7 Z" fill="#ffb570" stroke="#000000" stroke-width="2" stroke-miterlimit="10" pointer-events="none"/>
touchpad: introduce MULTITAP for multi-tap-and-drag Once we have a doubletap, enter a loop in the state machine where we can tap multiple times and either get a multi-click or a multi-click drag-and-drop. The sequence down/up down/up down/up produces a triple-click. The sequence down/up down/up down/up down produces a triple-click with a button down for dragging. Yes, that glorious octuple-tap-and-drag, it is now possible. World domination has been achieved, thank you for playing. We don't know when we finish tapping now, so add a timeout to send the last click event once the finger has been released for the last time. This guarantees that the timestamp of the last button down is later than the last release. This avoids the bug fixed in synaptics commit xf86-input-synaptics-1.8.0-21-g37d34f0 (some application don't handle doubletap correctly without the timestamps). This works for double-tap immediately, for multi-tap we need to remember the timestamp of the first press event and use it for the release event so that there's a forced gap between the release and the second press. https://bugs.freedesktop.org/show_bug.cgi?id=89511 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-04-16 10:19:11 +10:00
<g fill="#000000" font-family="Helvetica" text-anchor="middle" font-size="12px">
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<text x="61535.25" y="44200.75">
touchpad: end tap-and-drag with an extra tap Currently for the tap-and-drag gesture to end user has to wait for a timeout to expire. Make it possible to end the drag gesture by just tapping. The allowed finger sequences to start and end a drag are thus: tap, down, .... move ...., up <wait for timeout> tap, down, .... move ...., up, tap https://bugs.freedesktop.org/show_bug.cgi?id=90255 Signed-off-by: Velimir Lisec <lisec.velimir@gmail.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> State diagram changes and a doc change squashed in. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-04-30 00:13:51 +02:00
TOUCH_TOUCH</text>
touchpad: introduce MULTITAP for multi-tap-and-drag Once we have a doubletap, enter a loop in the state machine where we can tap multiple times and either get a multi-click or a multi-click drag-and-drop. The sequence down/up down/up down/up produces a triple-click. The sequence down/up down/up down/up down produces a triple-click with a button down for dragging. Yes, that glorious octuple-tap-and-drag, it is now possible. World domination has been achieved, thank you for playing. We don't know when we finish tapping now, so add a timeout to send the last click event once the finger has been released for the last time. This guarantees that the timestamp of the last button down is later than the last release. This avoids the bug fixed in synaptics commit xf86-input-synaptics-1.8.0-21-g37d34f0 (some application don't handle doubletap correctly without the timestamps). This works for double-tap immediately, for multi-tap we need to remember the timestamp of the first press event and use it for the release event so that there's a forced gap between the release and the second press. https://bugs.freedesktop.org/show_bug.cgi?id=89511 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-04-16 10:19:11 +10:00
</g>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<path d="M 61712.25 44126.38 L 61591.41 44174.66" fill="none" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 61586.54 44176.61 L 61591.74 44170.76 L 61591.41 44174.66 L 61594.34 44177.26 Z" fill="#000000" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 61774.5 45175.7 C 61790.62 45181.91 61808.38 45181.91 61824.5 45175.7 C 61840.62 45169.5 61858.38 45169.5 61874.5 45175.7 L 61874.5 45228.28 C 61858.38 45222.08 61840.62 45222.08 61824.5 45228.28 C 61808.38 45234.49 61790.62 45234.49 61774.5 45228.28 L 61774.5 45175.7 Z" fill="#e1d5e7" stroke="#000000" stroke-width="2" stroke-miterlimit="10" pointer-events="none"/>
touchpad: introduce MULTITAP for multi-tap-and-drag Once we have a doubletap, enter a loop in the state machine where we can tap multiple times and either get a multi-click or a multi-click drag-and-drop. The sequence down/up down/up down/up produces a triple-click. The sequence down/up down/up down/up down produces a triple-click with a button down for dragging. Yes, that glorious octuple-tap-and-drag, it is now possible. World domination has been achieved, thank you for playing. We don't know when we finish tapping now, so add a timeout to send the last click event once the finger has been released for the last time. This guarantees that the timestamp of the last button down is later than the last release. This avoids the bug fixed in synaptics commit xf86-input-synaptics-1.8.0-21-g37d34f0 (some application don't handle doubletap correctly without the timestamps). This works for double-tap immediately, for multi-tap we need to remember the timestamp of the first press event and use it for the release event so that there's a forced gap between the release and the second press. https://bugs.freedesktop.org/show_bug.cgi?id=89511 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-04-16 10:19:11 +10:00
<g fill="#000000" font-family="Helvetica" text-anchor="middle" font-size="12px">
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<text x="61824.25" y="45198.75">
touchpad: end tap-and-drag with an extra tap Currently for the tap-and-drag gesture to end user has to wait for a timeout to expire. Make it possible to end the drag gesture by just tapping. The allowed finger sequences to start and end a drag are thus: tap, down, .... move ...., up <wait for timeout> tap, down, .... move ...., up, tap https://bugs.freedesktop.org/show_bug.cgi?id=90255 Signed-off-by: Velimir Lisec <lisec.velimir@gmail.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> State diagram changes and a doc change squashed in. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-04-30 00:13:51 +02:00
that finger</text>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<text x="61824.25" y="45212.75">
touchpad: end tap-and-drag with an extra tap Currently for the tap-and-drag gesture to end user has to wait for a timeout to expire. Make it possible to end the drag gesture by just tapping. The allowed finger sequences to start and end a drag are thus: tap, down, .... move ...., up <wait for timeout> tap, down, .... move ...., up, tap https://bugs.freedesktop.org/show_bug.cgi?id=90255 Signed-off-by: Velimir Lisec <lisec.velimir@gmail.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> State diagram changes and a doc change squashed in. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-04-30 00:13:51 +02:00
TOUCH_IDLE</text>
touchpad: introduce MULTITAP for multi-tap-and-drag Once we have a doubletap, enter a loop in the state machine where we can tap multiple times and either get a multi-click or a multi-click drag-and-drop. The sequence down/up down/up down/up produces a triple-click. The sequence down/up down/up down/up down produces a triple-click with a button down for dragging. Yes, that glorious octuple-tap-and-drag, it is now possible. World domination has been achieved, thank you for playing. We don't know when we finish tapping now, so add a timeout to send the last click event once the finger has been released for the last time. This guarantees that the timestamp of the last button down is later than the last release. This avoids the bug fixed in synaptics commit xf86-input-synaptics-1.8.0-21-g37d34f0 (some application don't handle doubletap correctly without the timestamps). This works for double-tap immediately, for multi-tap we need to remember the timestamp of the first press event and use it for the release event so that there's a forced gap between the release and the second press. https://bugs.freedesktop.org/show_bug.cgi?id=89511 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-04-16 10:19:11 +10:00
</g>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<path d="M 61584.5 45206.16 L 61768.13 45202.98" fill="none" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 61773.38 45202.89 L 61766.44 45206.51 L 61768.13 45202.98 L 61766.32 45199.51 Z" fill="#000000" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 61457.5 44510.7 C 61473.62 44516.91 61491.38 44516.91 61507.5 44510.7 C 61523.62 44504.5 61541.38 44504.5 61557.5 44510.7 L 61557.5 44563.28 C 61541.38 44557.08 61523.62 44557.08 61507.5 44563.28 C 61491.38 44569.49 61473.62 44569.49 61457.5 44563.28 L 61457.5 44510.7 Z" fill="#ffb570" stroke="#000000" stroke-width="2" stroke-miterlimit="10" pointer-events="none"/>
touchpad: introduce MULTITAP for multi-tap-and-drag Once we have a doubletap, enter a loop in the state machine where we can tap multiple times and either get a multi-click or a multi-click drag-and-drop. The sequence down/up down/up down/up produces a triple-click. The sequence down/up down/up down/up down produces a triple-click with a button down for dragging. Yes, that glorious octuple-tap-and-drag, it is now possible. World domination has been achieved, thank you for playing. We don't know when we finish tapping now, so add a timeout to send the last click event once the finger has been released for the last time. This guarantees that the timestamp of the last button down is later than the last release. This avoids the bug fixed in synaptics commit xf86-input-synaptics-1.8.0-21-g37d34f0 (some application don't handle doubletap correctly without the timestamps). This works for double-tap immediately, for multi-tap we need to remember the timestamp of the first press event and use it for the release event so that there's a forced gap between the release and the second press. https://bugs.freedesktop.org/show_bug.cgi?id=89511 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-04-16 10:19:11 +10:00
<g fill="#000000" font-family="Helvetica" text-anchor="middle" font-size="12px">
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<text x="61507.25" y="44540.75">
touchpad: end tap-and-drag with an extra tap Currently for the tap-and-drag gesture to end user has to wait for a timeout to expire. Make it possible to end the drag gesture by just tapping. The allowed finger sequences to start and end a drag are thus: tap, down, .... move ...., up <wait for timeout> tap, down, .... move ...., up, tap https://bugs.freedesktop.org/show_bug.cgi?id=90255 Signed-off-by: Velimir Lisec <lisec.velimir@gmail.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> State diagram changes and a doc change squashed in. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-04-30 00:13:51 +02:00
TOUCH_DEAD</text>
touchpad: introduce MULTITAP for multi-tap-and-drag Once we have a doubletap, enter a loop in the state machine where we can tap multiple times and either get a multi-click or a multi-click drag-and-drop. The sequence down/up down/up down/up produces a triple-click. The sequence down/up down/up down/up down produces a triple-click with a button down for dragging. Yes, that glorious octuple-tap-and-drag, it is now possible. World domination has been achieved, thank you for playing. We don't know when we finish tapping now, so add a timeout to send the last click event once the finger has been released for the last time. This guarantees that the timestamp of the last button down is later than the last release. This avoids the bug fixed in synaptics commit xf86-input-synaptics-1.8.0-21-g37d34f0 (some application don't handle doubletap correctly without the timestamps). This works for double-tap immediately, for multi-tap we need to remember the timestamp of the first press event and use it for the release event so that there's a forced gap between the release and the second press. https://bugs.freedesktop.org/show_bug.cgi?id=89511 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-04-16 10:19:11 +10:00
</g>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<path d="M 61552.61 44432 L 61523.98 44498.65" fill="none" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 61521.9 44503.47 L 61521.45 44495.66 L 61523.98 44498.65 L 61527.88 44498.42 Z" fill="#000000" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 61453.92 44442 L 61486.04 44498.95" fill="none" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 61488.62 44503.53 L 61482.13 44499.15 L 61486.04 44498.95 L 61488.23 44495.71 Z" fill="#000000" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 61302.5 44442 L 61302.5 44493.63" fill="none" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 61302.5 44498.88 L 61299 44491.88 L 61302.5 44493.63 L 61306 44491.88 Z" fill="#000000" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 61386.5 44807.7 C 61402.62 44813.91 61420.38 44813.91 61436.5 44807.7 C 61452.62 44801.5 61470.38 44801.5 61486.5 44807.7 L 61486.5 44860.28 C 61470.38 44854.08 61452.62 44854.08 61436.5 44860.28 C 61420.38 44866.49 61402.62 44866.49 61386.5 44860.28 L 61386.5 44807.7 Z" fill="#e1d5e7" stroke="#000000" stroke-width="2" stroke-miterlimit="10" pointer-events="none"/>
touchpad: introduce MULTITAP for multi-tap-and-drag Once we have a doubletap, enter a loop in the state machine where we can tap multiple times and either get a multi-click or a multi-click drag-and-drop. The sequence down/up down/up down/up produces a triple-click. The sequence down/up down/up down/up down produces a triple-click with a button down for dragging. Yes, that glorious octuple-tap-and-drag, it is now possible. World domination has been achieved, thank you for playing. We don't know when we finish tapping now, so add a timeout to send the last click event once the finger has been released for the last time. This guarantees that the timestamp of the last button down is later than the last release. This avoids the bug fixed in synaptics commit xf86-input-synaptics-1.8.0-21-g37d34f0 (some application don't handle doubletap correctly without the timestamps). This works for double-tap immediately, for multi-tap we need to remember the timestamp of the first press event and use it for the release event so that there's a forced gap between the release and the second press. https://bugs.freedesktop.org/show_bug.cgi?id=89511 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-04-16 10:19:11 +10:00
<g fill="#000000" font-family="Helvetica" text-anchor="middle" font-size="12px">
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<text x="61436.25" y="44830.75">
touchpad: end tap-and-drag with an extra tap Currently for the tap-and-drag gesture to end user has to wait for a timeout to expire. Make it possible to end the drag gesture by just tapping. The allowed finger sequences to start and end a drag are thus: tap, down, .... move ...., up <wait for timeout> tap, down, .... move ...., up, tap https://bugs.freedesktop.org/show_bug.cgi?id=90255 Signed-off-by: Velimir Lisec <lisec.velimir@gmail.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> State diagram changes and a doc change squashed in. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-04-30 00:13:51 +02:00
that finger</text>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<text x="61436.25" y="44844.75">
touchpad: end tap-and-drag with an extra tap Currently for the tap-and-drag gesture to end user has to wait for a timeout to expire. Make it possible to end the drag gesture by just tapping. The allowed finger sequences to start and end a drag are thus: tap, down, .... move ...., up <wait for timeout> tap, down, .... move ...., up, tap https://bugs.freedesktop.org/show_bug.cgi?id=90255 Signed-off-by: Velimir Lisec <lisec.velimir@gmail.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> State diagram changes and a doc change squashed in. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-04-30 00:13:51 +02:00
TOUCH_IDLE</text>
touchpad: introduce MULTITAP for multi-tap-and-drag Once we have a doubletap, enter a loop in the state machine where we can tap multiple times and either get a multi-click or a multi-click drag-and-drop. The sequence down/up down/up down/up produces a triple-click. The sequence down/up down/up down/up down produces a triple-click with a button down for dragging. Yes, that glorious octuple-tap-and-drag, it is now possible. World domination has been achieved, thank you for playing. We don't know when we finish tapping now, so add a timeout to send the last click event once the finger has been released for the last time. This guarantees that the timestamp of the last button down is later than the last release. This avoids the bug fixed in synaptics commit xf86-input-synaptics-1.8.0-21-g37d34f0 (some application don't handle doubletap correctly without the timestamps). This works for double-tap immediately, for multi-tap we need to remember the timestamp of the first press event and use it for the release event so that there's a forced gap between the release and the second press. https://bugs.freedesktop.org/show_bug.cgi?id=89511 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-04-16 10:19:11 +10:00
</g>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<path d="M 61285 44827.2 L 61380.14 44831.47" fill="none" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 61385.38 44831.71 L 61378.23 44834.89 L 61380.14 44831.47 L 61378.55 44827.9 Z" fill="#000000" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 61326.09 44600 L 61418.45 44795.74" fill="none" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 61420.69 44800.49 L 61414.54 44795.65 L 61418.45 44795.74 L 61420.87 44792.66 Z" fill="#000000" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
touchpad: introduce MULTITAP for multi-tap-and-drag Once we have a doubletap, enter a loop in the state machine where we can tap multiple times and either get a multi-click or a multi-click drag-and-drop. The sequence down/up down/up down/up produces a triple-click. The sequence down/up down/up down/up down produces a triple-click with a button down for dragging. Yes, that glorious octuple-tap-and-drag, it is now possible. World domination has been achieved, thank you for playing. We don't know when we finish tapping now, so add a timeout to send the last click event once the finger has been released for the last time. This guarantees that the timestamp of the last button down is later than the last release. This avoids the bug fixed in synaptics commit xf86-input-synaptics-1.8.0-21-g37d34f0 (some application don't handle doubletap correctly without the timestamps). This works for double-tap immediately, for multi-tap we need to remember the timestamp of the first press event and use it for the release event so that there's a forced gap between the release and the second press. https://bugs.freedesktop.org/show_bug.cgi?id=89511 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-04-16 10:19:11 +10:00
<g fill="#000000" font-family="Helvetica" text-anchor="middle" font-size="11px">
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<rect fill="#ffffff" stroke="none" x="61367" y="44694" width="14" height="14" stroke-width="0"/>
<text x="61373.46" y="44703.89">
touchpad: end tap-and-drag with an extra tap Currently for the tap-and-drag gesture to end user has to wait for a timeout to expire. Make it possible to end the drag gesture by just tapping. The allowed finger sequences to start and end a drag are thus: tap, down, .... move ...., up <wait for timeout> tap, down, .... move ...., up, tap https://bugs.freedesktop.org/show_bug.cgi?id=90255 Signed-off-by: Velimir Lisec <lisec.velimir@gmail.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> State diagram changes and a doc change squashed in. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-04-30 00:13:51 +02:00
no</text>
touchpad: disable tapping for fingers exceeding the timeout/motion threshold The current code triggers multi-finger tapping even if the finger released was previously held on the touchpad for a while. For an event sequence of: 1. first finger down 2. first finger move past threshold/wait past timeout 3. second finger down 4. first finger up The second finger initiates the two-finger tap state, but the button event is sent when the first finger releases - despite that finger not meeting the usual tap constraints. This sequence can happen whenever a user swaps fingers. Add the finger state to the actual touchpoints and update them whenever the constrains are broken. Then, discard button events if the respective touch did not meet the conditions. http://bugs.freedesktop.org/76760 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2014-06-20 14:16:13 +10:00
</g>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<path d="M 60751.5 43940.7 C 60767.62 43946.91 60785.38 43946.91 60801.5 43940.7 C 60817.62 43934.5 60835.38 43934.5 60851.5 43940.7 L 60851.5 43993.28 C 60835.38 43987.08 60817.62 43987.08 60801.5 43993.28 C 60785.38 43999.49 60767.62 43999.49 60751.5 43993.28 L 60751.5 43940.7 Z" fill="#ffd966" stroke="#000000" stroke-width="2" stroke-miterlimit="10" pointer-events="none"/>
touchpad: disable tapping for fingers exceeding the timeout/motion threshold The current code triggers multi-finger tapping even if the finger released was previously held on the touchpad for a while. For an event sequence of: 1. first finger down 2. first finger move past threshold/wait past timeout 3. second finger down 4. first finger up The second finger initiates the two-finger tap state, but the button event is sent when the first finger releases - despite that finger not meeting the usual tap constraints. This sequence can happen whenever a user swaps fingers. Add the finger state to the actual touchpoints and update them whenever the constrains are broken. Then, discard button events if the respective touch did not meet the conditions. http://bugs.freedesktop.org/76760 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2014-06-20 14:16:13 +10:00
<g fill="#000000" font-family="Helvetica" text-anchor="middle" font-size="12px">
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<text x="60801.25" y="43970.75">
touchpad: end tap-and-drag with an extra tap Currently for the tap-and-drag gesture to end user has to wait for a timeout to expire. Make it possible to end the drag gesture by just tapping. The allowed finger sequences to start and end a drag are thus: tap, down, .... move ...., up <wait for timeout> tap, down, .... move ...., up, tap https://bugs.freedesktop.org/show_bug.cgi?id=90255 Signed-off-by: Velimir Lisec <lisec.velimir@gmail.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> State diagram changes and a doc change squashed in. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-04-30 00:13:51 +02:00
TOUCH_TOUCH</text>
touchpad: disable tapping for fingers exceeding the timeout/motion threshold The current code triggers multi-finger tapping even if the finger released was previously held on the touchpad for a while. For an event sequence of: 1. first finger down 2. first finger move past threshold/wait past timeout 3. second finger down 4. first finger up The second finger initiates the two-finger tap state, but the button event is sent when the first finger releases - despite that finger not meeting the usual tap constraints. This sequence can happen whenever a user swaps fingers. Add the finger state to the actual touchpoints and update them whenever the constrains are broken. Then, discard button events if the respective touch did not meet the conditions. http://bugs.freedesktop.org/76760 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2014-06-20 14:16:13 +10:00
</g>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<path d="M 60728.65 43903 L 60759.72 43930.3" fill="none" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 60763.67 43933.76 L 60756.1 43931.77 L 60759.72 43930.3 L 60760.72 43926.51 Z" fill="#000000" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 60093 43834.2 C 60109.12 43840.41 60126.88 43840.41 60143 43834.2 C 60159.12 43828 60176.88 43828 60193 43834.2 L 60193 43886.78 C 60176.88 43880.58 60159.12 43880.58 60143 43886.78 C 60126.88 43892.99 60109.12 43892.99 60093 43886.78 L 60093 43834.2 Z" fill="#ffd966" stroke="#000000" stroke-width="2" stroke-miterlimit="10" pointer-events="none"/>
touchpad: disable tapping for fingers exceeding the timeout/motion threshold The current code triggers multi-finger tapping even if the finger released was previously held on the touchpad for a while. For an event sequence of: 1. first finger down 2. first finger move past threshold/wait past timeout 3. second finger down 4. first finger up The second finger initiates the two-finger tap state, but the button event is sent when the first finger releases - despite that finger not meeting the usual tap constraints. This sequence can happen whenever a user swaps fingers. Add the finger state to the actual touchpoints and update them whenever the constrains are broken. Then, discard button events if the respective touch did not meet the conditions. http://bugs.freedesktop.org/76760 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2014-06-20 14:16:13 +10:00
<g fill="#000000" font-family="Helvetica" text-anchor="middle" font-size="12px">
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<text x="60142.75" y="43864.25">
touchpad: end tap-and-drag with an extra tap Currently for the tap-and-drag gesture to end user has to wait for a timeout to expire. Make it possible to end the drag gesture by just tapping. The allowed finger sequences to start and end a drag are thus: tap, down, .... move ...., up <wait for timeout> tap, down, .... move ...., up, tap https://bugs.freedesktop.org/show_bug.cgi?id=90255 Signed-off-by: Velimir Lisec <lisec.velimir@gmail.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> State diagram changes and a doc change squashed in. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-04-30 00:13:51 +02:00
TOUCH_IDLE</text>
touchpad: disable tapping for fingers exceeding the timeout/motion threshold The current code triggers multi-finger tapping even if the finger released was previously held on the touchpad for a while. For an event sequence of: 1. first finger down 2. first finger move past threshold/wait past timeout 3. second finger down 4. first finger up The second finger initiates the two-finger tap state, but the button event is sent when the first finger releases - despite that finger not meeting the usual tap constraints. This sequence can happen whenever a user swaps fingers. Add the finger state to the actual touchpoints and update them whenever the constrains are broken. Then, discard button events if the respective touch did not meet the conditions. http://bugs.freedesktop.org/76760 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2014-06-20 14:16:13 +10:00
</g>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<path d="M 60551.5 44223.7 C 60567.62 44229.91 60585.38 44229.91 60601.5 44223.7 C 60617.62 44217.5 60635.38 44217.5 60651.5 44223.7 L 60651.5 44276.28 C 60635.38 44270.08 60617.62 44270.08 60601.5 44276.28 C 60585.38 44282.49 60567.62 44282.49 60551.5 44276.28 L 60551.5 44223.7 Z" fill="#7ea6e0" stroke="#000000" stroke-width="2" stroke-miterlimit="10" pointer-events="none"/>
touchpad: disable tapping for fingers exceeding the timeout/motion threshold The current code triggers multi-finger tapping even if the finger released was previously held on the touchpad for a while. For an event sequence of: 1. first finger down 2. first finger move past threshold/wait past timeout 3. second finger down 4. first finger up The second finger initiates the two-finger tap state, but the button event is sent when the first finger releases - despite that finger not meeting the usual tap constraints. This sequence can happen whenever a user swaps fingers. Add the finger state to the actual touchpoints and update them whenever the constrains are broken. Then, discard button events if the respective touch did not meet the conditions. http://bugs.freedesktop.org/76760 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2014-06-20 14:16:13 +10:00
<g fill="#000000" font-family="Helvetica" text-anchor="middle" font-size="12px">
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<text x="60601.25" y="44253.75">
touchpad: end tap-and-drag with an extra tap Currently for the tap-and-drag gesture to end user has to wait for a timeout to expire. Make it possible to end the drag gesture by just tapping. The allowed finger sequences to start and end a drag are thus: tap, down, .... move ...., up <wait for timeout> tap, down, .... move ...., up, tap https://bugs.freedesktop.org/show_bug.cgi?id=90255 Signed-off-by: Velimir Lisec <lisec.velimir@gmail.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> State diagram changes and a doc change squashed in. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-04-30 00:13:51 +02:00
TOUCH_TOUCH</text>
touchpad: disable tapping for fingers exceeding the timeout/motion threshold The current code triggers multi-finger tapping even if the finger released was previously held on the touchpad for a while. For an event sequence of: 1. first finger down 2. first finger move past threshold/wait past timeout 3. second finger down 4. first finger up The second finger initiates the two-finger tap state, but the button event is sent when the first finger releases - despite that finger not meeting the usual tap constraints. This sequence can happen whenever a user swaps fingers. Add the finger state to the actual touchpoints and update them whenever the constrains are broken. Then, discard button events if the respective touch did not meet the conditions. http://bugs.freedesktop.org/76760 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2014-06-20 14:16:13 +10:00
</g>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<path d="M 60622.67 44157 L 60610.31 44211.29" fill="none" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 60609.15 44216.41 L 60607.29 44208.81 L 60610.31 44211.29 L 60614.11 44210.36 Z" fill="#000000" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 60359.5 44203.7 C 60375.62 44209.91 60393.38 44209.91 60409.5 44203.7 C 60425.62 44197.5 60443.38 44197.5 60459.5 44203.7 L 60459.5 44256.28 C 60443.38 44250.08 60425.62 44250.08 60409.5 44256.28 C 60393.38 44262.49 60375.62 44262.49 60359.5 44256.28 L 60359.5 44203.7 Z" fill="#ffd966" stroke="#000000" stroke-width="2" stroke-miterlimit="10" pointer-events="none"/>
touchpad: disable tapping for fingers exceeding the timeout/motion threshold The current code triggers multi-finger tapping even if the finger released was previously held on the touchpad for a while. For an event sequence of: 1. first finger down 2. first finger move past threshold/wait past timeout 3. second finger down 4. first finger up The second finger initiates the two-finger tap state, but the button event is sent when the first finger releases - despite that finger not meeting the usual tap constraints. This sequence can happen whenever a user swaps fingers. Add the finger state to the actual touchpoints and update them whenever the constrains are broken. Then, discard button events if the respective touch did not meet the conditions. http://bugs.freedesktop.org/76760 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2014-06-20 14:16:13 +10:00
<g fill="#000000" font-family="Helvetica" text-anchor="middle" font-size="12px">
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<text x="60409.25" y="44233.75">
touchpad: end tap-and-drag with an extra tap Currently for the tap-and-drag gesture to end user has to wait for a timeout to expire. Make it possible to end the drag gesture by just tapping. The allowed finger sequences to start and end a drag are thus: tap, down, .... move ...., up <wait for timeout> tap, down, .... move ...., up, tap https://bugs.freedesktop.org/show_bug.cgi?id=90255 Signed-off-by: Velimir Lisec <lisec.velimir@gmail.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> State diagram changes and a doc change squashed in. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-04-30 00:13:51 +02:00
TOUCH_DEAD</text>
touchpad: disable tapping for fingers exceeding the timeout/motion threshold The current code triggers multi-finger tapping even if the finger released was previously held on the touchpad for a while. For an event sequence of: 1. first finger down 2. first finger move past threshold/wait past timeout 3. second finger down 4. first finger up The second finger initiates the two-finger tap state, but the button event is sent when the first finger releases - despite that finger not meeting the usual tap constraints. This sequence can happen whenever a user swaps fingers. Add the finger state to the actual touchpoints and update them whenever the constrains are broken. Then, discard button events if the respective touch did not meet the conditions. http://bugs.freedesktop.org/76760 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2014-06-20 14:16:13 +10:00
</g>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<path d="M 60312.36 44162 L 60357.85 44193.85" fill="none" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 60362.16 44196.86 L 60354.41 44195.71 L 60357.85 44193.85 L 60358.43 44189.98 Z" fill="#000000" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 60455.57 44157 L 60433.41 44192.11" fill="none" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 60430.61 44196.55 L 60431.38 44188.77 L 60433.41 44192.11 L 60437.3 44192.5 Z" fill="#000000" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 60141.5 44575.7 C 60157.62 44581.91 60175.38 44581.91 60191.5 44575.7 C 60207.62 44569.5 60225.38 44569.5 60241.5 44575.7 L 60241.5 44628.28 C 60225.38 44622.08 60207.62 44622.08 60191.5 44628.28 C 60175.38 44634.49 60157.62 44634.49 60141.5 44628.28 L 60141.5 44575.7 Z" fill="#ffd966" stroke="#000000" stroke-width="2" stroke-miterlimit="10" pointer-events="none"/>
touchpad: disable tapping for fingers exceeding the timeout/motion threshold The current code triggers multi-finger tapping even if the finger released was previously held on the touchpad for a while. For an event sequence of: 1. first finger down 2. first finger move past threshold/wait past timeout 3. second finger down 4. first finger up The second finger initiates the two-finger tap state, but the button event is sent when the first finger releases - despite that finger not meeting the usual tap constraints. This sequence can happen whenever a user swaps fingers. Add the finger state to the actual touchpoints and update them whenever the constrains are broken. Then, discard button events if the respective touch did not meet the conditions. http://bugs.freedesktop.org/76760 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2014-06-20 14:16:13 +10:00
<g fill="#000000" font-family="Helvetica" text-anchor="middle" font-size="12px">
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<text x="60191.25" y="44605.75">
touchpad: end tap-and-drag with an extra tap Currently for the tap-and-drag gesture to end user has to wait for a timeout to expire. Make it possible to end the drag gesture by just tapping. The allowed finger sequences to start and end a drag are thus: tap, down, .... move ...., up <wait for timeout> tap, down, .... move ...., up, tap https://bugs.freedesktop.org/show_bug.cgi?id=90255 Signed-off-by: Velimir Lisec <lisec.velimir@gmail.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> State diagram changes and a doc change squashed in. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-04-30 00:13:51 +02:00
TOUCH_IDLE</text>
touchpad: disable tapping for fingers exceeding the timeout/motion threshold The current code triggers multi-finger tapping even if the finger released was previously held on the touchpad for a while. For an event sequence of: 1. first finger down 2. first finger move past threshold/wait past timeout 3. second finger down 4. first finger up The second finger initiates the two-finger tap state, but the button event is sent when the first finger releases - despite that finger not meeting the usual tap constraints. This sequence can happen whenever a user swaps fingers. Add the finger state to the actual touchpoints and update them whenever the constrains are broken. Then, discard button events if the respective touch did not meet the conditions. http://bugs.freedesktop.org/76760 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2014-06-20 14:16:13 +10:00
</g>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<path d="M 60228.31 44522 L 60195.84 44564.92" fill="none" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 60192.67 44569.11 L 60194.11 44561.41 L 60195.84 44564.92 L 60199.69 44565.64 Z" fill="#000000" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 60020.5 44573.7 C 60036.62 44579.91 60054.38 44579.91 60070.5 44573.7 C 60086.62 44567.5 60104.38 44567.5 60120.5 44573.7 L 60120.5 44626.28 C 60104.38 44620.08 60086.62 44620.08 60070.5 44626.28 C 60054.38 44632.49 60036.62 44632.49 60020.5 44626.28 L 60020.5 44573.7 Z" fill="#ffd966" stroke="#000000" stroke-width="2" stroke-miterlimit="10" pointer-events="none"/>
touchpad: disable tapping for fingers exceeding the timeout/motion threshold The current code triggers multi-finger tapping even if the finger released was previously held on the touchpad for a while. For an event sequence of: 1. first finger down 2. first finger move past threshold/wait past timeout 3. second finger down 4. first finger up The second finger initiates the two-finger tap state, but the button event is sent when the first finger releases - despite that finger not meeting the usual tap constraints. This sequence can happen whenever a user swaps fingers. Add the finger state to the actual touchpoints and update them whenever the constrains are broken. Then, discard button events if the respective touch did not meet the conditions. http://bugs.freedesktop.org/76760 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2014-06-20 14:16:13 +10:00
<g fill="#000000" font-family="Helvetica" text-anchor="middle" font-size="12px">
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<text x="60070.25" y="44603.75">
touchpad: end tap-and-drag with an extra tap Currently for the tap-and-drag gesture to end user has to wait for a timeout to expire. Make it possible to end the drag gesture by just tapping. The allowed finger sequences to start and end a drag are thus: tap, down, .... move ...., up <wait for timeout> tap, down, .... move ...., up, tap https://bugs.freedesktop.org/show_bug.cgi?id=90255 Signed-off-by: Velimir Lisec <lisec.velimir@gmail.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> State diagram changes and a doc change squashed in. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-04-30 00:13:51 +02:00
TOUCH_TOUCH</text>
touchpad: disable tapping for fingers exceeding the timeout/motion threshold The current code triggers multi-finger tapping even if the finger released was previously held on the touchpad for a while. For an event sequence of: 1. first finger down 2. first finger move past threshold/wait past timeout 3. second finger down 4. first finger up The second finger initiates the two-finger tap state, but the button event is sent when the first finger releases - despite that finger not meeting the usual tap constraints. This sequence can happen whenever a user swaps fingers. Add the finger state to the actual touchpoints and update them whenever the constrains are broken. Then, discard button events if the respective touch did not meet the conditions. http://bugs.freedesktop.org/76760 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2014-06-20 14:16:13 +10:00
</g>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<path d="M 60417.5 44670.7 C 60433.62 44676.91 60451.38 44676.91 60467.5 44670.7 C 60483.62 44664.5 60501.38 44664.5 60517.5 44670.7 L 60517.5 44723.28 C 60501.38 44717.08 60483.62 44717.08 60467.5 44723.28 C 60451.38 44729.49 60433.62 44729.49 60417.5 44723.28 L 60417.5 44670.7 Z" fill="#7ea6e0" stroke="#000000" stroke-width="2" stroke-miterlimit="10" pointer-events="none"/>
touchpad: disable tapping for fingers exceeding the timeout/motion threshold The current code triggers multi-finger tapping even if the finger released was previously held on the touchpad for a while. For an event sequence of: 1. first finger down 2. first finger move past threshold/wait past timeout 3. second finger down 4. first finger up The second finger initiates the two-finger tap state, but the button event is sent when the first finger releases - despite that finger not meeting the usual tap constraints. This sequence can happen whenever a user swaps fingers. Add the finger state to the actual touchpoints and update them whenever the constrains are broken. Then, discard button events if the respective touch did not meet the conditions. http://bugs.freedesktop.org/76760 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2014-06-20 14:16:13 +10:00
<g fill="#000000" font-family="Helvetica" text-anchor="middle" font-size="12px">
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<text x="60467.25" y="44700.75">
touchpad: end tap-and-drag with an extra tap Currently for the tap-and-drag gesture to end user has to wait for a timeout to expire. Make it possible to end the drag gesture by just tapping. The allowed finger sequences to start and end a drag are thus: tap, down, .... move ...., up <wait for timeout> tap, down, .... move ...., up, tap https://bugs.freedesktop.org/show_bug.cgi?id=90255 Signed-off-by: Velimir Lisec <lisec.velimir@gmail.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> State diagram changes and a doc change squashed in. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-04-30 00:13:51 +02:00
TOUCH_TOUCH</text>
touchpad: disable tapping for fingers exceeding the timeout/motion threshold The current code triggers multi-finger tapping even if the finger released was previously held on the touchpad for a while. For an event sequence of: 1. first finger down 2. first finger move past threshold/wait past timeout 3. second finger down 4. first finger up The second finger initiates the two-finger tap state, but the button event is sent when the first finger releases - despite that finger not meeting the usual tap constraints. This sequence can happen whenever a user swaps fingers. Add the finger state to the actual touchpoints and update them whenever the constrains are broken. Then, discard button events if the respective touch did not meet the conditions. http://bugs.freedesktop.org/76760 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2014-06-20 14:16:13 +10:00
</g>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<path d="M 60366 44640.84 L 60411.93 44666.25" fill="none" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 60416.52 44668.79 L 60408.7 44668.47 L 60411.93 44666.25 L 60412.09 44662.34 Z" fill="#000000" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 60366.5 44465.7 C 60382.62 44471.91 60400.38 44471.91 60416.5 44465.7 C 60432.62 44459.5 60450.38 44459.5 60466.5 44465.7 L 60466.5 44518.28 C 60450.38 44512.08 60432.62 44512.08 60416.5 44518.28 C 60400.38 44524.49 60382.62 44524.49 60366.5 44518.28 L 60366.5 44465.7 Z" fill="#ffd966" stroke="#000000" stroke-width="2" stroke-miterlimit="10" pointer-events="none"/>
touchpad: disable tapping for fingers exceeding the timeout/motion threshold The current code triggers multi-finger tapping even if the finger released was previously held on the touchpad for a while. For an event sequence of: 1. first finger down 2. first finger move past threshold/wait past timeout 3. second finger down 4. first finger up The second finger initiates the two-finger tap state, but the button event is sent when the first finger releases - despite that finger not meeting the usual tap constraints. This sequence can happen whenever a user swaps fingers. Add the finger state to the actual touchpoints and update them whenever the constrains are broken. Then, discard button events if the respective touch did not meet the conditions. http://bugs.freedesktop.org/76760 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2014-06-20 14:16:13 +10:00
<g fill="#000000" font-family="Helvetica" text-anchor="middle" font-size="12px">
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<text x="60416.25" y="44495.75">
touchpad: end tap-and-drag with an extra tap Currently for the tap-and-drag gesture to end user has to wait for a timeout to expire. Make it possible to end the drag gesture by just tapping. The allowed finger sequences to start and end a drag are thus: tap, down, .... move ...., up <wait for timeout> tap, down, .... move ...., up, tap https://bugs.freedesktop.org/show_bug.cgi?id=90255 Signed-off-by: Velimir Lisec <lisec.velimir@gmail.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> State diagram changes and a doc change squashed in. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-04-30 00:13:51 +02:00
TOUCH_IDLE</text>
touchpad: disable tapping for fingers exceeding the timeout/motion threshold The current code triggers multi-finger tapping even if the finger released was previously held on the touchpad for a while. For an event sequence of: 1. first finger down 2. first finger move past threshold/wait past timeout 3. second finger down 4. first finger up The second finger initiates the two-finger tap state, but the button event is sent when the first finger releases - despite that finger not meeting the usual tap constraints. This sequence can happen whenever a user swaps fingers. Add the finger state to the actual touchpoints and update them whenever the constrains are broken. Then, discard button events if the respective touch did not meet the conditions. http://bugs.freedesktop.org/76760 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2014-06-20 14:16:13 +10:00
</g>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<path d="M 60425.93 44554 L 60422.4 44530.8" fill="none" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 60421.61 44525.61 L 60426.13 44532 L 60422.4 44530.8 L 60419.21 44533.05 Z" fill="#000000" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 60531.5 44581.7 C 60547.62 44587.91 60565.38 44587.91 60581.5 44581.7 C 60597.62 44575.5 60615.38 44575.5 60631.5 44581.7 L 60631.5 44634.28 C 60615.38 44628.08 60597.62 44628.08 60581.5 44634.28 C 60565.38 44640.49 60547.62 44640.49 60531.5 44634.28 L 60531.5 44581.7 Z" fill="#7ea6e0" stroke="#000000" stroke-width="2" stroke-miterlimit="10" pointer-events="none"/>
touchpad: disable tapping for fingers exceeding the timeout/motion threshold The current code triggers multi-finger tapping even if the finger released was previously held on the touchpad for a while. For an event sequence of: 1. first finger down 2. first finger move past threshold/wait past timeout 3. second finger down 4. first finger up The second finger initiates the two-finger tap state, but the button event is sent when the first finger releases - despite that finger not meeting the usual tap constraints. This sequence can happen whenever a user swaps fingers. Add the finger state to the actual touchpoints and update them whenever the constrains are broken. Then, discard button events if the respective touch did not meet the conditions. http://bugs.freedesktop.org/76760 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2014-06-20 14:16:13 +10:00
<g fill="#000000" font-family="Helvetica" text-anchor="middle" font-size="12px">
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<text x="60581.25" y="44611.75">
touchpad: end tap-and-drag with an extra tap Currently for the tap-and-drag gesture to end user has to wait for a timeout to expire. Make it possible to end the drag gesture by just tapping. The allowed finger sequences to start and end a drag are thus: tap, down, .... move ...., up <wait for timeout> tap, down, .... move ...., up, tap https://bugs.freedesktop.org/show_bug.cgi?id=90255 Signed-off-by: Velimir Lisec <lisec.velimir@gmail.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> State diagram changes and a doc change squashed in. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-04-30 00:13:51 +02:00
TOUCH_IDLE</text>
touchpad: disable tapping for fingers exceeding the timeout/motion threshold The current code triggers multi-finger tapping even if the finger released was previously held on the touchpad for a while. For an event sequence of: 1. first finger down 2. first finger move past threshold/wait past timeout 3. second finger down 4. first finger up The second finger initiates the two-finger tap state, but the button event is sent when the first finger releases - despite that finger not meeting the usual tap constraints. This sequence can happen whenever a user swaps fingers. Add the finger state to the actual touchpoints and update them whenever the constrains are broken. Then, discard button events if the respective touch did not meet the conditions. http://bugs.freedesktop.org/76760 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2014-06-20 14:16:13 +10:00
</g>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<path d="M 60596 44550 L 60591.17 44569.32" fill="none" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 60589.9 44574.42 L 60588.2 44566.78 L 60591.17 44569.32 L 60594.99 44568.47 Z" fill="#000000" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 60730.5 44861.7 C 60746.62 44867.91 60764.38 44867.91 60780.5 44861.7 C 60796.62 44855.5 60814.38 44855.5 60830.5 44861.7 L 60830.5 44914.28 C 60814.38 44908.08 60796.62 44908.08 60780.5 44914.28 C 60764.38 44920.49 60746.62 44920.49 60730.5 44914.28 L 60730.5 44861.7 Z" fill="#ffb570" stroke="#000000" stroke-width="2" stroke-miterlimit="10" pointer-events="none"/>
touchpad: disable tapping for fingers exceeding the timeout/motion threshold The current code triggers multi-finger tapping even if the finger released was previously held on the touchpad for a while. For an event sequence of: 1. first finger down 2. first finger move past threshold/wait past timeout 3. second finger down 4. first finger up The second finger initiates the two-finger tap state, but the button event is sent when the first finger releases - despite that finger not meeting the usual tap constraints. This sequence can happen whenever a user swaps fingers. Add the finger state to the actual touchpoints and update them whenever the constrains are broken. Then, discard button events if the respective touch did not meet the conditions. http://bugs.freedesktop.org/76760 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2014-06-20 14:16:13 +10:00
<g fill="#000000" font-family="Helvetica" text-anchor="middle" font-size="12px">
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<text x="60780.25" y="44891.75">
touchpad: end tap-and-drag with an extra tap Currently for the tap-and-drag gesture to end user has to wait for a timeout to expire. Make it possible to end the drag gesture by just tapping. The allowed finger sequences to start and end a drag are thus: tap, down, .... move ...., up <wait for timeout> tap, down, .... move ...., up, tap https://bugs.freedesktop.org/show_bug.cgi?id=90255 Signed-off-by: Velimir Lisec <lisec.velimir@gmail.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> State diagram changes and a doc change squashed in. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-04-30 00:13:51 +02:00
TOUCH_TOUCH</text>
touchpad: disable tapping for fingers exceeding the timeout/motion threshold The current code triggers multi-finger tapping even if the finger released was previously held on the touchpad for a while. For an event sequence of: 1. first finger down 2. first finger move past threshold/wait past timeout 3. second finger down 4. first finger up The second finger initiates the two-finger tap state, but the button event is sent when the first finger releases - despite that finger not meeting the usual tap constraints. This sequence can happen whenever a user swaps fingers. Add the finger state to the actual touchpoints and update them whenever the constrains are broken. Then, discard button events if the respective touch did not meet the conditions. http://bugs.freedesktop.org/76760 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2014-06-20 14:16:13 +10:00
</g>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<path d="M 60701.02 44522 L 60772.09 44849.28" fill="none" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 60773.2 44854.41 L 60768.3 44848.31 L 60772.09 44849.28 L 60775.14 44846.82 Z" fill="#000000" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 61662.5 43628.7 C 61678.62 43634.91 61696.38 43634.91 61712.5 43628.7 C 61728.62 43622.5 61746.38 43622.5 61762.5 43628.7 L 61762.5 43681.28 C 61746.38 43675.08 61728.62 43675.08 61712.5 43681.28 C 61696.38 43687.49 61678.62 43687.49 61662.5 43681.28 L 61662.5 43628.7 Z" fill="#ffd966" stroke="#000000" stroke-width="2" stroke-miterlimit="10" pointer-events="none"/>
touchpad: disable tapping for fingers exceeding the timeout/motion threshold The current code triggers multi-finger tapping even if the finger released was previously held on the touchpad for a while. For an event sequence of: 1. first finger down 2. first finger move past threshold/wait past timeout 3. second finger down 4. first finger up The second finger initiates the two-finger tap state, but the button event is sent when the first finger releases - despite that finger not meeting the usual tap constraints. This sequence can happen whenever a user swaps fingers. Add the finger state to the actual touchpoints and update them whenever the constrains are broken. Then, discard button events if the respective touch did not meet the conditions. http://bugs.freedesktop.org/76760 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2014-06-20 14:16:13 +10:00
<g fill="#000000" font-family="Helvetica" text-anchor="middle" font-size="12px">
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<text x="61712.25" y="43658.75">
touchpad: end tap-and-drag with an extra tap Currently for the tap-and-drag gesture to end user has to wait for a timeout to expire. Make it possible to end the drag gesture by just tapping. The allowed finger sequences to start and end a drag are thus: tap, down, .... move ...., up <wait for timeout> tap, down, .... move ...., up, tap https://bugs.freedesktop.org/show_bug.cgi?id=90255 Signed-off-by: Velimir Lisec <lisec.velimir@gmail.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> State diagram changes and a doc change squashed in. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-04-30 00:13:51 +02:00
TOUCH_IDLE</text>
touchpad: disable tapping for fingers exceeding the timeout/motion threshold The current code triggers multi-finger tapping even if the finger released was previously held on the touchpad for a while. For an event sequence of: 1. first finger down 2. first finger move past threshold/wait past timeout 3. second finger down 4. first finger up The second finger initiates the two-finger tap state, but the button event is sent when the first finger releases - despite that finger not meeting the usual tap constraints. This sequence can happen whenever a user swaps fingers. Add the finger state to the actual touchpoints and update them whenever the constrains are broken. Then, discard button events if the respective touch did not meet the conditions. http://bugs.freedesktop.org/76760 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2014-06-20 14:16:13 +10:00
</g>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<path d="M 61658.2 43610 L 61668.38 43618.44" fill="none" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 61672.42 43621.79 L 61664.8 43620.01 L 61668.38 43618.44 L 61669.27 43614.63 Z" fill="#000000" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 61310.5 44040.7 C 61326.62 44046.91 61344.38 44046.91 61360.5 44040.7 C 61376.62 44034.5 61394.38 44034.5 61410.5 44040.7 L 61410.5 44093.28 C 61394.38 44087.08 61376.62 44087.08 61360.5 44093.28 C 61344.38 44099.49 61326.62 44099.49 61310.5 44093.28 L 61310.5 44040.7 Z" fill="#ffb570" stroke="#000000" stroke-width="2" stroke-miterlimit="10" pointer-events="none"/>
touchpad: disable tapping for fingers exceeding the timeout/motion threshold The current code triggers multi-finger tapping even if the finger released was previously held on the touchpad for a while. For an event sequence of: 1. first finger down 2. first finger move past threshold/wait past timeout 3. second finger down 4. first finger up The second finger initiates the two-finger tap state, but the button event is sent when the first finger releases - despite that finger not meeting the usual tap constraints. This sequence can happen whenever a user swaps fingers. Add the finger state to the actual touchpoints and update them whenever the constrains are broken. Then, discard button events if the respective touch did not meet the conditions. http://bugs.freedesktop.org/76760 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2014-06-20 14:16:13 +10:00
<g fill="#000000" font-family="Helvetica" text-anchor="middle" font-size="12px">
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<text x="61360.25" y="44070.75">
touchpad: end tap-and-drag with an extra tap Currently for the tap-and-drag gesture to end user has to wait for a timeout to expire. Make it possible to end the drag gesture by just tapping. The allowed finger sequences to start and end a drag are thus: tap, down, .... move ...., up <wait for timeout> tap, down, .... move ...., up, tap https://bugs.freedesktop.org/show_bug.cgi?id=90255 Signed-off-by: Velimir Lisec <lisec.velimir@gmail.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> State diagram changes and a doc change squashed in. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-04-30 00:13:51 +02:00
TOUCH_TOUCH</text>
touchpad: disable tapping for fingers exceeding the timeout/motion threshold The current code triggers multi-finger tapping even if the finger released was previously held on the touchpad for a while. For an event sequence of: 1. first finger down 2. first finger move past threshold/wait past timeout 3. second finger down 4. first finger up The second finger initiates the two-finger tap state, but the button event is sent when the first finger releases - despite that finger not meeting the usual tap constraints. This sequence can happen whenever a user swaps fingers. Add the finger state to the actual touchpoints and update them whenever the constrains are broken. Then, discard button events if the respective touch did not meet the conditions. http://bugs.freedesktop.org/76760 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2014-06-20 14:16:13 +10:00
</g>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<path d="M 61383.32 43903 L 61365.9 44028.19" fill="none" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 61365.18 44033.39 L 61362.68 44025.98 L 61365.9 44028.19 L 61369.61 44026.94 Z" fill="#000000" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 60936.5 45516.7 C 60952.62 45522.91 60970.38 45522.91 60986.5 45516.7 C 61002.62 45510.5 61020.38 45510.5 61036.5 45516.7 L 61036.5 45569.28 C 61020.38 45563.08 61002.62 45563.08 60986.5 45569.28 C 60970.38 45575.49 60952.62 45575.49 60936.5 45569.28 L 60936.5 45516.7 Z" fill="#e1d5e7" stroke="#000000" stroke-width="2" stroke-miterlimit="10" pointer-events="none"/>
touchpad: disable tapping for fingers exceeding the timeout/motion threshold The current code triggers multi-finger tapping even if the finger released was previously held on the touchpad for a while. For an event sequence of: 1. first finger down 2. first finger move past threshold/wait past timeout 3. second finger down 4. first finger up The second finger initiates the two-finger tap state, but the button event is sent when the first finger releases - despite that finger not meeting the usual tap constraints. This sequence can happen whenever a user swaps fingers. Add the finger state to the actual touchpoints and update them whenever the constrains are broken. Then, discard button events if the respective touch did not meet the conditions. http://bugs.freedesktop.org/76760 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2014-06-20 14:16:13 +10:00
<g fill="#000000" font-family="Helvetica" text-anchor="middle" font-size="12px">
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<text x="60986.25" y="45539.75">
touchpad: end tap-and-drag with an extra tap Currently for the tap-and-drag gesture to end user has to wait for a timeout to expire. Make it possible to end the drag gesture by just tapping. The allowed finger sequences to start and end a drag are thus: tap, down, .... move ...., up <wait for timeout> tap, down, .... move ...., up, tap https://bugs.freedesktop.org/show_bug.cgi?id=90255 Signed-off-by: Velimir Lisec <lisec.velimir@gmail.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> State diagram changes and a doc change squashed in. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-04-30 00:13:51 +02:00
that finger</text>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<text x="60986.25" y="45553.75">
touchpad: end tap-and-drag with an extra tap Currently for the tap-and-drag gesture to end user has to wait for a timeout to expire. Make it possible to end the drag gesture by just tapping. The allowed finger sequences to start and end a drag are thus: tap, down, .... move ...., up <wait for timeout> tap, down, .... move ...., up, tap https://bugs.freedesktop.org/show_bug.cgi?id=90255 Signed-off-by: Velimir Lisec <lisec.velimir@gmail.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> State diagram changes and a doc change squashed in. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-04-30 00:13:51 +02:00
TOUCH_IDLE</text>
touchpad: disable tapping for fingers exceeding the timeout/motion threshold The current code triggers multi-finger tapping even if the finger released was previously held on the touchpad for a while. For an event sequence of: 1. first finger down 2. first finger move past threshold/wait past timeout 3. second finger down 4. first finger up The second finger initiates the two-finger tap state, but the button event is sent when the first finger releases - despite that finger not meeting the usual tap constraints. This sequence can happen whenever a user swaps fingers. Add the finger state to the actual touchpoints and update them whenever the constrains are broken. Then, discard button events if the respective touch did not meet the conditions. http://bugs.freedesktop.org/76760 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2014-06-20 14:16:13 +10:00
</g>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<path d="M 60982.14 45482 L 60983.72 45504.15" fill="none" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 60984.1 45509.38 L 60980.11 45502.65 L 60983.72 45504.15 L 60987.09 45502.15 Z" fill="#000000" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 62119 44701.2 C 62135.12 44707.41 62152.88 44707.41 62169 44701.2 C 62185.12 44695 62202.88 44695 62219 44701.2 L 62219 44753.78 C 62202.88 44747.58 62185.12 44747.58 62169 44753.78 C 62152.88 44759.99 62135.12 44759.99 62119 44753.78 L 62119 44701.2 Z" fill="#ffd966" stroke="#000000" stroke-width="2" stroke-miterlimit="10" pointer-events="none"/>
touchpad: disable tapping for fingers exceeding the timeout/motion threshold The current code triggers multi-finger tapping even if the finger released was previously held on the touchpad for a while. For an event sequence of: 1. first finger down 2. first finger move past threshold/wait past timeout 3. second finger down 4. first finger up The second finger initiates the two-finger tap state, but the button event is sent when the first finger releases - despite that finger not meeting the usual tap constraints. This sequence can happen whenever a user swaps fingers. Add the finger state to the actual touchpoints and update them whenever the constrains are broken. Then, discard button events if the respective touch did not meet the conditions. http://bugs.freedesktop.org/76760 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2014-06-20 14:16:13 +10:00
<g fill="#000000" font-family="Helvetica" text-anchor="middle" font-size="12px">
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<text x="62168.75" y="44731.25">
touchpad: end tap-and-drag with an extra tap Currently for the tap-and-drag gesture to end user has to wait for a timeout to expire. Make it possible to end the drag gesture by just tapping. The allowed finger sequences to start and end a drag are thus: tap, down, .... move ...., up <wait for timeout> tap, down, .... move ...., up, tap https://bugs.freedesktop.org/show_bug.cgi?id=90255 Signed-off-by: Velimir Lisec <lisec.velimir@gmail.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> State diagram changes and a doc change squashed in. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-04-30 00:13:51 +02:00
TOUCH_DEAD</text>
touchpad: disable tapping for fingers exceeding the timeout/motion threshold The current code triggers multi-finger tapping even if the finger released was previously held on the touchpad for a while. For an event sequence of: 1. first finger down 2. first finger move past threshold/wait past timeout 3. second finger down 4. first finger up The second finger initiates the two-finger tap state, but the button event is sent when the first finger releases - despite that finger not meeting the usual tap constraints. This sequence can happen whenever a user swaps fingers. Add the finger state to the actual touchpoints and update them whenever the constrains are broken. Then, discard button events if the respective touch did not meet the conditions. http://bugs.freedesktop.org/76760 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2014-06-20 14:16:13 +10:00
</g>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<path d="M 62171 43737 L 62171 44332 Q 62171 44342 62171 44352 L 62171 44688.63" fill="none" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 62171 44693.88 L 62167.5 44686.88 L 62171 44688.63 L 62174.5 44686.88 Z" fill="#000000" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 62118.5 44751.7 C 62134.62 44757.91 62152.38 44757.91 62168.5 44751.7 C 62184.62 44745.5 62202.38 44745.5 62218.5 44751.7 L 62218.5 44804.28 C 62202.38 44798.08 62184.62 44798.08 62168.5 44804.28 C 62152.38 44810.49 62134.62 44810.49 62118.5 44804.28 L 62118.5 44751.7 Z" fill="#7ea6e0" stroke="#000000" stroke-width="2" stroke-miterlimit="10" pointer-events="none"/>
touchpad: disable tapping for fingers exceeding the timeout/motion threshold The current code triggers multi-finger tapping even if the finger released was previously held on the touchpad for a while. For an event sequence of: 1. first finger down 2. first finger move past threshold/wait past timeout 3. second finger down 4. first finger up The second finger initiates the two-finger tap state, but the button event is sent when the first finger releases - despite that finger not meeting the usual tap constraints. This sequence can happen whenever a user swaps fingers. Add the finger state to the actual touchpoints and update them whenever the constrains are broken. Then, discard button events if the respective touch did not meet the conditions. http://bugs.freedesktop.org/76760 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2014-06-20 14:16:13 +10:00
<g fill="#000000" font-family="Helvetica" text-anchor="middle" font-size="12px">
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<text x="62168.25" y="44781.75">
touchpad: end tap-and-drag with an extra tap Currently for the tap-and-drag gesture to end user has to wait for a timeout to expire. Make it possible to end the drag gesture by just tapping. The allowed finger sequences to start and end a drag are thus: tap, down, .... move ...., up <wait for timeout> tap, down, .... move ...., up, tap https://bugs.freedesktop.org/show_bug.cgi?id=90255 Signed-off-by: Velimir Lisec <lisec.velimir@gmail.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> State diagram changes and a doc change squashed in. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-04-30 00:13:51 +02:00
TOUCH_DEAD</text>
touchpad: disable tapping for fingers exceeding the timeout/motion threshold The current code triggers multi-finger tapping even if the finger released was previously held on the touchpad for a while. For an event sequence of: 1. first finger down 2. first finger move past threshold/wait past timeout 3. second finger down 4. first finger up The second finger initiates the two-finger tap state, but the button event is sent when the first finger releases - despite that finger not meeting the usual tap constraints. This sequence can happen whenever a user swaps fingers. Add the finger state to the actual touchpoints and update them whenever the constrains are broken. Then, discard button events if the respective touch did not meet the conditions. http://bugs.freedesktop.org/76760 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2014-06-20 14:16:13 +10:00
</g>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<path d="M 62118.5 44801.7 C 62134.62 44807.91 62152.38 44807.91 62168.5 44801.7 C 62184.62 44795.5 62202.38 44795.5 62218.5 44801.7 L 62218.5 44854.28 C 62202.38 44848.08 62184.62 44848.08 62168.5 44854.28 C 62152.38 44860.49 62134.62 44860.49 62118.5 44854.28 L 62118.5 44801.7 Z" fill="#ffb570" stroke="#000000" stroke-width="2" stroke-miterlimit="10" pointer-events="none"/>
touchpad: disable tapping for fingers exceeding the timeout/motion threshold The current code triggers multi-finger tapping even if the finger released was previously held on the touchpad for a while. For an event sequence of: 1. first finger down 2. first finger move past threshold/wait past timeout 3. second finger down 4. first finger up The second finger initiates the two-finger tap state, but the button event is sent when the first finger releases - despite that finger not meeting the usual tap constraints. This sequence can happen whenever a user swaps fingers. Add the finger state to the actual touchpoints and update them whenever the constrains are broken. Then, discard button events if the respective touch did not meet the conditions. http://bugs.freedesktop.org/76760 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2014-06-20 14:16:13 +10:00
<g fill="#000000" font-family="Helvetica" text-anchor="middle" font-size="12px">
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<text x="62168.25" y="44831.75">
touchpad: end tap-and-drag with an extra tap Currently for the tap-and-drag gesture to end user has to wait for a timeout to expire. Make it possible to end the drag gesture by just tapping. The allowed finger sequences to start and end a drag are thus: tap, down, .... move ...., up <wait for timeout> tap, down, .... move ...., up, tap https://bugs.freedesktop.org/show_bug.cgi?id=90255 Signed-off-by: Velimir Lisec <lisec.velimir@gmail.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> State diagram changes and a doc change squashed in. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-04-30 00:13:51 +02:00
TOUCH_DEAD</text>
touchpad: disable tapping for fingers exceeding the timeout/motion threshold The current code triggers multi-finger tapping even if the finger released was previously held on the touchpad for a while. For an event sequence of: 1. first finger down 2. first finger move past threshold/wait past timeout 3. second finger down 4. first finger up The second finger initiates the two-finger tap state, but the button event is sent when the first finger releases - despite that finger not meeting the usual tap constraints. This sequence can happen whenever a user swaps fingers. Add the finger state to the actual touchpoints and update them whenever the constrains are broken. Then, discard button events if the respective touch did not meet the conditions. http://bugs.freedesktop.org/76760 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2014-06-20 14:16:13 +10:00
</g>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<path d="M 60202 44982.2 C 60218.12 44988.41 60235.88 44988.41 60252 44982.2 C 60268.12 44976 60285.88 44976 60302 44982.2 L 60302 45034.78 C 60285.88 45028.58 60268.12 45028.58 60252 45034.78 C 60235.88 45040.99 60218.12 45040.99 60202 45034.78 L 60202 44982.2 Z" fill="#ffd966" stroke="#000000" stroke-width="2" stroke-miterlimit="10" pointer-events="none"/>
touchpad: disable tapping for fingers exceeding the timeout/motion threshold The current code triggers multi-finger tapping even if the finger released was previously held on the touchpad for a while. For an event sequence of: 1. first finger down 2. first finger move past threshold/wait past timeout 3. second finger down 4. first finger up The second finger initiates the two-finger tap state, but the button event is sent when the first finger releases - despite that finger not meeting the usual tap constraints. This sequence can happen whenever a user swaps fingers. Add the finger state to the actual touchpoints and update them whenever the constrains are broken. Then, discard button events if the respective touch did not meet the conditions. http://bugs.freedesktop.org/76760 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2014-06-20 14:16:13 +10:00
<g fill="#000000" font-family="Helvetica" text-anchor="middle" font-size="12px">
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<text x="60251.75" y="45012.25">
touchpad: end tap-and-drag with an extra tap Currently for the tap-and-drag gesture to end user has to wait for a timeout to expire. Make it possible to end the drag gesture by just tapping. The allowed finger sequences to start and end a drag are thus: tap, down, .... move ...., up <wait for timeout> tap, down, .... move ...., up, tap https://bugs.freedesktop.org/show_bug.cgi?id=90255 Signed-off-by: Velimir Lisec <lisec.velimir@gmail.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> State diagram changes and a doc change squashed in. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-04-30 00:13:51 +02:00
TOUCH_DEAD</text>
touchpad: disable tapping for fingers exceeding the timeout/motion threshold The current code triggers multi-finger tapping even if the finger released was previously held on the touchpad for a while. For an event sequence of: 1. first finger down 2. first finger move past threshold/wait past timeout 3. second finger down 4. first finger up The second finger initiates the two-finger tap state, but the button event is sent when the first finger releases - despite that finger not meeting the usual tap constraints. This sequence can happen whenever a user swaps fingers. Add the finger state to the actual touchpoints and update them whenever the constrains are broken. Then, discard button events if the respective touch did not meet the conditions. http://bugs.freedesktop.org/76760 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2014-06-20 14:16:13 +10:00
</g>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<path d="M 59819 44993.68 L 60195.64 45006.57" fill="none" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 60200.88 45006.75 L 60193.77 45010.01 L 60195.64 45006.57 L 60194.01 45003.01 Z" fill="#000000" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 60344.5 45035.7 C 60360.62 45041.91 60378.38 45041.91 60394.5 45035.7 C 60410.62 45029.5 60428.38 45029.5 60444.5 45035.7 L 60444.5 45088.28 C 60428.38 45082.08 60410.62 45082.08 60394.5 45088.28 C 60378.38 45094.49 60360.62 45094.49 60344.5 45088.28 L 60344.5 45035.7 Z" fill="#7ea6e0" stroke="#000000" stroke-width="2" stroke-miterlimit="10" pointer-events="none"/>
touchpad: disable tapping for fingers exceeding the timeout/motion threshold The current code triggers multi-finger tapping even if the finger released was previously held on the touchpad for a while. For an event sequence of: 1. first finger down 2. first finger move past threshold/wait past timeout 3. second finger down 4. first finger up The second finger initiates the two-finger tap state, but the button event is sent when the first finger releases - despite that finger not meeting the usual tap constraints. This sequence can happen whenever a user swaps fingers. Add the finger state to the actual touchpoints and update them whenever the constrains are broken. Then, discard button events if the respective touch did not meet the conditions. http://bugs.freedesktop.org/76760 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2014-06-20 14:16:13 +10:00
<g fill="#000000" font-family="Helvetica" text-anchor="middle" font-size="12px">
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<text x="60394.25" y="45065.75">
touchpad: end tap-and-drag with an extra tap Currently for the tap-and-drag gesture to end user has to wait for a timeout to expire. Make it possible to end the drag gesture by just tapping. The allowed finger sequences to start and end a drag are thus: tap, down, .... move ...., up <wait for timeout> tap, down, .... move ...., up, tap https://bugs.freedesktop.org/show_bug.cgi?id=90255 Signed-off-by: Velimir Lisec <lisec.velimir@gmail.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> State diagram changes and a doc change squashed in. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-04-30 00:13:51 +02:00
TOUCH_DEAD</text>
touchpad: disable tapping for fingers exceeding the timeout/motion threshold The current code triggers multi-finger tapping even if the finger released was previously held on the touchpad for a while. For an event sequence of: 1. first finger down 2. first finger move past threshold/wait past timeout 3. second finger down 4. first finger up The second finger initiates the two-finger tap state, but the button event is sent when the first finger releases - despite that finger not meeting the usual tap constraints. This sequence can happen whenever a user swaps fingers. Add the finger state to the actual touchpoints and update them whenever the constrains are broken. Then, discard button events if the respective touch did not meet the conditions. http://bugs.freedesktop.org/76760 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2014-06-20 14:16:13 +10:00
</g>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<path d="M 60302 45027.27 L 60338.54 45040.99" fill="none" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 60343.45 45042.84 L 60335.67 45043.65 L 60338.54 45040.99 L 60338.13 45037.1 Z" fill="#000000" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 60469.5 45080.7 C 60485.62 45086.91 60503.38 45086.91 60519.5 45080.7 C 60535.62 45074.5 60553.38 45074.5 60569.5 45080.7 L 60569.5 45133.28 C 60553.38 45127.08 60535.62 45127.08 60519.5 45133.28 C 60503.38 45139.49 60485.62 45139.49 60469.5 45133.28 L 60469.5 45080.7 Z" fill="#ffb570" stroke="#000000" stroke-width="2" stroke-miterlimit="10" pointer-events="none"/>
touchpad: disable tapping for fingers exceeding the timeout/motion threshold The current code triggers multi-finger tapping even if the finger released was previously held on the touchpad for a while. For an event sequence of: 1. first finger down 2. first finger move past threshold/wait past timeout 3. second finger down 4. first finger up The second finger initiates the two-finger tap state, but the button event is sent when the first finger releases - despite that finger not meeting the usual tap constraints. This sequence can happen whenever a user swaps fingers. Add the finger state to the actual touchpoints and update them whenever the constrains are broken. Then, discard button events if the respective touch did not meet the conditions. http://bugs.freedesktop.org/76760 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2014-06-20 14:16:13 +10:00
<g fill="#000000" font-family="Helvetica" text-anchor="middle" font-size="12px">
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<text x="60519.25" y="45110.75">
touchpad: end tap-and-drag with an extra tap Currently for the tap-and-drag gesture to end user has to wait for a timeout to expire. Make it possible to end the drag gesture by just tapping. The allowed finger sequences to start and end a drag are thus: tap, down, .... move ...., up <wait for timeout> tap, down, .... move ...., up, tap https://bugs.freedesktop.org/show_bug.cgi?id=90255 Signed-off-by: Velimir Lisec <lisec.velimir@gmail.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> State diagram changes and a doc change squashed in. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-04-30 00:13:51 +02:00
TOUCH_DEAD</text>
touchpad: disable tapping for fingers exceeding the timeout/motion threshold The current code triggers multi-finger tapping even if the finger released was previously held on the touchpad for a while. For an event sequence of: 1. first finger down 2. first finger move past threshold/wait past timeout 3. second finger down 4. first finger up The second finger initiates the two-finger tap state, but the button event is sent when the first finger releases - despite that finger not meeting the usual tap constraints. This sequence can happen whenever a user swaps fingers. Add the finger state to the actual touchpoints and update them whenever the constrains are broken. Then, discard button events if the respective touch did not meet the conditions. http://bugs.freedesktop.org/76760 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2014-06-20 14:16:13 +10:00
</g>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<path d="M 60444.5 45080 L 60463.51 45086.84" fill="none" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 60468.45 45088.62 L 60460.68 45089.54 L 60463.51 45086.84 L 60463.05 45082.96 Z" fill="#000000" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 61302.5 44500 L 61366 44550 L 61302.5 44600 L 61239 44550 Z" fill="#e1d5e7" stroke="#000000" stroke-width="2" stroke-miterlimit="10" pointer-events="none"/>
touchpad: disable tapping for fingers exceeding the timeout/motion threshold The current code triggers multi-finger tapping even if the finger released was previously held on the touchpad for a while. For an event sequence of: 1. first finger down 2. first finger move past threshold/wait past timeout 3. second finger down 4. first finger up The second finger initiates the two-finger tap state, but the button event is sent when the first finger releases - despite that finger not meeting the usual tap constraints. This sequence can happen whenever a user swaps fingers. Add the finger state to the actual touchpoints and update them whenever the constrains are broken. Then, discard button events if the respective touch did not meet the conditions. http://bugs.freedesktop.org/76760 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2014-06-20 14:16:13 +10:00
<g fill="#000000" font-family="Helvetica" text-anchor="middle" font-size="12px">
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<text x="61302.25" y="44546.75">
touchpad: end tap-and-drag with an extra tap Currently for the tap-and-drag gesture to end user has to wait for a timeout to expire. Make it possible to end the drag gesture by just tapping. The allowed finger sequences to start and end a drag are thus: tap, down, .... move ...., up <wait for timeout> tap, down, .... move ...., up, tap https://bugs.freedesktop.org/show_bug.cgi?id=90255 Signed-off-by: Velimir Lisec <lisec.velimir@gmail.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> State diagram changes and a doc change squashed in. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-04-30 00:13:51 +02:00
that finger state ==</text>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<text x="61302.25" y="44560.75">
touchpad: end tap-and-drag with an extra tap Currently for the tap-and-drag gesture to end user has to wait for a timeout to expire. Make it possible to end the drag gesture by just tapping. The allowed finger sequences to start and end a drag are thus: tap, down, .... move ...., up <wait for timeout> tap, down, .... move ...., up, tap https://bugs.freedesktop.org/show_bug.cgi?id=90255 Signed-off-by: Velimir Lisec <lisec.velimir@gmail.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> State diagram changes and a doc change squashed in. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-04-30 00:13:51 +02:00
TOUCH_TOUCH</text>
touchpad: disable tapping for fingers exceeding the timeout/motion threshold The current code triggers multi-finger tapping even if the finger released was previously held on the touchpad for a while. For an event sequence of: 1. first finger down 2. first finger move past threshold/wait past timeout 3. second finger down 4. first finger up The second finger initiates the two-finger tap state, but the button event is sent when the first finger releases - despite that finger not meeting the usual tap constraints. This sequence can happen whenever a user swaps fingers. Add the finger state to the actual touchpoints and update them whenever the constrains are broken. Then, discard button events if the respective touch did not meet the conditions. http://bugs.freedesktop.org/76760 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2014-06-20 14:16:13 +10:00
</g>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<path d="M 61712.5 43863.7 C 61728.62 43869.91 61746.38 43869.91 61762.5 43863.7 C 61778.62 43857.5 61796.38 43857.5 61812.5 43863.7 L 61812.5 43916.28 C 61796.38 43910.08 61778.62 43910.08 61762.5 43916.28 C 61746.38 43922.49 61728.62 43922.49 61712.5 43916.28 L 61712.5 43863.7 Z" fill="#ffd966" stroke="#000000" stroke-width="2" stroke-miterlimit="10" pointer-events="none"/>
touchpad: disable tapping for fingers exceeding the timeout/motion threshold The current code triggers multi-finger tapping even if the finger released was previously held on the touchpad for a while. For an event sequence of: 1. first finger down 2. first finger move past threshold/wait past timeout 3. second finger down 4. first finger up The second finger initiates the two-finger tap state, but the button event is sent when the first finger releases - despite that finger not meeting the usual tap constraints. This sequence can happen whenever a user swaps fingers. Add the finger state to the actual touchpoints and update them whenever the constrains are broken. Then, discard button events if the respective touch did not meet the conditions. http://bugs.freedesktop.org/76760 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2014-06-20 14:16:13 +10:00
<g fill="#000000" font-family="Helvetica" text-anchor="middle" font-size="12px">
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<text x="61762.25" y="43893.75">
touchpad: end tap-and-drag with an extra tap Currently for the tap-and-drag gesture to end user has to wait for a timeout to expire. Make it possible to end the drag gesture by just tapping. The allowed finger sequences to start and end a drag are thus: tap, down, .... move ...., up <wait for timeout> tap, down, .... move ...., up, tap https://bugs.freedesktop.org/show_bug.cgi?id=90255 Signed-off-by: Velimir Lisec <lisec.velimir@gmail.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> State diagram changes and a doc change squashed in. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-04-30 00:13:51 +02:00
TOUCH_DEAD</text>
touchpad: disable tapping for fingers exceeding the timeout/motion threshold The current code triggers multi-finger tapping even if the finger released was previously held on the touchpad for a while. For an event sequence of: 1. first finger down 2. first finger move past threshold/wait past timeout 3. second finger down 4. first finger up The second finger initiates the two-finger tap state, but the button event is sent when the first finger releases - despite that finger not meeting the usual tap constraints. This sequence can happen whenever a user swaps fingers. Add the finger state to the actual touchpoints and update them whenever the constrains are broken. Then, discard button events if the respective touch did not meet the conditions. http://bugs.freedesktop.org/76760 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2014-06-20 14:16:13 +10:00
</g>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<path d="M 61761.5 43857.5 L 61761.5 43857.5" fill="none" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 61761.5 43857.5 L 61761.5 43857.5 L 61761.5 43857.5 L 61761.5 43857.5 Z" fill="#000000" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 61457.5 44562.7 C 61473.62 44568.91 61491.38 44568.91 61507.5 44562.7 C 61523.62 44556.5 61541.38 44556.5 61557.5 44562.7 L 61557.5 44615.28 C 61541.38 44609.08 61523.62 44609.08 61507.5 44615.28 C 61491.38 44621.49 61473.62 44621.49 61457.5 44615.28 L 61457.5 44562.7 Z" fill="#7ea6e0" stroke="#000000" stroke-width="2" stroke-miterlimit="10" pointer-events="none"/>
touchpad: disable tapping for fingers exceeding the timeout/motion threshold The current code triggers multi-finger tapping even if the finger released was previously held on the touchpad for a while. For an event sequence of: 1. first finger down 2. first finger move past threshold/wait past timeout 3. second finger down 4. first finger up The second finger initiates the two-finger tap state, but the button event is sent when the first finger releases - despite that finger not meeting the usual tap constraints. This sequence can happen whenever a user swaps fingers. Add the finger state to the actual touchpoints and update them whenever the constrains are broken. Then, discard button events if the respective touch did not meet the conditions. http://bugs.freedesktop.org/76760 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2014-06-20 14:16:13 +10:00
<g fill="#000000" font-family="Helvetica" text-anchor="middle" font-size="12px">
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<text x="61507.25" y="44592.75">
touchpad: end tap-and-drag with an extra tap Currently for the tap-and-drag gesture to end user has to wait for a timeout to expire. Make it possible to end the drag gesture by just tapping. The allowed finger sequences to start and end a drag are thus: tap, down, .... move ...., up <wait for timeout> tap, down, .... move ...., up, tap https://bugs.freedesktop.org/show_bug.cgi?id=90255 Signed-off-by: Velimir Lisec <lisec.velimir@gmail.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> State diagram changes and a doc change squashed in. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-04-30 00:13:51 +02:00
TOUCH_DEAD</text>
touchpad: disable tapping for fingers exceeding the timeout/motion threshold The current code triggers multi-finger tapping even if the finger released was previously held on the touchpad for a while. For an event sequence of: 1. first finger down 2. first finger move past threshold/wait past timeout 3. second finger down 4. first finger up The second finger initiates the two-finger tap state, but the button event is sent when the first finger releases - despite that finger not meeting the usual tap constraints. This sequence can happen whenever a user swaps fingers. Add the finger state to the actual touchpoints and update them whenever the constrains are broken. Then, discard button events if the respective touch did not meet the conditions. http://bugs.freedesktop.org/76760 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2014-06-20 14:16:13 +10:00
</g>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<path d="M 61457.5 44614.7 C 61473.62 44620.91 61491.38 44620.91 61507.5 44614.7 C 61523.62 44608.5 61541.38 44608.5 61557.5 44614.7 L 61557.5 44667.28 C 61541.38 44661.08 61523.62 44661.08 61507.5 44667.28 C 61491.38 44673.49 61473.62 44673.49 61457.5 44667.28 L 61457.5 44614.7 Z" fill="#ffd966" stroke="#000000" stroke-width="2" stroke-miterlimit="10" pointer-events="none"/>
touchpad: disable tapping for fingers exceeding the timeout/motion threshold The current code triggers multi-finger tapping even if the finger released was previously held on the touchpad for a while. For an event sequence of: 1. first finger down 2. first finger move past threshold/wait past timeout 3. second finger down 4. first finger up The second finger initiates the two-finger tap state, but the button event is sent when the first finger releases - despite that finger not meeting the usual tap constraints. This sequence can happen whenever a user swaps fingers. Add the finger state to the actual touchpoints and update them whenever the constrains are broken. Then, discard button events if the respective touch did not meet the conditions. http://bugs.freedesktop.org/76760 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2014-06-20 14:16:13 +10:00
<g fill="#000000" font-family="Helvetica" text-anchor="middle" font-size="12px">
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<text x="61507.25" y="44644.75">
touchpad: end tap-and-drag with an extra tap Currently for the tap-and-drag gesture to end user has to wait for a timeout to expire. Make it possible to end the drag gesture by just tapping. The allowed finger sequences to start and end a drag are thus: tap, down, .... move ...., up <wait for timeout> tap, down, .... move ...., up, tap https://bugs.freedesktop.org/show_bug.cgi?id=90255 Signed-off-by: Velimir Lisec <lisec.velimir@gmail.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> State diagram changes and a doc change squashed in. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-04-30 00:13:51 +02:00
TOUCH_DEAD</text>
touchpad: disable tapping for fingers exceeding the timeout/motion threshold The current code triggers multi-finger tapping even if the finger released was previously held on the touchpad for a while. For an event sequence of: 1. first finger down 2. first finger move past threshold/wait past timeout 3. second finger down 4. first finger up The second finger initiates the two-finger tap state, but the button event is sent when the first finger releases - despite that finger not meeting the usual tap constraints. This sequence can happen whenever a user swaps fingers. Add the finger state to the actual touchpoints and update them whenever the constrains are broken. Then, discard button events if the respective touch did not meet the conditions. http://bugs.freedesktop.org/76760 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2014-06-20 14:16:13 +10:00
</g>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<path d="M 59723.54 43752 C 59726.34 43748.86 59730.32 43747.05 59734.52 43747 L 59768.49 43747 C 59772.69 43747.05 59776.67 43748.86 59779.47 43752 L 59799.45 43775 C 59800.01 43776.28 59800.01 43777.72 59799.45 43779 L 59779.47 43802 C 59776.67 43805.14 59772.69 43806.95 59768.49 43807 L 59734.52 43807 C 59730.32 43806.95 59726.34 43805.14 59723.54 43802 L 59703.56 43779 C 59703 43777.72 59703 43776.28 59703.56 43775 L 59723.54 43752 Z" fill="#ffd966" stroke="#000000" stroke-width="2" stroke-miterlimit="10" pointer-events="none"/>
touchpad: disable tapping for fingers exceeding the timeout/motion threshold The current code triggers multi-finger tapping even if the finger released was previously held on the touchpad for a while. For an event sequence of: 1. first finger down 2. first finger move past threshold/wait past timeout 3. second finger down 4. first finger up The second finger initiates the two-finger tap state, but the button event is sent when the first finger releases - despite that finger not meeting the usual tap constraints. This sequence can happen whenever a user swaps fingers. Add the finger state to the actual touchpoints and update them whenever the constrains are broken. Then, discard button events if the respective touch did not meet the conditions. http://bugs.freedesktop.org/76760 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2014-06-20 14:16:13 +10:00
<g fill="#000000" font-family="Helvetica" text-anchor="middle" font-size="12px">
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<text x="59751.25" y="43773.75">
touchpad: end tap-and-drag with an extra tap Currently for the tap-and-drag gesture to end user has to wait for a timeout to expire. Make it possible to end the drag gesture by just tapping. The allowed finger sequences to start and end a drag are thus: tap, down, .... move ...., up <wait for timeout> tap, down, .... move ...., up, tap https://bugs.freedesktop.org/show_bug.cgi?id=90255 Signed-off-by: Velimir Lisec <lisec.velimir@gmail.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> State diagram changes and a doc change squashed in. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-04-30 00:13:51 +02:00
first</text>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<text x="59751.25" y="43787.75">
touchpad: end tap-and-drag with an extra tap Currently for the tap-and-drag gesture to end user has to wait for a timeout to expire. Make it possible to end the drag gesture by just tapping. The allowed finger sequences to start and end a drag are thus: tap, down, .... move ...., up <wait for timeout> tap, down, .... move ...., up, tap https://bugs.freedesktop.org/show_bug.cgi?id=90255 Signed-off-by: Velimir Lisec <lisec.velimir@gmail.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> State diagram changes and a doc change squashed in. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-04-30 00:13:51 +02:00
finger down</text>
touchpad: disable tapping for fingers exceeding the timeout/motion threshold The current code triggers multi-finger tapping even if the finger released was previously held on the touchpad for a while. For an event sequence of: 1. first finger down 2. first finger move past threshold/wait past timeout 3. second finger down 4. first finger up The second finger initiates the two-finger tap state, but the button event is sent when the first finger releases - despite that finger not meeting the usual tap constraints. This sequence can happen whenever a user swaps fingers. Add the finger state to the actual touchpoints and update them whenever the constrains are broken. Then, discard button events if the respective touch did not meet the conditions. http://bugs.freedesktop.org/76760 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2014-06-20 14:16:13 +10:00
</g>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<rect x="59760.5" y="43912" width="209" height="40" rx="2.4" ry="2.4" fill="#ccffcc" stroke="#000000" stroke-width="2" pointer-events="none"/>
touchpad: disable tapping for fingers exceeding the timeout/motion threshold The current code triggers multi-finger tapping even if the finger released was previously held on the touchpad for a while. For an event sequence of: 1. first finger down 2. first finger move past threshold/wait past timeout 3. second finger down 4. first finger up The second finger initiates the two-finger tap state, but the button event is sent when the first finger releases - despite that finger not meeting the usual tap constraints. This sequence can happen whenever a user swaps fingers. Add the finger state to the actual touchpoints and update them whenever the constrains are broken. Then, discard button events if the respective touch did not meet the conditions. http://bugs.freedesktop.org/76760 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2014-06-20 14:16:13 +10:00
<g fill="#000000" font-family="Helvetica" text-anchor="middle" font-size="12px">
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<text x="59864.75" y="43935.75">
touchpad: end tap-and-drag with an extra tap Currently for the tap-and-drag gesture to end user has to wait for a timeout to expire. Make it possible to end the drag gesture by just tapping. The allowed finger sequences to start and end a drag are thus: tap, down, .... move ...., up <wait for timeout> tap, down, .... move ...., up, tap https://bugs.freedesktop.org/show_bug.cgi?id=90255 Signed-off-by: Velimir Lisec <lisec.velimir@gmail.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> State diagram changes and a doc change squashed in. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-04-30 00:13:51 +02:00
MULTITAP</text>
touchpad: disable tapping for fingers exceeding the timeout/motion threshold The current code triggers multi-finger tapping even if the finger released was previously held on the touchpad for a while. For an event sequence of: 1. first finger down 2. first finger move past threshold/wait past timeout 3. second finger down 4. first finger up The second finger initiates the two-finger tap state, but the button event is sent when the first finger releases - despite that finger not meeting the usual tap constraints. This sequence can happen whenever a user swaps fingers. Add the finger state to the actual touchpoints and update them whenever the constrains are broken. Then, discard button events if the respective touch did not meet the conditions. http://bugs.freedesktop.org/76760 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2014-06-20 14:16:13 +10:00
</g>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<path d="M 59954.49 43873 L 59900.65 43908.49" fill="none" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 59896.27 43911.38 L 59900.19 43904.61 L 59900.65 43908.49 L 59904.04 43910.45 Z" fill="#000000" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 59850.35 43912 L 59777.23 43812.14" fill="none" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 59774.13 43807.9 L 59781.09 43811.48 L 59777.23 43812.14 L 59775.44 43815.62 Z" fill="#000000" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 59811.54 44032 C 59814.34 44028.86 59818.32 44027.05 59822.52 44027 L 59856.49 44027 C 59860.69 44027.05 59864.67 44028.86 59867.47 44032 L 59887.45 44055 C 59888.01 44056.28 59888.01 44057.72 59887.45 44059 L 59867.47 44082 C 59864.67 44085.14 59860.69 44086.95 59856.49 44087 L 59822.52 44087 C 59818.32 44086.95 59814.34 44085.14 59811.54 44082 L 59791.56 44059 C 59791 44057.72 59791 44056.28 59791.56 44055 L 59811.54 44032 Z" fill="#ffd966" stroke="#000000" stroke-width="2" stroke-miterlimit="10" pointer-events="none"/>
touchpad: disable tapping for fingers exceeding the timeout/motion threshold The current code triggers multi-finger tapping even if the finger released was previously held on the touchpad for a while. For an event sequence of: 1. first finger down 2. first finger move past threshold/wait past timeout 3. second finger down 4. first finger up The second finger initiates the two-finger tap state, but the button event is sent when the first finger releases - despite that finger not meeting the usual tap constraints. This sequence can happen whenever a user swaps fingers. Add the finger state to the actual touchpoints and update them whenever the constrains are broken. Then, discard button events if the respective touch did not meet the conditions. http://bugs.freedesktop.org/76760 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2014-06-20 14:16:13 +10:00
<g fill="#000000" font-family="Helvetica" text-anchor="middle" font-size="12px">
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<text x="59839.25" y="44060.75">
touchpad: end tap-and-drag with an extra tap Currently for the tap-and-drag gesture to end user has to wait for a timeout to expire. Make it possible to end the drag gesture by just tapping. The allowed finger sequences to start and end a drag are thus: tap, down, .... move ...., up <wait for timeout> tap, down, .... move ...., up, tap https://bugs.freedesktop.org/show_bug.cgi?id=90255 Signed-off-by: Velimir Lisec <lisec.velimir@gmail.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> State diagram changes and a doc change squashed in. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-04-30 00:13:51 +02:00
timeout</text>
touchpad: introduce MULTITAP for multi-tap-and-drag Once we have a doubletap, enter a loop in the state machine where we can tap multiple times and either get a multi-click or a multi-click drag-and-drop. The sequence down/up down/up down/up produces a triple-click. The sequence down/up down/up down/up down produces a triple-click with a button down for dragging. Yes, that glorious octuple-tap-and-drag, it is now possible. World domination has been achieved, thank you for playing. We don't know when we finish tapping now, so add a timeout to send the last click event once the finger has been released for the last time. This guarantees that the timestamp of the last button down is later than the last release. This avoids the bug fixed in synaptics commit xf86-input-synaptics-1.8.0-21-g37d34f0 (some application don't handle doubletap correctly without the timestamps). This works for double-tap immediately, for multi-tap we need to remember the timestamp of the first press event and use it for the release event so that there's a forced gap between the release and the second press. https://bugs.freedesktop.org/show_bug.cgi?id=89511 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-04-16 10:19:11 +10:00
</g>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<path d="M 59818.26 44087 L 59775.92 44146.8" fill="none" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 59772.89 44151.09 L 59774.07 44143.35 L 59775.92 44146.8 L 59779.79 44147.4 Z" fill="#000000" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 59860.92 43952 L 59846.89 44020.76" fill="none" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 59845.84 44025.9 L 59843.81 44018.35 L 59846.89 44020.76 L 59850.67 44019.75 Z" fill="#000000" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<ellipse cx="59752" cy="44452" rx="49.5" ry="30" fill="#ccccff" stroke="#000000" stroke-width="2" pointer-events="none"/>
touchpad: introduce MULTITAP for multi-tap-and-drag Once we have a doubletap, enter a loop in the state machine where we can tap multiple times and either get a multi-click or a multi-click drag-and-drop. The sequence down/up down/up down/up produces a triple-click. The sequence down/up down/up down/up down produces a triple-click with a button down for dragging. Yes, that glorious octuple-tap-and-drag, it is now possible. World domination has been achieved, thank you for playing. We don't know when we finish tapping now, so add a timeout to send the last click event once the finger has been released for the last time. This guarantees that the timestamp of the last button down is later than the last release. This avoids the bug fixed in synaptics commit xf86-input-synaptics-1.8.0-21-g37d34f0 (some application don't handle doubletap correctly without the timestamps). This works for double-tap immediately, for multi-tap we need to remember the timestamp of the first press event and use it for the release event so that there's a forced gap between the release and the second press. https://bugs.freedesktop.org/show_bug.cgi?id=89511 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-04-16 10:19:11 +10:00
<g fill="#000000" font-family="Helvetica" text-anchor="middle" font-size="12px">
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<text x="59751.25" y="44455.75">
touchpad: end tap-and-drag with an extra tap Currently for the tap-and-drag gesture to end user has to wait for a timeout to expire. Make it possible to end the drag gesture by just tapping. The allowed finger sequences to start and end a drag are thus: tap, down, .... move ...., up <wait for timeout> tap, down, .... move ...., up, tap https://bugs.freedesktop.org/show_bug.cgi?id=90255 Signed-off-by: Velimir Lisec <lisec.velimir@gmail.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> State diagram changes and a doc change squashed in. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-04-30 00:13:51 +02:00
IDLE</text>
touchpad: disable tapping for fingers exceeding the timeout/motion threshold The current code triggers multi-finger tapping even if the finger released was previously held on the touchpad for a while. For an event sequence of: 1. first finger down 2. first finger move past threshold/wait past timeout 3. second finger down 4. first finger up The second finger initiates the two-finger tap state, but the button event is sent when the first finger releases - despite that finger not meeting the usual tap constraints. This sequence can happen whenever a user swaps fingers. Add the finger state to the actual touchpoints and update them whenever the constrains are broken. Then, discard button events if the respective touch did not meet the conditions. http://bugs.freedesktop.org/76760 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2014-06-20 14:16:13 +10:00
</g>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<path d="M 59751.5 44352 L 59751.5 44415.63" fill="none" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 59751.5 44420.88 L 59748 44413.88 L 59751.5 44415.63 L 59755 44413.88 Z" fill="#000000" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 60093 43854.38 L 60055.32 43849.77" fill="none" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 60050.11 43849.13 L 60057.48 43846.51 L 60055.32 43849.77 L 60056.63 43853.46 Z" fill="#000000" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 60262.5 43883.62 L 60199.25 43871.38" fill="none" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 60194.1 43870.38 L 60201.63 43868.28 L 60199.25 43871.38 L 60200.31 43875.15 Z" fill="#000000" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<rect x="60120.5" y="43412" width="209" height="40" rx="2.4" ry="2.4" fill="#ccffcc" stroke="#000000" stroke-width="2" pointer-events="none"/>
touchpad: introduce MULTITAP for multi-tap-and-drag Once we have a doubletap, enter a loop in the state machine where we can tap multiple times and either get a multi-click or a multi-click drag-and-drop. The sequence down/up down/up down/up produces a triple-click. The sequence down/up down/up down/up down produces a triple-click with a button down for dragging. Yes, that glorious octuple-tap-and-drag, it is now possible. World domination has been achieved, thank you for playing. We don't know when we finish tapping now, so add a timeout to send the last click event once the finger has been released for the last time. This guarantees that the timestamp of the last button down is later than the last release. This avoids the bug fixed in synaptics commit xf86-input-synaptics-1.8.0-21-g37d34f0 (some application don't handle doubletap correctly without the timestamps). This works for double-tap immediately, for multi-tap we need to remember the timestamp of the first press event and use it for the release event so that there's a forced gap between the release and the second press. https://bugs.freedesktop.org/show_bug.cgi?id=89511 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-04-16 10:19:11 +10:00
<g fill="#000000" font-family="Helvetica" text-anchor="middle" font-size="12px">
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<text x="60224.75" y="43435.75">
touchpad: end tap-and-drag with an extra tap Currently for the tap-and-drag gesture to end user has to wait for a timeout to expire. Make it possible to end the drag gesture by just tapping. The allowed finger sequences to start and end a drag are thus: tap, down, .... move ...., up <wait for timeout> tap, down, .... move ...., up, tap https://bugs.freedesktop.org/show_bug.cgi?id=90255 Signed-off-by: Velimir Lisec <lisec.velimir@gmail.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> State diagram changes and a doc change squashed in. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-04-30 00:13:51 +02:00
MULTITAP_DOWN</text>
touchpad: introduce MULTITAP for multi-tap-and-drag Once we have a doubletap, enter a loop in the state machine where we can tap multiple times and either get a multi-click or a multi-click drag-and-drop. The sequence down/up down/up down/up produces a triple-click. The sequence down/up down/up down/up down produces a triple-click with a button down for dragging. Yes, that glorious octuple-tap-and-drag, it is now possible. World domination has been achieved, thank you for playing. We don't know when we finish tapping now, so add a timeout to send the last click event once the finger has been released for the last time. This guarantees that the timestamp of the last button down is later than the last release. This avoids the bug fixed in synaptics commit xf86-input-synaptics-1.8.0-21-g37d34f0 (some application don't handle doubletap correctly without the timestamps). This works for double-tap immediately, for multi-tap we need to remember the timestamp of the first press event and use it for the release event so that there's a forced gap between the release and the second press. https://bugs.freedesktop.org/show_bug.cgi?id=89511 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-04-16 10:19:11 +10:00
</g>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<path d="M 59872.22 43495.1 C 59873.36 43491.9 59875.22 43490.04 59877.18 43490.12 L 59945.64 43490.12 C 59947.2 43490.08 59948.7 43490.63 59949.67 43491.61 C 59950.65 43492.59 59950.99 43493.88 59950.6 43495.1 L 59931.75 43544.9 C 59930.61 43548.1 59928.75 43549.96 59926.79 43549.88 L 59857.34 43549.88 C 59855.95 43549.69 59854.73 43549.05 59853.97 43548.1 C 59853.22 43547.15 59853 43545.99 59853.37 43544.9 Z" fill="#ff6666" stroke="#000000" stroke-width="2" stroke-miterlimit="10" pointer-events="none"/>
touchpad: introduce MULTITAP for multi-tap-and-drag Once we have a doubletap, enter a loop in the state machine where we can tap multiple times and either get a multi-click or a multi-click drag-and-drop. The sequence down/up down/up down/up produces a triple-click. The sequence down/up down/up down/up down produces a triple-click with a button down for dragging. Yes, that glorious octuple-tap-and-drag, it is now possible. World domination has been achieved, thank you for playing. We don't know when we finish tapping now, so add a timeout to send the last click event once the finger has been released for the last time. This guarantees that the timestamp of the last button down is later than the last release. This avoids the bug fixed in synaptics commit xf86-input-synaptics-1.8.0-21-g37d34f0 (some application don't handle doubletap correctly without the timestamps). This works for double-tap immediately, for multi-tap we need to remember the timestamp of the first press event and use it for the release event so that there's a forced gap between the release and the second press. https://bugs.freedesktop.org/show_bug.cgi?id=89511 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-04-16 10:19:11 +10:00
<g fill="#000000" font-family="Helvetica" text-anchor="middle" font-size="12px">
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<text x="59901.75" y="43516.75">
touchpad: end tap-and-drag with an extra tap Currently for the tap-and-drag gesture to end user has to wait for a timeout to expire. Make it possible to end the drag gesture by just tapping. The allowed finger sequences to start and end a drag are thus: tap, down, .... move ...., up <wait for timeout> tap, down, .... move ...., up, tap https://bugs.freedesktop.org/show_bug.cgi?id=90255 Signed-off-by: Velimir Lisec <lisec.velimir@gmail.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> State diagram changes and a doc change squashed in. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-04-30 00:13:51 +02:00
button 1</text>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<text x="59901.75" y="43530.75">
touchpad: end tap-and-drag with an extra tap Currently for the tap-and-drag gesture to end user has to wait for a timeout to expire. Make it possible to end the drag gesture by just tapping. The allowed finger sequences to start and end a drag are thus: tap, down, .... move ...., up <wait for timeout> tap, down, .... move ...., up, tap https://bugs.freedesktop.org/show_bug.cgi?id=90255 Signed-off-by: Velimir Lisec <lisec.velimir@gmail.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> State diagram changes and a doc change squashed in. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-04-30 00:13:51 +02:00
press</text>
touchpad: introduce MULTITAP for multi-tap-and-drag Once we have a doubletap, enter a loop in the state machine where we can tap multiple times and either get a multi-click or a multi-click drag-and-drop. The sequence down/up down/up down/up produces a triple-click. The sequence down/up down/up down/up down produces a triple-click with a button down for dragging. Yes, that glorious octuple-tap-and-drag, it is now possible. World domination has been achieved, thank you for playing. We don't know when we finish tapping now, so add a timeout to send the last click event once the finger has been released for the last time. This guarantees that the timestamp of the last button down is later than the last release. This avoids the bug fixed in synaptics commit xf86-input-synaptics-1.8.0-21-g37d34f0 (some application don't handle doubletap correctly without the timestamps). This works for double-tap immediately, for multi-tap we need to remember the timestamp of the first press event and use it for the release event so that there's a forced gap between the release and the second press. https://bugs.freedesktop.org/show_bug.cgi?id=89511 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-04-16 10:19:11 +10:00
</g>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<path d="M 59790.17 43642.5 L 59870.32 43554.7" fill="none" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 59873.86 43550.83 L 59871.72 43558.36 L 59870.32 43554.7 L 59866.55 43553.64 Z" fill="#000000" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 59951 43506.65 L 60145.45 43453.67" fill="none" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 60150.51 43452.29 L 60144.68 43457.51 L 60145.45 43453.67 L 60142.84 43450.76 Z" fill="#000000" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 59972.54 43535 C 59975.34 43531.86 59979.32 43530.05 59983.52 43530 L 60017.49 43530 C 60021.69 43530.05 60025.67 43531.86 60028.47 43535 L 60048.45 43558 C 60049.01 43559.28 60049.01 43560.72 60048.45 43562 L 60028.47 43585 C 60025.67 43588.14 60021.69 43589.95 60017.49 43590 L 59983.52 43590 C 59979.32 43589.95 59975.34 43588.14 59972.54 43585 L 59952.56 43562 C 59952 43560.72 59952 43559.28 59952.56 43558 L 59972.54 43535 Z" fill="#ffd966" stroke="#000000" stroke-width="2" stroke-miterlimit="10" pointer-events="none"/>
touchpad: introduce MULTITAP for multi-tap-and-drag Once we have a doubletap, enter a loop in the state machine where we can tap multiple times and either get a multi-click or a multi-click drag-and-drop. The sequence down/up down/up down/up produces a triple-click. The sequence down/up down/up down/up down produces a triple-click with a button down for dragging. Yes, that glorious octuple-tap-and-drag, it is now possible. World domination has been achieved, thank you for playing. We don't know when we finish tapping now, so add a timeout to send the last click event once the finger has been released for the last time. This guarantees that the timestamp of the last button down is later than the last release. This avoids the bug fixed in synaptics commit xf86-input-synaptics-1.8.0-21-g37d34f0 (some application don't handle doubletap correctly without the timestamps). This works for double-tap immediately, for multi-tap we need to remember the timestamp of the first press event and use it for the release event so that there's a forced gap between the release and the second press. https://bugs.freedesktop.org/show_bug.cgi?id=89511 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-04-16 10:19:11 +10:00
<g fill="#000000" font-family="Helvetica" text-anchor="middle" font-size="12px">
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<text x="60000.25" y="43556.75">
touchpad: end tap-and-drag with an extra tap Currently for the tap-and-drag gesture to end user has to wait for a timeout to expire. Make it possible to end the drag gesture by just tapping. The allowed finger sequences to start and end a drag are thus: tap, down, .... move ...., up <wait for timeout> tap, down, .... move ...., up, tap https://bugs.freedesktop.org/show_bug.cgi?id=90255 Signed-off-by: Velimir Lisec <lisec.velimir@gmail.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> State diagram changes and a doc change squashed in. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-04-30 00:13:51 +02:00
first</text>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<text x="60000.25" y="43570.75">
touchpad: end tap-and-drag with an extra tap Currently for the tap-and-drag gesture to end user has to wait for a timeout to expire. Make it possible to end the drag gesture by just tapping. The allowed finger sequences to start and end a drag are thus: tap, down, .... move ...., up <wait for timeout> tap, down, .... move ...., up, tap https://bugs.freedesktop.org/show_bug.cgi?id=90255 Signed-off-by: Velimir Lisec <lisec.velimir@gmail.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> State diagram changes and a doc change squashed in. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-04-30 00:13:51 +02:00
finger up</text>
touchpad: introduce MULTITAP for multi-tap-and-drag Once we have a doubletap, enter a loop in the state machine where we can tap multiple times and either get a multi-click or a multi-click drag-and-drop. The sequence down/up down/up down/up produces a triple-click. The sequence down/up down/up down/up down produces a triple-click with a button down for dragging. Yes, that glorious octuple-tap-and-drag, it is now possible. World domination has been achieved, thank you for playing. We don't know when we finish tapping now, so add a timeout to send the last click event once the finger has been released for the last time. This guarantees that the timestamp of the last button down is later than the last release. This avoids the bug fixed in synaptics commit xf86-input-synaptics-1.8.0-21-g37d34f0 (some application don't handle doubletap correctly without the timestamps). This works for double-tap immediately, for multi-tap we need to remember the timestamp of the first press event and use it for the release event so that there's a forced gap between the release and the second press. https://bugs.freedesktop.org/show_bug.cgi?id=89511 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-04-16 10:19:11 +10:00
</g>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<path d="M 60189.92 43452 L 60054.53 43529.19" fill="none" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 60049.97 43531.79 L 60054.32 43525.29 L 60054.53 43529.19 L 60057.79 43531.37 Z" fill="#000000" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 59852.22 43760.1 C 59853.36 43756.9 59855.22 43755.04 59857.18 43755.12 L 59925.64 43755.12 C 59927.2 43755.08 59928.7 43755.63 59929.67 43756.61 C 59930.65 43757.59 59930.99 43758.88 59930.6 43760.1 L 59911.75 43809.9 C 59910.61 43813.1 59908.75 43814.96 59906.79 43814.88 L 59837.34 43814.88 C 59835.95 43814.69 59834.73 43814.05 59833.97 43813.1 C 59833.22 43812.15 59833 43810.99 59833.37 43809.9 Z" fill="#ff6666" stroke="#000000" stroke-width="2" stroke-miterlimit="10" pointer-events="none"/>
touchpad: introduce MULTITAP for multi-tap-and-drag Once we have a doubletap, enter a loop in the state machine where we can tap multiple times and either get a multi-click or a multi-click drag-and-drop. The sequence down/up down/up down/up produces a triple-click. The sequence down/up down/up down/up down produces a triple-click with a button down for dragging. Yes, that glorious octuple-tap-and-drag, it is now possible. World domination has been achieved, thank you for playing. We don't know when we finish tapping now, so add a timeout to send the last click event once the finger has been released for the last time. This guarantees that the timestamp of the last button down is later than the last release. This avoids the bug fixed in synaptics commit xf86-input-synaptics-1.8.0-21-g37d34f0 (some application don't handle doubletap correctly without the timestamps). This works for double-tap immediately, for multi-tap we need to remember the timestamp of the first press event and use it for the release event so that there's a forced gap between the release and the second press. https://bugs.freedesktop.org/show_bug.cgi?id=89511 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-04-16 10:19:11 +10:00
<g fill="#000000" font-family="Helvetica" text-anchor="middle" font-size="12px">
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<text x="59881.75" y="43781.75">
touchpad: end tap-and-drag with an extra tap Currently for the tap-and-drag gesture to end user has to wait for a timeout to expire. Make it possible to end the drag gesture by just tapping. The allowed finger sequences to start and end a drag are thus: tap, down, .... move ...., up <wait for timeout> tap, down, .... move ...., up, tap https://bugs.freedesktop.org/show_bug.cgi?id=90255 Signed-off-by: Velimir Lisec <lisec.velimir@gmail.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> State diagram changes and a doc change squashed in. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-04-30 00:13:51 +02:00
button 1</text>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<text x="59881.75" y="43795.75">
touchpad: end tap-and-drag with an extra tap Currently for the tap-and-drag gesture to end user has to wait for a timeout to expire. Make it possible to end the drag gesture by just tapping. The allowed finger sequences to start and end a drag are thus: tap, down, .... move ...., up <wait for timeout> tap, down, .... move ...., up, tap https://bugs.freedesktop.org/show_bug.cgi?id=90255 Signed-off-by: Velimir Lisec <lisec.velimir@gmail.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> State diagram changes and a doc change squashed in. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-04-30 00:13:51 +02:00
release</text>
touchpad: introduce MULTITAP for multi-tap-and-drag Once we have a doubletap, enter a loop in the state machine where we can tap multiple times and either get a multi-click or a multi-click drag-and-drop. The sequence down/up down/up down/up produces a triple-click. The sequence down/up down/up down/up down produces a triple-click with a button down for dragging. Yes, that glorious octuple-tap-and-drag, it is now possible. World domination has been achieved, thank you for playing. We don't know when we finish tapping now, so add a timeout to send the last click event once the finger has been released for the last time. This guarantees that the timestamp of the last button down is later than the last release. This avoids the bug fixed in synaptics commit xf86-input-synaptics-1.8.0-21-g37d34f0 (some application don't handle doubletap correctly without the timestamps). This works for double-tap immediately, for multi-tap we need to remember the timestamp of the first press event and use it for the release event so that there's a forced gap between the release and the second press. https://bugs.freedesktop.org/show_bug.cgi?id=89511 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-04-16 10:19:11 +10:00
</g>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<path d="M 59954.55 43697.5 L 59910.94 43750.1" fill="none" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 59907.59 43754.14 L 59909.36 43746.52 L 59910.94 43750.1 L 59914.75 43750.98 Z" fill="#000000" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 60261.54 43537 C 60264.34 43533.86 60268.32 43532.05 60272.52 43532 L 60306.49 43532 C 60310.69 43532.05 60314.67 43533.86 60317.47 43537 L 60337.45 43560 C 60338.01 43561.28 60338.01 43562.72 60337.45 43564 L 60317.47 43587 C 60314.67 43590.14 60310.69 43591.95 60306.49 43592 L 60272.52 43592 C 60268.32 43591.95 60264.34 43590.14 60261.54 43587 L 60241.56 43564 C 60241 43562.72 60241 43561.28 60241.56 43560 L 60261.54 43537 Z" fill="#99ffff" stroke="#000000" stroke-width="2" stroke-miterlimit="10" pointer-events="none"/>
touchpad: introduce MULTITAP for multi-tap-and-drag Once we have a doubletap, enter a loop in the state machine where we can tap multiple times and either get a multi-click or a multi-click drag-and-drop. The sequence down/up down/up down/up produces a triple-click. The sequence down/up down/up down/up down produces a triple-click with a button down for dragging. Yes, that glorious octuple-tap-and-drag, it is now possible. World domination has been achieved, thank you for playing. We don't know when we finish tapping now, so add a timeout to send the last click event once the finger has been released for the last time. This guarantees that the timestamp of the last button down is later than the last release. This avoids the bug fixed in synaptics commit xf86-input-synaptics-1.8.0-21-g37d34f0 (some application don't handle doubletap correctly without the timestamps). This works for double-tap immediately, for multi-tap we need to remember the timestamp of the first press event and use it for the release event so that there's a forced gap between the release and the second press. https://bugs.freedesktop.org/show_bug.cgi?id=89511 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-04-16 10:19:11 +10:00
<g fill="#000000" font-family="Helvetica" text-anchor="middle" font-size="12px">
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<text x="60289.25" y="43565.75">
touchpad: end tap-and-drag with an extra tap Currently for the tap-and-drag gesture to end user has to wait for a timeout to expire. Make it possible to end the drag gesture by just tapping. The allowed finger sequences to start and end a drag are thus: tap, down, .... move ...., up <wait for timeout> tap, down, .... move ...., up, tap https://bugs.freedesktop.org/show_bug.cgi?id=90255 Signed-off-by: Velimir Lisec <lisec.velimir@gmail.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> State diagram changes and a doc change squashed in. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-04-30 00:13:51 +02:00
timeout</text>
touchpad: introduce MULTITAP for multi-tap-and-drag Once we have a doubletap, enter a loop in the state machine where we can tap multiple times and either get a multi-click or a multi-click drag-and-drop. The sequence down/up down/up down/up produces a triple-click. The sequence down/up down/up down/up down produces a triple-click with a button down for dragging. Yes, that glorious octuple-tap-and-drag, it is now possible. World domination has been achieved, thank you for playing. We don't know when we finish tapping now, so add a timeout to send the last click event once the finger has been released for the last time. This guarantees that the timestamp of the last button down is later than the last release. This avoids the bug fixed in synaptics commit xf86-input-synaptics-1.8.0-21-g37d34f0 (some application don't handle doubletap correctly without the timestamps). This works for double-tap immediately, for multi-tap we need to remember the timestamp of the first press event and use it for the release event so that there's a forced gap between the release and the second press. https://bugs.freedesktop.org/show_bug.cgi?id=89511 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-04-16 10:19:11 +10:00
</g>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<path d="M 60384.54 43535 C 60387.34 43531.86 60391.32 43530.05 60395.52 43530 L 60429.49 43530 C 60433.69 43530.05 60437.67 43531.86 60440.47 43535 L 60460.45 43558 C 60461.01 43559.28 60461.01 43560.72 60460.45 43562 L 60440.47 43585 C 60437.67 43588.14 60433.69 43589.95 60429.49 43590 L 60395.52 43590 C 60391.32 43589.95 60387.34 43588.14 60384.54 43585 L 60364.56 43562 C 60364 43560.72 60364 43559.28 60364.56 43558 L 60384.54 43535 Z" fill="#7ea6e0" stroke="#000000" stroke-width="2" stroke-miterlimit="10" pointer-events="none"/>
touchpad: introduce MULTITAP for multi-tap-and-drag Once we have a doubletap, enter a loop in the state machine where we can tap multiple times and either get a multi-click or a multi-click drag-and-drop. The sequence down/up down/up down/up produces a triple-click. The sequence down/up down/up down/up down produces a triple-click with a button down for dragging. Yes, that glorious octuple-tap-and-drag, it is now possible. World domination has been achieved, thank you for playing. We don't know when we finish tapping now, so add a timeout to send the last click event once the finger has been released for the last time. This guarantees that the timestamp of the last button down is later than the last release. This avoids the bug fixed in synaptics commit xf86-input-synaptics-1.8.0-21-g37d34f0 (some application don't handle doubletap correctly without the timestamps). This works for double-tap immediately, for multi-tap we need to remember the timestamp of the first press event and use it for the release event so that there's a forced gap between the release and the second press. https://bugs.freedesktop.org/show_bug.cgi?id=89511 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-04-16 10:19:11 +10:00
<g fill="#000000" font-family="Helvetica" text-anchor="middle" font-size="12px">
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<text x="60412.25" y="43556.75">
touchpad: end tap-and-drag with an extra tap Currently for the tap-and-drag gesture to end user has to wait for a timeout to expire. Make it possible to end the drag gesture by just tapping. The allowed finger sequences to start and end a drag are thus: tap, down, .... move ...., up <wait for timeout> tap, down, .... move ...., up, tap https://bugs.freedesktop.org/show_bug.cgi?id=90255 Signed-off-by: Velimir Lisec <lisec.velimir@gmail.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> State diagram changes and a doc change squashed in. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-04-30 00:13:51 +02:00
second</text>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<text x="60412.25" y="43570.75">
touchpad: end tap-and-drag with an extra tap Currently for the tap-and-drag gesture to end user has to wait for a timeout to expire. Make it possible to end the drag gesture by just tapping. The allowed finger sequences to start and end a drag are thus: tap, down, .... move ...., up <wait for timeout> tap, down, .... move ...., up, tap https://bugs.freedesktop.org/show_bug.cgi?id=90255 Signed-off-by: Velimir Lisec <lisec.velimir@gmail.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> State diagram changes and a doc change squashed in. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-04-30 00:13:51 +02:00
finger down</text>
touchpad: introduce MULTITAP for multi-tap-and-drag Once we have a doubletap, enter a loop in the state machine where we can tap multiple times and either get a multi-click or a multi-click drag-and-drop. The sequence down/up down/up down/up produces a triple-click. The sequence down/up down/up down/up down produces a triple-click with a button down for dragging. Yes, that glorious octuple-tap-and-drag, it is now possible. World domination has been achieved, thank you for playing. We don't know when we finish tapping now, so add a timeout to send the last click event once the finger has been released for the last time. This guarantees that the timestamp of the last button down is later than the last release. This avoids the bug fixed in synaptics commit xf86-input-synaptics-1.8.0-21-g37d34f0 (some application don't handle doubletap correctly without the timestamps). This works for double-tap immediately, for multi-tap we need to remember the timestamp of the first press event and use it for the release event so that there's a forced gap between the release and the second press. https://bugs.freedesktop.org/show_bug.cgi?id=89511 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-04-16 10:19:11 +10:00
</g>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<path d="M 60085.54 43535 C 60088.34 43531.86 60092.32 43530.05 60096.52 43530 L 60130.49 43530 C 60134.69 43530.05 60138.67 43531.86 60141.47 43535 L 60161.45 43558 C 60162.01 43559.28 60162.01 43560.72 60161.45 43562 L 60141.47 43585 C 60138.67 43588.14 60134.69 43589.95 60130.49 43590 L 60096.52 43590 C 60092.32 43589.95 60088.34 43588.14 60085.54 43585 L 60065.56 43562 C 60065 43560.72 60065 43559.28 60065.56 43558 L 60085.54 43535 Z" fill="#67ab9f" stroke="#000000" stroke-width="2" stroke-miterlimit="10" pointer-events="none"/>
touchpad: introduce MULTITAP for multi-tap-and-drag Once we have a doubletap, enter a loop in the state machine where we can tap multiple times and either get a multi-click or a multi-click drag-and-drop. The sequence down/up down/up down/up produces a triple-click. The sequence down/up down/up down/up down produces a triple-click with a button down for dragging. Yes, that glorious octuple-tap-and-drag, it is now possible. World domination has been achieved, thank you for playing. We don't know when we finish tapping now, so add a timeout to send the last click event once the finger has been released for the last time. This guarantees that the timestamp of the last button down is later than the last release. This avoids the bug fixed in synaptics commit xf86-input-synaptics-1.8.0-21-g37d34f0 (some application don't handle doubletap correctly without the timestamps). This works for double-tap immediately, for multi-tap we need to remember the timestamp of the first press event and use it for the release event so that there's a forced gap between the release and the second press. https://bugs.freedesktop.org/show_bug.cgi?id=89511 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-04-16 10:19:11 +10:00
<g fill="#000000" font-family="Helvetica" text-anchor="middle" font-size="12px">
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<text x="60113.25" y="43556.75">
touchpad: end tap-and-drag with an extra tap Currently for the tap-and-drag gesture to end user has to wait for a timeout to expire. Make it possible to end the drag gesture by just tapping. The allowed finger sequences to start and end a drag are thus: tap, down, .... move ...., up <wait for timeout> tap, down, .... move ...., up, tap https://bugs.freedesktop.org/show_bug.cgi?id=90255 Signed-off-by: Velimir Lisec <lisec.velimir@gmail.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> State diagram changes and a doc change squashed in. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-04-30 00:13:51 +02:00
move &gt; </text>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<text x="60113.25" y="43570.75">
touchpad: end tap-and-drag with an extra tap Currently for the tap-and-drag gesture to end user has to wait for a timeout to expire. Make it possible to end the drag gesture by just tapping. The allowed finger sequences to start and end a drag are thus: tap, down, .... move ...., up <wait for timeout> tap, down, .... move ...., up, tap https://bugs.freedesktop.org/show_bug.cgi?id=90255 Signed-off-by: Velimir Lisec <lisec.velimir@gmail.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> State diagram changes and a doc change squashed in. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-04-30 00:13:51 +02:00
threshold</text>
touchpad: introduce MULTITAP for multi-tap-and-drag Once we have a doubletap, enter a loop in the state machine where we can tap multiple times and either get a multi-click or a multi-click drag-and-drop. The sequence down/up down/up down/up produces a triple-click. The sequence down/up down/up down/up down produces a triple-click with a button down for dragging. Yes, that glorious octuple-tap-and-drag, it is now possible. World domination has been achieved, thank you for playing. We don't know when we finish tapping now, so add a timeout to send the last click event once the finger has been released for the last time. This guarantees that the timestamp of the last button down is later than the last release. This avoids the bug fixed in synaptics commit xf86-input-synaptics-1.8.0-21-g37d34f0 (some application don't handle doubletap correctly without the timestamps). This works for double-tap immediately, for multi-tap we need to remember the timestamp of the first press event and use it for the release event so that there's a forced gap between the release and the second press. https://bugs.freedesktop.org/show_bug.cgi?id=89511 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-04-16 10:19:11 +10:00
</g>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<path d="M 60207.58 43452 L 60143.82 43525.2" fill="none" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 60140.37 43529.16 L 60142.33 43521.58 L 60143.82 43525.2 L 60147.6 43526.18 Z" fill="#000000" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 60234.92 43452 L 60271.79 43526.3" fill="none" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 60274.12 43531 L 60267.87 43526.28 L 60271.79 43526.3 L 60274.14 43523.17 Z" fill="#000000" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 60254.3 43452 L 60363.3 43526.41" fill="none" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 60367.63 43529.37 L 60359.88 43528.31 L 60363.3 43526.41 L 60363.82 43522.53 Z" fill="#000000" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 60126.75 43590 L 60392.57 44191.68" fill="none" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 60394.69 44196.48 L 60388.66 44191.49 L 60392.57 44191.68 L 60395.06 44188.66 Z" fill="#000000" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 60294.89 43592 L 60402.54 44191.23" fill="none" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 60403.46 44196.4 L 60398.78 44190.13 L 60402.54 44191.23 L 60405.67 44188.89 Z" fill="#000000" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 60420.72 43590 L 60590.92 44211.36" fill="none" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 60592.3 44216.42 L 60587.08 44210.6 L 60590.92 44211.36 L 60593.83 44208.75 Z" fill="#000000" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 59878.53 43815 L 59868.04 43905.67" fill="none" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 59867.44 43910.89 L 59864.77 43903.53 L 59868.04 43905.67 L 59871.72 43904.34 Z" fill="#000000" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 59710.5 43648.7 C 59726.62 43654.91 59744.38 43654.91 59760.5 43648.7 C 59776.62 43642.5 59794.38 43642.5 59810.5 43648.7 L 59810.5 43701.28 C 59794.38 43695.08 59776.62 43695.08 59760.5 43701.28 C 59744.38 43707.49 59726.62 43707.49 59710.5 43701.28 L 59710.5 43648.7 Z" fill="#ffd966" stroke="#000000" stroke-width="2" stroke-miterlimit="10" pointer-events="none"/>
<g fill="#000000" font-family="Helvetica" text-anchor="middle" font-size="12px">
<text x="59760.25" y="43678.75">
touchpad: end tap-and-drag with an extra tap Currently for the tap-and-drag gesture to end user has to wait for a timeout to expire. Make it possible to end the drag gesture by just tapping. The allowed finger sequences to start and end a drag are thus: tap, down, .... move ...., up <wait for timeout> tap, down, .... move ...., up, tap https://bugs.freedesktop.org/show_bug.cgi?id=90255 Signed-off-by: Velimir Lisec <lisec.velimir@gmail.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> State diagram changes and a doc change squashed in. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-04-30 00:13:51 +02:00
TOUCH_TOUCH</text>
touchpad: introduce MULTITAP for multi-tap-and-drag Once we have a doubletap, enter a loop in the state machine where we can tap multiple times and either get a multi-click or a multi-click drag-and-drop. The sequence down/up down/up down/up produces a triple-click. The sequence down/up down/up down/up down produces a triple-click with a button down for dragging. Yes, that glorious octuple-tap-and-drag, it is now possible. World domination has been achieved, thank you for playing. We don't know when we finish tapping now, so add a timeout to send the last click event once the finger has been released for the last time. This guarantees that the timestamp of the last button down is later than the last release. This avoids the bug fixed in synaptics commit xf86-input-synaptics-1.8.0-21-g37d34f0 (some application don't handle doubletap correctly without the timestamps). This works for double-tap immediately, for multi-tap we need to remember the timestamp of the first press event and use it for the release event so that there's a forced gap between the release and the second press. https://bugs.freedesktop.org/show_bug.cgi?id=89511 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-04-16 10:19:11 +10:00
</g>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<path d="M 59754.15 43747 L 59757.07 43713.84" fill="none" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 59757.53 43708.61 L 59760.41 43715.89 L 59757.07 43713.84 L 59753.43 43715.28 Z" fill="#000000" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 59931.5 43638.7 C 59947.62 43644.91 59965.38 43644.91 59981.5 43638.7 C 59997.62 43632.5 60015.38 43632.5 60031.5 43638.7 L 60031.5 43691.28 C 60015.38 43685.08 59997.62 43685.08 59981.5 43691.28 C 59965.38 43697.49 59947.62 43697.49 59931.5 43691.28 L 59931.5 43638.7 Z" fill="#ffd966" stroke="#000000" stroke-width="2" stroke-miterlimit="10" pointer-events="none"/>
touchpad: introduce MULTITAP for multi-tap-and-drag Once we have a doubletap, enter a loop in the state machine where we can tap multiple times and either get a multi-click or a multi-click drag-and-drop. The sequence down/up down/up down/up produces a triple-click. The sequence down/up down/up down/up down produces a triple-click with a button down for dragging. Yes, that glorious octuple-tap-and-drag, it is now possible. World domination has been achieved, thank you for playing. We don't know when we finish tapping now, so add a timeout to send the last click event once the finger has been released for the last time. This guarantees that the timestamp of the last button down is later than the last release. This avoids the bug fixed in synaptics commit xf86-input-synaptics-1.8.0-21-g37d34f0 (some application don't handle doubletap correctly without the timestamps). This works for double-tap immediately, for multi-tap we need to remember the timestamp of the first press event and use it for the release event so that there's a forced gap between the release and the second press. https://bugs.freedesktop.org/show_bug.cgi?id=89511 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-04-16 10:19:11 +10:00
<g fill="#000000" font-family="Helvetica" text-anchor="middle" font-size="12px">
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<text x="59981.25" y="43668.75">
touchpad: end tap-and-drag with an extra tap Currently for the tap-and-drag gesture to end user has to wait for a timeout to expire. Make it possible to end the drag gesture by just tapping. The allowed finger sequences to start and end a drag are thus: tap, down, .... move ...., up <wait for timeout> tap, down, .... move ...., up, tap https://bugs.freedesktop.org/show_bug.cgi?id=90255 Signed-off-by: Velimir Lisec <lisec.velimir@gmail.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> State diagram changes and a doc change squashed in. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-04-30 00:13:51 +02:00
TOUCH_IDLE</text>
touchpad: introduce MULTITAP for multi-tap-and-drag Once we have a doubletap, enter a loop in the state machine where we can tap multiple times and either get a multi-click or a multi-click drag-and-drop. The sequence down/up down/up down/up produces a triple-click. The sequence down/up down/up down/up down produces a triple-click with a button down for dragging. Yes, that glorious octuple-tap-and-drag, it is now possible. World domination has been achieved, thank you for playing. We don't know when we finish tapping now, so add a timeout to send the last click event once the finger has been released for the last time. This guarantees that the timestamp of the last button down is later than the last release. This avoids the bug fixed in synaptics commit xf86-input-synaptics-1.8.0-21-g37d34f0 (some application don't handle doubletap correctly without the timestamps). This works for double-tap immediately, for multi-tap we need to remember the timestamp of the first press event and use it for the release event so that there's a forced gap between the release and the second press. https://bugs.freedesktop.org/show_bug.cgi?id=89511 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-04-16 10:19:11 +10:00
</g>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<path d="M 59995.07 43590 L 59988.51 43626.23" fill="none" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 59987.58 43631.4 L 59985.38 43623.89 L 59988.51 43626.23 L 59992.27 43625.13 Z" fill="#000000" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 59521.54 44157 C 59524.34 44153.86 59528.32 44152.05 59532.52 44152 L 59566.49 44152 C 59570.69 44152.05 59574.67 44153.86 59577.47 44157 L 59597.45 44180 C 59598.01 44181.28 59598.01 44182.72 59597.45 44184 L 59577.47 44207 C 59574.67 44210.14 59570.69 44211.95 59566.49 44212 L 59532.52 44212 C 59528.32 44211.95 59524.34 44210.14 59521.54 44207 L 59501.56 44184 C 59501 44182.72 59501 44181.28 59501.56 44180 L 59521.54 44157 Z" fill="#000000" stroke="#ffffff" stroke-width="2" stroke-miterlimit="10" pointer-events="none"/>
touchpad: introduce MULTITAP for multi-tap-and-drag Once we have a doubletap, enter a loop in the state machine where we can tap multiple times and either get a multi-click or a multi-click drag-and-drop. The sequence down/up down/up down/up produces a triple-click. The sequence down/up down/up down/up down produces a triple-click with a button down for dragging. Yes, that glorious octuple-tap-and-drag, it is now possible. World domination has been achieved, thank you for playing. We don't know when we finish tapping now, so add a timeout to send the last click event once the finger has been released for the last time. This guarantees that the timestamp of the last button down is later than the last release. This avoids the bug fixed in synaptics commit xf86-input-synaptics-1.8.0-21-g37d34f0 (some application don't handle doubletap correctly without the timestamps). This works for double-tap immediately, for multi-tap we need to remember the timestamp of the first press event and use it for the release event so that there's a forced gap between the release and the second press. https://bugs.freedesktop.org/show_bug.cgi?id=89511 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-04-16 10:19:11 +10:00
<g fill="#FFFFFF" font-family="Helvetica" text-anchor="middle" font-size="12px">
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<text x="59549.25" y="44171.75">
touchpad: end tap-and-drag with an extra tap Currently for the tap-and-drag gesture to end user has to wait for a timeout to expire. Make it possible to end the drag gesture by just tapping. The allowed finger sequences to start and end a drag are thus: tap, down, .... move ...., up <wait for timeout> tap, down, .... move ...., up, tap https://bugs.freedesktop.org/show_bug.cgi?id=90255 Signed-off-by: Velimir Lisec <lisec.velimir@gmail.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> State diagram changes and a doc change squashed in. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-04-30 00:13:51 +02:00
phys</text>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<text x="59549.25" y="44185.75">
touchpad: end tap-and-drag with an extra tap Currently for the tap-and-drag gesture to end user has to wait for a timeout to expire. Make it possible to end the drag gesture by just tapping. The allowed finger sequences to start and end a drag are thus: tap, down, .... move ...., up <wait for timeout> tap, down, .... move ...., up, tap https://bugs.freedesktop.org/show_bug.cgi?id=90255 Signed-off-by: Velimir Lisec <lisec.velimir@gmail.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> State diagram changes and a doc change squashed in. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-04-30 00:13:51 +02:00
button</text>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<text x="59549.25" y="44199.75">
touchpad: end tap-and-drag with an extra tap Currently for the tap-and-drag gesture to end user has to wait for a timeout to expire. Make it possible to end the drag gesture by just tapping. The allowed finger sequences to start and end a drag are thus: tap, down, .... move ...., up <wait for timeout> tap, down, .... move ...., up, tap https://bugs.freedesktop.org/show_bug.cgi?id=90255 Signed-off-by: Velimir Lisec <lisec.velimir@gmail.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> State diagram changes and a doc change squashed in. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-04-30 00:13:51 +02:00
press</text>
touchpad: introduce MULTITAP for multi-tap-and-drag Once we have a doubletap, enter a loop in the state machine where we can tap multiple times and either get a multi-click or a multi-click drag-and-drop. The sequence down/up down/up down/up produces a triple-click. The sequence down/up down/up down/up down produces a triple-click with a button down for dragging. Yes, that glorious octuple-tap-and-drag, it is now possible. World domination has been achieved, thank you for playing. We don't know when we finish tapping now, so add a timeout to send the last click event once the finger has been released for the last time. This guarantees that the timestamp of the last button down is later than the last release. This avoids the bug fixed in synaptics commit xf86-input-synaptics-1.8.0-21-g37d34f0 (some application don't handle doubletap correctly without the timestamps). This works for double-tap immediately, for multi-tap we need to remember the timestamp of the first press event and use it for the release event so that there's a forced gap between the release and the second press. https://bugs.freedesktop.org/show_bug.cgi?id=89511 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-04-16 10:19:11 +10:00
</g>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<path d="M 59839.76 43952 L 59592.35 44148.05" fill="none" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 59588.24 44151.31 L 59591.55 44144.22 L 59592.35 44148.05 L 59595.9 44149.7 Z" fill="#000000" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 59571.94 44212 L 59725.24 44416.9" fill="none" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 59728.39 44421.1 L 59721.39 44417.6 L 59725.24 44416.9 L 59726.99 44413.4 Z" fill="#000000" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 60217.08 43452 L 59983.73 44041.08" fill="none" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 59981.8 44045.96 L 59981.12 44038.16 L 59983.73 44041.08 L 59987.63 44040.74 Z" fill="#000000" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<rect x="59938.5" y="44362" width="209" height="40" rx="2.4" ry="2.4" fill="#ccffcc" stroke="#000000" stroke-width="2" pointer-events="none"/>
touchpad: end tap-and-drag with an extra tap Currently for the tap-and-drag gesture to end user has to wait for a timeout to expire. Make it possible to end the drag gesture by just tapping. The allowed finger sequences to start and end a drag are thus: tap, down, .... move ...., up <wait for timeout> tap, down, .... move ...., up, tap https://bugs.freedesktop.org/show_bug.cgi?id=90255 Signed-off-by: Velimir Lisec <lisec.velimir@gmail.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> State diagram changes and a doc change squashed in. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-04-30 00:13:51 +02:00
<g fill="#000000" font-family="Helvetica" text-anchor="middle" font-size="12px">
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<text x="60042.75" y="44385.75">
touchpad: end tap-and-drag with an extra tap Currently for the tap-and-drag gesture to end user has to wait for a timeout to expire. Make it possible to end the drag gesture by just tapping. The allowed finger sequences to start and end a drag are thus: tap, down, .... move ...., up <wait for timeout> tap, down, .... move ...., up, tap https://bugs.freedesktop.org/show_bug.cgi?id=90255 Signed-off-by: Velimir Lisec <lisec.velimir@gmail.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> State diagram changes and a doc change squashed in. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-04-30 00:13:51 +02:00
DRAGGING_OR_TAP</text>
</g>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<path d="M 59923.04 44627 C 59925.84 44623.86 59929.82 44622.05 59934.02 44622 L 59967.99 44622 C 59972.19 44622.05 59976.17 44623.86 59978.97 44627 L 59998.95 44650 C 59999.51 44651.28 59999.51 44652.72 59998.95 44654 L 59978.97 44677 C 59976.17 44680.14 59972.19 44681.95 59967.99 44682 L 59934.02 44682 C 59929.82 44681.95 59925.84 44680.14 59923.04 44677 L 59903.06 44654 C 59902.5 44652.72 59902.5 44651.28 59903.06 44650 L 59923.04 44627 Z" fill="#ffd966" stroke="#000000" stroke-width="2" stroke-miterlimit="10" pointer-events="none"/>
touchpad: end tap-and-drag with an extra tap Currently for the tap-and-drag gesture to end user has to wait for a timeout to expire. Make it possible to end the drag gesture by just tapping. The allowed finger sequences to start and end a drag are thus: tap, down, .... move ...., up <wait for timeout> tap, down, .... move ...., up, tap https://bugs.freedesktop.org/show_bug.cgi?id=90255 Signed-off-by: Velimir Lisec <lisec.velimir@gmail.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> State diagram changes and a doc change squashed in. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-04-30 00:13:51 +02:00
<g fill="#000000" font-family="Helvetica" text-anchor="middle" font-size="12px">
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<text x="59950.75" y="44648.75">
touchpad: end tap-and-drag with an extra tap Currently for the tap-and-drag gesture to end user has to wait for a timeout to expire. Make it possible to end the drag gesture by just tapping. The allowed finger sequences to start and end a drag are thus: tap, down, .... move ...., up <wait for timeout> tap, down, .... move ...., up, tap https://bugs.freedesktop.org/show_bug.cgi?id=90255 Signed-off-by: Velimir Lisec <lisec.velimir@gmail.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> State diagram changes and a doc change squashed in. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-04-30 00:13:51 +02:00
first</text>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<text x="59950.75" y="44662.75">
touchpad: end tap-and-drag with an extra tap Currently for the tap-and-drag gesture to end user has to wait for a timeout to expire. Make it possible to end the drag gesture by just tapping. The allowed finger sequences to start and end a drag are thus: tap, down, .... move ...., up <wait for timeout> tap, down, .... move ...., up, tap https://bugs.freedesktop.org/show_bug.cgi?id=90255 Signed-off-by: Velimir Lisec <lisec.velimir@gmail.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> State diagram changes and a doc change squashed in. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-04-30 00:13:51 +02:00
finger up</text>
</g>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<path d="M 60036.19 44402 L 59963.28 44615.97" fill="none" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 59961.58 44620.94 L 59960.53 44613.19 L 59963.28 44615.97 L 59967.15 44615.44 Z" fill="#000000" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 60095.04 44267 C 60097.84 44263.86 60101.82 44262.05 60106.02 44262 L 60139.99 44262 C 60144.19 44262.05 60148.17 44263.86 60150.97 44267 L 60170.95 44290 C 60171.51 44291.28 60171.51 44292.72 60170.95 44294 L 60150.97 44317 C 60148.17 44320.14 60144.19 44321.95 60139.99 44322 L 60106.02 44322 C 60101.82 44321.95 60097.84 44320.14 60095.04 44317 L 60075.06 44294 C 60074.5 44292.72 60074.5 44291.28 60075.06 44290 L 60095.04 44267 Z" fill="#99ffff" stroke="#000000" stroke-width="2" stroke-miterlimit="10" pointer-events="none"/>
touchpad: end tap-and-drag with an extra tap Currently for the tap-and-drag gesture to end user has to wait for a timeout to expire. Make it possible to end the drag gesture by just tapping. The allowed finger sequences to start and end a drag are thus: tap, down, .... move ...., up <wait for timeout> tap, down, .... move ...., up, tap https://bugs.freedesktop.org/show_bug.cgi?id=90255 Signed-off-by: Velimir Lisec <lisec.velimir@gmail.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> State diagram changes and a doc change squashed in. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-04-30 00:13:51 +02:00
<g fill="#000000" font-family="Helvetica" text-anchor="middle" font-size="12px">
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<text x="60122.75" y="44295.75">
touchpad: end tap-and-drag with an extra tap Currently for the tap-and-drag gesture to end user has to wait for a timeout to expire. Make it possible to end the drag gesture by just tapping. The allowed finger sequences to start and end a drag are thus: tap, down, .... move ...., up <wait for timeout> tap, down, .... move ...., up, tap https://bugs.freedesktop.org/show_bug.cgi?id=90255 Signed-off-by: Velimir Lisec <lisec.velimir@gmail.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> State diagram changes and a doc change squashed in. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-04-30 00:13:51 +02:00
timeout</text>
</g>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<path d="M 60060.78 44362 L 60092.1 44326.76" fill="none" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 60095.59 44322.84 L 60093.56 44330.39 L 60092.1 44326.76 L 60088.32 44325.74 Z" fill="#000000" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 60171.5 44303.63 L 60322.81 44339.92" fill="none" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 60327.91 44341.15 L 60320.29 44342.92 L 60322.81 44339.92 L 60321.92 44336.11 Z" fill="#000000" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 60212.54 44367 C 60215.34 44363.86 60219.32 44362.05 60223.52 44362 L 60257.49 44362 C 60261.69 44362.05 60265.67 44363.86 60268.47 44367 L 60288.45 44390 C 60289.01 44391.28 60289.01 44392.72 60288.45 44394 L 60268.47 44417 C 60265.67 44420.14 60261.69 44421.95 60257.49 44422 L 60223.52 44422 C 60219.32 44421.95 60215.34 44420.14 60212.54 44417 L 60192.56 44394 C 60192 44392.72 60192 44391.28 60192.56 44390 L 60212.54 44367 Z" fill="#67ab9f" stroke="#000000" stroke-width="2" stroke-miterlimit="10" pointer-events="none"/>
touchpad: end tap-and-drag with an extra tap Currently for the tap-and-drag gesture to end user has to wait for a timeout to expire. Make it possible to end the drag gesture by just tapping. The allowed finger sequences to start and end a drag are thus: tap, down, .... move ...., up <wait for timeout> tap, down, .... move ...., up, tap https://bugs.freedesktop.org/show_bug.cgi?id=90255 Signed-off-by: Velimir Lisec <lisec.velimir@gmail.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> State diagram changes and a doc change squashed in. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-04-30 00:13:51 +02:00
<g fill="#000000" font-family="Helvetica" text-anchor="middle" font-size="12px">
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<text x="60240.25" y="44388.75">
touchpad: end tap-and-drag with an extra tap Currently for the tap-and-drag gesture to end user has to wait for a timeout to expire. Make it possible to end the drag gesture by just tapping. The allowed finger sequences to start and end a drag are thus: tap, down, .... move ...., up <wait for timeout> tap, down, .... move ...., up, tap https://bugs.freedesktop.org/show_bug.cgi?id=90255 Signed-off-by: Velimir Lisec <lisec.velimir@gmail.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> State diagram changes and a doc change squashed in. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-04-30 00:13:51 +02:00
move &gt; </text>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<text x="60240.25" y="44402.75">
touchpad: end tap-and-drag with an extra tap Currently for the tap-and-drag gesture to end user has to wait for a timeout to expire. Make it possible to end the drag gesture by just tapping. The allowed finger sequences to start and end a drag are thus: tap, down, .... move ...., up <wait for timeout> tap, down, .... move ...., up, tap https://bugs.freedesktop.org/show_bug.cgi?id=90255 Signed-off-by: Velimir Lisec <lisec.velimir@gmail.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> State diagram changes and a doc change squashed in. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-04-30 00:13:51 +02:00
threshold</text>
</g>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<path d="M 60147.5 44387.29 L 60185.64 44389.22" fill="none" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 60190.88 44389.49 L 60183.72 44392.63 L 60185.64 44389.22 L 60184.07 44385.64 Z" fill="#000000" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 60289 44380.94 L 60322.79 44373.24" fill="none" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 60327.91 44372.07 L 60321.86 44377.04 L 60322.79 44373.24 L 60320.31 44370.21 Z" fill="#000000" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 60073.93 44781 L 60071.24 44638.87" fill="none" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 60071.14 44633.62 L 60074.77 44640.55 L 60071.24 44638.87 L 60067.77 44640.68 Z" fill="#000000" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 60066.4 44567.5 L 60046.32 44408.32" fill="none" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 60045.66 44403.11 L 60050.01 44409.62 L 60046.32 44408.32 L 60043.07 44410.49 Z" fill="#000000" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 60066.66 44402 L 60277.14 44579.89" fill="none" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 60281.15 44583.28 L 60273.54 44581.43 L 60277.14 44579.89 L 60278.06 44576.09 Z" fill="#000000" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 59968.5 44887.7 C 59984.62 44893.91 60002.38 44893.91 60018.5 44887.7 C 60034.62 44881.5 60052.38 44881.5 60068.5 44887.7 L 60068.5 44940.28 C 60052.38 44934.08 60034.62 44934.08 60018.5 44940.28 C 60002.38 44946.49 59984.62 44946.49 59968.5 44940.28 L 59968.5 44887.7 Z" fill="#ffd966" stroke="#000000" stroke-width="2" stroke-miterlimit="10" pointer-events="none"/>
<g fill="#000000" font-family="Helvetica" text-anchor="middle" font-size="12px">
<text x="60018.25" y="44917.75">
touchpad: end tap-and-drag with an extra tap Currently for the tap-and-drag gesture to end user has to wait for a timeout to expire. Make it possible to end the drag gesture by just tapping. The allowed finger sequences to start and end a drag are thus: tap, down, .... move ...., up <wait for timeout> tap, down, .... move ...., up, tap https://bugs.freedesktop.org/show_bug.cgi?id=90255 Signed-off-by: Velimir Lisec <lisec.velimir@gmail.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> State diagram changes and a doc change squashed in. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-04-30 00:13:51 +02:00
TOUCH_IDLE</text>
</g>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<path d="M 59958.73 44682 L 60008.54 44875.33" fill="none" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 60009.85 44880.42 L 60004.71 44874.51 L 60008.54 44875.33 L 60011.49 44872.77 Z" fill="#000000" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 60068.5 44914 L 60313.63 44914" fill="none" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 60318.88 44914 L 60311.88 44917.5 L 60313.63 44914 L 60311.88 44910.5 Z" fill="#000000" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 60038.18 44362 L 59978.22 44113.19" fill="none" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 59976.99 44108.09 L 59982.03 44114.07 L 59978.22 44113.19 L 59975.23 44115.71 Z" fill="#000000" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 60236 44658 L 60276 44698 L 60236 44738 L 60196 44698 Z" fill="#ffffff" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<g transform="translate(60204,44684)">
touchpad: hook up drag lock configuration Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-06-22 11:06:25 +10:00
<switch>
<foreignObject pointer-events="all" width="64" height="31" requiredFeatures="http://www.w3.org/TR/SVG11/feature#Extensibility">
<div xmlns="http://www.w3.org/1999/xhtml" style="display: inline-block; font-size: 12px; font-family: Helvetica; color: rgb(0, 0, 0); line-height: 1.2; vertical-align: top; width: 64px; white-space: normal; text-align: center;">
<div style="display:inline-block;text-align:inherit;text-decoration:inherit;" xmlns="http://www.w3.org/1999/xhtml">
drag lock<br />
enabled?<br />
</div>
</div>
</foreignObject>
<text x="32" y="22" fill="#000000" text-anchor="middle" font-size="12px" font-family="Helvetica">
[Not supported by viewer]</text>
</switch>
</g>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<path d="M 60276 44698 L 60369 44698 L 60369 44877.63" fill="none" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 60369 44882.88 L 60365.5 44875.88 L 60369 44877.63 L 60372.5 44875.88 Z" fill="#000000" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<g transform="translate(60363,44735)">
touchpad: hook up drag lock configuration Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-06-22 11:06:25 +10:00
<switch>
<foreignObject pointer-events="all" width="16" height="16" requiredFeatures="http://www.w3.org/TR/SVG11/feature#Extensibility">
<div xmlns="http://www.w3.org/1999/xhtml" style="display: inline-block; font-size: 12px; font-family: Helvetica; color: rgb(0, 0, 0); line-height: 1.2; vertical-align: top; white-space: nowrap; text-align: center;">
<div style="display:inline-block;text-align:inherit;text-decoration:inherit;background-color:#ffffff;" xmlns="http://www.w3.org/1999/xhtml">
no</div>
</div>
</foreignObject>
<text x="8" y="14" fill="#000000" text-anchor="middle" font-size="12px" font-family="Helvetica">
[Not supported by viewer]</text>
</switch>
</g>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<path d="M 60236 44738 L 60236 44772.63" fill="none" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 60236 44777.88 L 60232.5 44770.88 L 60236 44772.63 L 60239.5 44770.88 Z" fill="#000000" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<g transform="translate(60226,44756)">
touchpad: hook up drag lock configuration Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-06-22 11:06:25 +10:00
<switch>
<foreignObject pointer-events="all" width="21" height="16" requiredFeatures="http://www.w3.org/TR/SVG11/feature#Extensibility">
<div xmlns="http://www.w3.org/1999/xhtml" style="display: inline-block; font-size: 12px; font-family: Helvetica; color: rgb(0, 0, 0); line-height: 1.2; vertical-align: top; white-space: nowrap; text-align: center;">
<div style="display:inline-block;text-align:inherit;text-decoration:inherit;background-color:#ffffff;" xmlns="http://www.w3.org/1999/xhtml">
yes<br />
</div>
</div>
</foreignObject>
<text x="11" y="14" fill="#000000" text-anchor="middle" font-size="12px" font-family="Helvetica">
[Not supported by viewer]</text>
</switch>
</g>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<path d="M 61594.54 43257 C 61597.34 43253.86 61601.32 43252.05 61605.52 43252 L 61639.49 43252 C 61643.69 43252.05 61647.67 43253.86 61650.47 43257 L 61670.45 43280 C 61671.01 43281.28 61671.01 43282.72 61670.45 43284 L 61650.47 43307 C 61647.67 43310.14 61643.69 43311.95 61639.49 43312 L 61605.52 43312 C 61601.32 43311.95 61597.34 43310.14 61594.54 43307 L 61574.56 43284 C 61574 43282.72 61574 43281.28 61574.56 43280 L 61594.54 43257 Z" fill="#ff99cc" stroke="#000000" stroke-width="2" stroke-miterlimit="10" pointer-events="none"/>
touchpad: work thumb detection into the tap state machine Most thumbs are detected a few events into the sequence. Work this into parts of the tapping state machine. Only the most common use-case is handled here - if the first finger ends up being marked as a thumb, we return to the idle state and ignore that touch sequence. At any other state, we handle thumbs like any other finger. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-07-06 15:22:45 +10:00
<g fill="#000000" font-family="Helvetica" text-anchor="middle" font-size="12px">
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<text x="61622.25" y="43285.75">
touchpad: work thumb detection into the tap state machine Most thumbs are detected a few events into the sequence. Work this into parts of the tapping state machine. Only the most common use-case is handled here - if the first finger ends up being marked as a thumb, we return to the idle state and ignore that touch sequence. At any other state, we handle thumbs like any other finger. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-07-06 15:22:45 +10:00
thumb</text>
</g>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<path d="M 61300.42 43182 L 61567.92 43265.05" fill="none" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 61572.93 43266.61 L 61565.21 43267.88 L 61567.92 43265.05 L 61567.28 43261.19 Z" fill="#000000" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 61651.5 43338.7 C 61667.62 43344.91 61685.38 43344.91 61701.5 43338.7 C 61717.62 43332.5 61735.38 43332.5 61751.5 43338.7 L 61751.5 43391.28 C 61735.38 43385.08 61717.62 43385.08 61701.5 43391.28 C 61685.38 43397.49 61667.62 43397.49 61651.5 43391.28 L 61651.5 43338.7 Z" fill="#ffd966" stroke="#000000" stroke-width="2" stroke-miterlimit="10" pointer-events="none"/>
touchpad: work thumb detection into the tap state machine Most thumbs are detected a few events into the sequence. Work this into parts of the tapping state machine. Only the most common use-case is handled here - if the first finger ends up being marked as a thumb, we return to the idle state and ignore that touch sequence. At any other state, we handle thumbs like any other finger. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-07-06 15:22:45 +10:00
<g fill="#000000" font-family="Helvetica" text-anchor="middle" font-size="12px">
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<text x="61701.25" y="43368.75">
touchpad: work thumb detection into the tap state machine Most thumbs are detected a few events into the sequence. Work this into parts of the tapping state machine. Only the most common use-case is handled here - if the first finger ends up being marked as a thumb, we return to the idle state and ignore that touch sequence. At any other state, we handle thumbs like any other finger. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-07-06 15:22:45 +10:00
TOUCH_DEAD</text>
</g>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<path d="M 61651.05 43312 L 61666.18 43327.89" fill="none" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 61669.8 43331.69 L 61662.43 43329.03 L 61666.18 43327.89 L 61667.5 43324.21 Z" fill="#000000" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 61716.81 43397.5 L 61823.65 43624.24" fill="none" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 61825.89 43628.99 L 61819.74 43624.15 L 61823.65 43624.24 L 61826.07 43621.16 Z" fill="#000000" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 61458.61 43427 L 61583.82 43316.22" fill="none" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 61587.75 43312.74 L 61584.83 43320 L 61583.82 43316.22 L 61580.19 43314.76 Z" fill="#000000" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<rect x="60971" y="43497" width="154" height="40" rx="2.4" ry="2.4" fill="#ccffcc" stroke="#000000" stroke-width="2" pointer-events="none"/>
touchpad: don't tap for 2fg down, followed by a single finger up The following sequence currently generates a right-button event: finger 1 down finger 2 down finger 1 up finger 2 held down This is easily triggered with short scroll events. There are two issues here: first is that the tapping code elsewhere treats any tap with a second finger down as a left-button tap, not a right button one. So if anything, we should generate a left button click here, not a right button click. Arguably, generating a button click here is wrong though, it's not a very well defined sequence and relatively difficult to trigger intentionally. So the best solution here is to simply ignore the release event and move straight back to state HOLD - unless the second finger is released within the timeout. If the finger is set down again during the timeout, we move straight to TOUCH_2_HOLD - this could eventually be interpreted as a tap, but not for now. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-08-31 11:10:58 +10:00
<g fill="#000000" font-family="Helvetica" text-anchor="middle" font-size="12px">
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<text x="61047.75" y="43520.75">
touchpad: don't tap for 2fg down, followed by a single finger up The following sequence currently generates a right-button event: finger 1 down finger 2 down finger 1 up finger 2 held down This is easily triggered with short scroll events. There are two issues here: first is that the tapping code elsewhere treats any tap with a second finger down as a left-button tap, not a right button one. So if anything, we should generate a left button click here, not a right button click. Arguably, generating a button click here is wrong though, it's not a very well defined sequence and relatively difficult to trigger intentionally. So the best solution here is to simply ignore the release event and move straight back to state HOLD - unless the second finger is released within the timeout. If the finger is set down again during the timeout, we move straight to TOUCH_2_HOLD - this could eventually be interpreted as a tap, but not for now. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-08-31 11:10:58 +10:00
TOUCH_2_RELEASE</text>
</g>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<path d="M 60900.04 43422 C 60902.84 43418.86 60906.82 43417.05 60911.02 43417 L 60944.99 43417 C 60949.19 43417.05 60953.17 43418.86 60955.97 43422 L 60975.95 43445 C 60976.51 43446.28 60976.51 43447.72 60975.95 43449 L 60955.97 43472 C 60953.17 43475.14 60949.19 43476.95 60944.99 43477 L 60911.02 43477 C 60906.82 43476.95 60902.84 43475.14 60900.04 43472 L 60880.06 43449 C 60879.5 43447.72 60879.5 43446.28 60880.06 43445 L 60900.04 43422 Z" fill="#7ea6e0" stroke="#000000" stroke-width="2" stroke-miterlimit="10" pointer-events="none"/>
touchpad: don't tap for 2fg down, followed by a single finger up The following sequence currently generates a right-button event: finger 1 down finger 2 down finger 1 up finger 2 held down This is easily triggered with short scroll events. There are two issues here: first is that the tapping code elsewhere treats any tap with a second finger down as a left-button tap, not a right button one. So if anything, we should generate a left button click here, not a right button click. Arguably, generating a button click here is wrong though, it's not a very well defined sequence and relatively difficult to trigger intentionally. So the best solution here is to simply ignore the release event and move straight back to state HOLD - unless the second finger is released within the timeout. If the finger is set down again during the timeout, we move straight to TOUCH_2_HOLD - this could eventually be interpreted as a tap, but not for now. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-08-31 11:10:58 +10:00
<g fill="#000000" font-family="Helvetica" text-anchor="middle" font-size="12px">
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<text x="60927.75" y="43443.75">
touchpad: don't tap for 2fg down, followed by a single finger up The following sequence currently generates a right-button event: finger 1 down finger 2 down finger 1 up finger 2 held down This is easily triggered with short scroll events. There are two issues here: first is that the tapping code elsewhere treats any tap with a second finger down as a left-button tap, not a right button one. So if anything, we should generate a left button click here, not a right button click. Arguably, generating a button click here is wrong though, it's not a very well defined sequence and relatively difficult to trigger intentionally. So the best solution here is to simply ignore the release event and move straight back to state HOLD - unless the second finger is released within the timeout. If the finger is set down again during the timeout, we move straight to TOUCH_2_HOLD - this could eventually be interpreted as a tap, but not for now. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-08-31 11:10:58 +10:00
second</text>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<text x="60927.75" y="43457.75">
touchpad: don't tap for 2fg down, followed by a single finger up The following sequence currently generates a right-button event: finger 1 down finger 2 down finger 1 up finger 2 held down This is easily triggered with short scroll events. There are two issues here: first is that the tapping code elsewhere treats any tap with a second finger down as a left-button tap, not a right button one. So if anything, we should generate a left button click here, not a right button click. Arguably, generating a button click here is wrong though, it's not a very well defined sequence and relatively difficult to trigger intentionally. So the best solution here is to simply ignore the release event and move straight back to state HOLD - unless the second finger is released within the timeout. If the finger is set down again during the timeout, we move straight to TOUCH_2_HOLD - this could eventually be interpreted as a tap, but not for now. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-08-31 11:10:58 +10:00
finger up</text>
</g>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<path d="M 61013.71 43497 L 60982 43478.5" fill="none" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 60977.47 43475.85 L 60985.28 43476.36 L 60982 43478.5 L 60981.75 43482.41 Z" fill="#000000" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 61193.54 43450 C 61196.34 43446.86 61200.32 43445.05 61204.52 43445 L 61238.49 43445 C 61242.69 43445.05 61246.67 43446.86 61249.47 43450 L 61269.45 43473 C 61270.01 43474.28 61270.01 43475.72 61269.45 43477 L 61249.47 43500 C 61246.67 43503.14 61242.69 43504.95 61238.49 43505 L 61204.52 43505 C 61200.32 43504.95 61196.34 43503.14 61193.54 43500 L 61173.56 43477 C 61173 43475.72 61173 43474.28 61173.56 43473 L 61193.54 43450 Z" fill="#99ffff" stroke="#000000" stroke-width="2" stroke-miterlimit="10" pointer-events="none"/>
touchpad: don't tap for 2fg down, followed by a single finger up The following sequence currently generates a right-button event: finger 1 down finger 2 down finger 1 up finger 2 held down This is easily triggered with short scroll events. There are two issues here: first is that the tapping code elsewhere treats any tap with a second finger down as a left-button tap, not a right button one. So if anything, we should generate a left button click here, not a right button click. Arguably, generating a button click here is wrong though, it's not a very well defined sequence and relatively difficult to trigger intentionally. So the best solution here is to simply ignore the release event and move straight back to state HOLD - unless the second finger is released within the timeout. If the finger is set down again during the timeout, we move straight to TOUCH_2_HOLD - this could eventually be interpreted as a tap, but not for now. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-08-31 11:10:58 +10:00
<g fill="#000000" font-family="Helvetica" text-anchor="middle" font-size="12px">
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<text x="61221.25" y="43478.75">
touchpad: don't tap for 2fg down, followed by a single finger up The following sequence currently generates a right-button event: finger 1 down finger 2 down finger 1 up finger 2 held down This is easily triggered with short scroll events. There are two issues here: first is that the tapping code elsewhere treats any tap with a second finger down as a left-button tap, not a right button one. So if anything, we should generate a left button click here, not a right button click. Arguably, generating a button click here is wrong though, it's not a very well defined sequence and relatively difficult to trigger intentionally. So the best solution here is to simply ignore the release event and move straight back to state HOLD - unless the second finger is released within the timeout. If the finger is set down again during the timeout, we move straight to TOUCH_2_HOLD - this could eventually be interpreted as a tap, but not for now. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-08-31 11:10:58 +10:00
timeout</text>
</g>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<path d="M 61125 43498.36 L 61166.81 43488.24" fill="none" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 61171.91 43487 L 61165.93 43492.05 L 61166.81 43488.24 L 61164.29 43485.25 Z" fill="#000000" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 61207.54 43543 C 61210.34 43539.86 61214.32 43538.05 61218.52 43538 L 61252.49 43538 C 61256.69 43538.05 61260.67 43539.86 61263.47 43543 L 61283.45 43566 C 61284.01 43567.28 61284.01 43568.72 61283.45 43570 L 61263.47 43593 C 61260.67 43596.14 61256.69 43597.95 61252.49 43598 L 61218.52 43598 C 61214.32 43597.95 61210.34 43596.14 61207.54 43593 L 61187.56 43570 C 61187 43568.72 61187 43567.28 61187.56 43566 L 61207.54 43543 Z" fill="#67ab9f" stroke="#000000" stroke-width="2" stroke-miterlimit="10" pointer-events="none"/>
touchpad: don't tap for 2fg down, followed by a single finger up The following sequence currently generates a right-button event: finger 1 down finger 2 down finger 1 up finger 2 held down This is easily triggered with short scroll events. There are two issues here: first is that the tapping code elsewhere treats any tap with a second finger down as a left-button tap, not a right button one. So if anything, we should generate a left button click here, not a right button click. Arguably, generating a button click here is wrong though, it's not a very well defined sequence and relatively difficult to trigger intentionally. So the best solution here is to simply ignore the release event and move straight back to state HOLD - unless the second finger is released within the timeout. If the finger is set down again during the timeout, we move straight to TOUCH_2_HOLD - this could eventually be interpreted as a tap, but not for now. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-08-31 11:10:58 +10:00
<g fill="#000000" font-family="Helvetica" text-anchor="middle" font-size="12px">
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<text x="61235.25" y="43564.75">
touchpad: don't tap for 2fg down, followed by a single finger up The following sequence currently generates a right-button event: finger 1 down finger 2 down finger 1 up finger 2 held down This is easily triggered with short scroll events. There are two issues here: first is that the tapping code elsewhere treats any tap with a second finger down as a left-button tap, not a right button one. So if anything, we should generate a left button click here, not a right button click. Arguably, generating a button click here is wrong though, it's not a very well defined sequence and relatively difficult to trigger intentionally. So the best solution here is to simply ignore the release event and move straight back to state HOLD - unless the second finger is released within the timeout. If the finger is set down again during the timeout, we move straight to TOUCH_2_HOLD - this could eventually be interpreted as a tap, but not for now. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-08-31 11:10:58 +10:00
move &gt; </text>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<text x="61235.25" y="43578.75">
touchpad: don't tap for 2fg down, followed by a single finger up The following sequence currently generates a right-button event: finger 1 down finger 2 down finger 1 up finger 2 held down This is easily triggered with short scroll events. There are two issues here: first is that the tapping code elsewhere treats any tap with a second finger down as a left-button tap, not a right button one. So if anything, we should generate a left button click here, not a right button click. Arguably, generating a button click here is wrong though, it's not a very well defined sequence and relatively difficult to trigger intentionally. So the best solution here is to simply ignore the release event and move straight back to state HOLD - unless the second finger is released within the timeout. If the finger is set down again during the timeout, we move straight to TOUCH_2_HOLD - this could eventually be interpreted as a tap, but not for now. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-08-31 11:10:58 +10:00
threshold</text>
</g>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<path d="M 61121.53 43537 L 61180.86 43553.14" fill="none" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 61185.92 43554.51 L 61178.25 43556.05 L 61180.86 43553.14 L 61180.09 43549.3 Z" fill="#000000" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 61270 43468.67 L 61364.69 43456.31" fill="none" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 61369.89 43455.63 L 61363.4 43460.01 L 61364.69 43456.31 L 61362.5 43453.07 Z" fill="#000000" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 61284 43538.73 L 61397.41 43470.29" fill="none" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 61401.9 43467.58 L 61397.72 43474.19 L 61397.41 43470.29 L 61394.1 43468.2 Z" fill="#000000" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 60907.77 43417 L 60833.79 43307.28" fill="none" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 60830.85 43302.93 L 60837.67 43306.77 L 60833.79 43307.28 L 60831.87 43310.69 Z" fill="#000000" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 61095.04 43833 C 61097.84 43829.86 61101.82 43828.05 61106.02 43828 L 61139.99 43828 C 61144.19 43828.05 61148.17 43829.86 61150.97 43833 L 61170.95 43856 C 61171.51 43857.28 61171.51 43858.72 61170.95 43860 L 61150.97 43883 C 61148.17 43886.14 61144.19 43887.95 61139.99 43888 L 61106.02 43888 C 61101.82 43887.95 61097.84 43886.14 61095.04 43883 L 61075.06 43860 C 61074.5 43858.72 61074.5 43857.28 61075.06 43856 L 61095.04 43833 Z" fill="#ffd966" stroke="#000000" stroke-width="2" stroke-miterlimit="10" pointer-events="none"/>
<g fill="#000000" font-family="Helvetica" text-anchor="middle" font-size="12px">
<text x="61122.75" y="43854.75">
touchpad: don't tap for 2fg down, followed by a single finger up The following sequence currently generates a right-button event: finger 1 down finger 2 down finger 1 up finger 2 held down This is easily triggered with short scroll events. There are two issues here: first is that the tapping code elsewhere treats any tap with a second finger down as a left-button tap, not a right button one. So if anything, we should generate a left button click here, not a right button click. Arguably, generating a button click here is wrong though, it's not a very well defined sequence and relatively difficult to trigger intentionally. So the best solution here is to simply ignore the release event and move straight back to state HOLD - unless the second finger is released within the timeout. If the finger is set down again during the timeout, we move straight to TOUCH_2_HOLD - this could eventually be interpreted as a tap, but not for now. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-08-31 11:10:58 +10:00
first</text>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<text x="61122.75" y="43868.75">
touchpad: don't tap for 2fg down, followed by a single finger up The following sequence currently generates a right-button event: finger 1 down finger 2 down finger 1 up finger 2 held down This is easily triggered with short scroll events. There are two issues here: first is that the tapping code elsewhere treats any tap with a second finger down as a left-button tap, not a right button one. So if anything, we should generate a left button click here, not a right button click. Arguably, generating a button click here is wrong though, it's not a very well defined sequence and relatively difficult to trigger intentionally. So the best solution here is to simply ignore the release event and move straight back to state HOLD - unless the second finger is released within the timeout. If the finger is set down again during the timeout, we move straight to TOUCH_2_HOLD - this could eventually be interpreted as a tap, but not for now. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-08-31 11:10:58 +10:00
finger down</text>
</g>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<path d="M 61052.4 43537 L 61115.03 43821.78" fill="none" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 61116.16 43826.91 L 61111.24 43820.82 L 61115.03 43821.78 L 61118.08 43819.32 Z" fill="#000000" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 60886.07 43142 L 61184.36 42915.85" fill="none" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 61188.54 42912.68 L 61185.08 42919.69 L 61184.36 42915.85 L 61180.85 42914.12 Z" fill="#000000" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 60895.5 43608.7 C 60911.62 43614.91 60929.38 43614.91 60945.5 43608.7 C 60961.62 43602.5 60979.38 43602.5 60995.5 43608.7 L 60995.5 43661.28 C 60979.38 43655.08 60961.62 43655.08 60945.5 43661.28 C 60929.38 43667.49 60911.62 43667.49 60895.5 43661.28 L 60895.5 43608.7 Z" fill="#ffd966" stroke="#000000" stroke-width="2" stroke-miterlimit="10" pointer-events="none"/>
touchpad: don't tap for 2fg down, followed by a single finger up The following sequence currently generates a right-button event: finger 1 down finger 2 down finger 1 up finger 2 held down This is easily triggered with short scroll events. There are two issues here: first is that the tapping code elsewhere treats any tap with a second finger down as a left-button tap, not a right button one. So if anything, we should generate a left button click here, not a right button click. Arguably, generating a button click here is wrong though, it's not a very well defined sequence and relatively difficult to trigger intentionally. So the best solution here is to simply ignore the release event and move straight back to state HOLD - unless the second finger is released within the timeout. If the finger is set down again during the timeout, we move straight to TOUCH_2_HOLD - this could eventually be interpreted as a tap, but not for now. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-08-31 11:10:58 +10:00
<g fill="#000000" font-family="Helvetica" text-anchor="middle" font-size="12px">
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<text x="60945.25" y="43638.75">
touchpad: don't tap for 2fg down, followed by a single finger up The following sequence currently generates a right-button event: finger 1 down finger 2 down finger 1 up finger 2 held down This is easily triggered with short scroll events. There are two issues here: first is that the tapping code elsewhere treats any tap with a second finger down as a left-button tap, not a right button one. So if anything, we should generate a left button click here, not a right button click. Arguably, generating a button click here is wrong though, it's not a very well defined sequence and relatively difficult to trigger intentionally. So the best solution here is to simply ignore the release event and move straight back to state HOLD - unless the second finger is released within the timeout. If the finger is set down again during the timeout, we move straight to TOUCH_2_HOLD - this could eventually be interpreted as a tap, but not for now. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-08-31 11:10:58 +10:00
TOUCH_IDLE</text>
</g>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<path d="M 60973.73 43602.5 L 61026.45 43541.81" fill="none" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 61029.89 43537.84 L 61027.95 43545.42 L 61026.45 43541.81 L 61022.66 43540.83 Z" fill="#000000" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 60991.54 43370 C 60994.34 43366.86 60998.32 43365.05 61002.52 43365 L 61036.49 43365 C 61040.69 43365.05 61044.67 43366.86 61047.47 43370 L 61067.45 43393 C 61068.01 43394.28 61068.01 43395.72 61067.45 43397 L 61047.47 43420 C 61044.67 43423.14 61040.69 43424.95 61036.49 43425 L 61002.52 43425 C 60998.32 43424.95 60994.34 43423.14 60991.54 43420 L 60971.56 43397 C 60971 43395.72 60971 43394.28 60971.56 43393 L 60991.54 43370 Z" fill="#ffd966" stroke="#000000" stroke-width="2" stroke-miterlimit="10" pointer-events="none"/>
touchpad: don't tap for 2fg down, followed by a single finger up The following sequence currently generates a right-button event: finger 1 down finger 2 down finger 1 up finger 2 held down This is easily triggered with short scroll events. There are two issues here: first is that the tapping code elsewhere treats any tap with a second finger down as a left-button tap, not a right button one. So if anything, we should generate a left button click here, not a right button click. Arguably, generating a button click here is wrong though, it's not a very well defined sequence and relatively difficult to trigger intentionally. So the best solution here is to simply ignore the release event and move straight back to state HOLD - unless the second finger is released within the timeout. If the finger is set down again during the timeout, we move straight to TOUCH_2_HOLD - this could eventually be interpreted as a tap, but not for now. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-08-31 11:10:58 +10:00
<g fill="#000000" font-family="Helvetica" text-anchor="middle" font-size="12px">
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<text x="61019.25" y="43391.75">
touchpad: don't tap for 2fg down, followed by a single finger up The following sequence currently generates a right-button event: finger 1 down finger 2 down finger 1 up finger 2 held down This is easily triggered with short scroll events. There are two issues here: first is that the tapping code elsewhere treats any tap with a second finger down as a left-button tap, not a right button one. So if anything, we should generate a left button click here, not a right button click. Arguably, generating a button click here is wrong though, it's not a very well defined sequence and relatively difficult to trigger intentionally. So the best solution here is to simply ignore the release event and move straight back to state HOLD - unless the second finger is released within the timeout. If the finger is set down again during the timeout, we move straight to TOUCH_2_HOLD - this could eventually be interpreted as a tap, but not for now. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-08-31 11:10:58 +10:00
first</text>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<text x="61019.25" y="43405.75">
touchpad: don't tap for 2fg down, followed by a single finger up The following sequence currently generates a right-button event: finger 1 down finger 2 down finger 1 up finger 2 held down This is easily triggered with short scroll events. There are two issues here: first is that the tapping code elsewhere treats any tap with a second finger down as a left-button tap, not a right button one. So if anything, we should generate a left button click here, not a right button click. Arguably, generating a button click here is wrong though, it's not a very well defined sequence and relatively difficult to trigger intentionally. So the best solution here is to simply ignore the release event and move straight back to state HOLD - unless the second finger is released within the timeout. If the finger is set down again during the timeout, we move straight to TOUCH_2_HOLD - this could eventually be interpreted as a tap, but not for now. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-08-31 11:10:58 +10:00
finger up</text>
</g>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<path d="M 61043.33 43497 L 61027.96 43431.2" fill="none" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 61026.76 43426.09 L 61031.76 43432.11 L 61027.96 43431.2 L 61024.95 43433.7 Z" fill="#000000" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 60971 43366.53 L 60864.49 43303.99" fill="none" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 60859.96 43301.33 L 60867.77 43301.86 L 60864.49 43303.99 L 60864.23 43307.9 Z" fill="#000000" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 61020.54 43893 C 61023.34 43889.86 61027.32 43888.05 61031.52 43888 L 61065.49 43888 C 61069.69 43888.05 61073.67 43889.86 61076.47 43893 L 61096.45 43916 C 61097.01 43917.28 61097.01 43918.72 61096.45 43920 L 61076.47 43943 C 61073.67 43946.14 61069.69 43947.95 61065.49 43948 L 61031.52 43948 C 61027.32 43947.95 61023.34 43946.14 61020.54 43943 L 61000.56 43920 C 61000 43918.72 61000 43917.28 61000.56 43916 L 61020.54 43893 Z" fill="#7ea6e0" stroke="#000000" stroke-width="2" stroke-miterlimit="10" pointer-events="none"/>
touchpad: don't tap for 2fg down, followed by a single finger up The following sequence currently generates a right-button event: finger 1 down finger 2 down finger 1 up finger 2 held down This is easily triggered with short scroll events. There are two issues here: first is that the tapping code elsewhere treats any tap with a second finger down as a left-button tap, not a right button one. So if anything, we should generate a left button click here, not a right button click. Arguably, generating a button click here is wrong though, it's not a very well defined sequence and relatively difficult to trigger intentionally. So the best solution here is to simply ignore the release event and move straight back to state HOLD - unless the second finger is released within the timeout. If the finger is set down again during the timeout, we move straight to TOUCH_2_HOLD - this could eventually be interpreted as a tap, but not for now. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-08-31 11:10:58 +10:00
<g fill="#000000" font-family="Helvetica" text-anchor="middle" font-size="12px">
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<text x="61048.25" y="43914.75">
touchpad: don't tap for 2fg down, followed by a single finger up The following sequence currently generates a right-button event: finger 1 down finger 2 down finger 1 up finger 2 held down This is easily triggered with short scroll events. There are two issues here: first is that the tapping code elsewhere treats any tap with a second finger down as a left-button tap, not a right button one. So if anything, we should generate a left button click here, not a right button click. Arguably, generating a button click here is wrong though, it's not a very well defined sequence and relatively difficult to trigger intentionally. So the best solution here is to simply ignore the release event and move straight back to state HOLD - unless the second finger is released within the timeout. If the finger is set down again during the timeout, we move straight to TOUCH_2_HOLD - this could eventually be interpreted as a tap, but not for now. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-08-31 11:10:58 +10:00
second</text>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<text x="61048.25" y="43928.75">
touchpad: don't tap for 2fg down, followed by a single finger up The following sequence currently generates a right-button event: finger 1 down finger 2 down finger 1 up finger 2 held down This is easily triggered with short scroll events. There are two issues here: first is that the tapping code elsewhere treats any tap with a second finger down as a left-button tap, not a right button one. So if anything, we should generate a left button click here, not a right button click. Arguably, generating a button click here is wrong though, it's not a very well defined sequence and relatively difficult to trigger intentionally. So the best solution here is to simply ignore the release event and move straight back to state HOLD - unless the second finger is released within the timeout. If the finger is set down again during the timeout, we move straight to TOUCH_2_HOLD - this could eventually be interpreted as a tap, but not for now. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-08-31 11:10:58 +10:00
finger down</text>
</g>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<path d="M 61048.02 43537 L 61048.45 43881.63" fill="none" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 61048.46 43886.88 L 61044.95 43879.89 L 61048.45 43881.63 L 61051.95 43879.88 Z" fill="#000000" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 61179.5 43960.7 C 61195.62 43966.91 61213.38 43966.91 61229.5 43960.7 C 61245.62 43954.5 61263.38 43954.5 61279.5 43960.7 L 61279.5 44013.28 C 61263.38 44007.08 61245.62 44007.08 61229.5 44013.28 C 61213.38 44019.49 61195.62 44019.49 61179.5 44013.28 L 61179.5 43960.7 Z" fill="#7ea6e0" stroke="#000000" stroke-width="2" stroke-miterlimit="10" pointer-events="none"/>
touchpad: don't tap for 2fg down, followed by a single finger up The following sequence currently generates a right-button event: finger 1 down finger 2 down finger 1 up finger 2 held down This is easily triggered with short scroll events. There are two issues here: first is that the tapping code elsewhere treats any tap with a second finger down as a left-button tap, not a right button one. So if anything, we should generate a left button click here, not a right button click. Arguably, generating a button click here is wrong though, it's not a very well defined sequence and relatively difficult to trigger intentionally. So the best solution here is to simply ignore the release event and move straight back to state HOLD - unless the second finger is released within the timeout. If the finger is set down again during the timeout, we move straight to TOUCH_2_HOLD - this could eventually be interpreted as a tap, but not for now. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-08-31 11:10:58 +10:00
<g fill="#000000" font-family="Helvetica" text-anchor="middle" font-size="12px">
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<text x="61229.25" y="43990.75">
touchpad: don't tap for 2fg down, followed by a single finger up The following sequence currently generates a right-button event: finger 1 down finger 2 down finger 1 up finger 2 held down This is easily triggered with short scroll events. There are two issues here: first is that the tapping code elsewhere treats any tap with a second finger down as a left-button tap, not a right button one. So if anything, we should generate a left button click here, not a right button click. Arguably, generating a button click here is wrong though, it's not a very well defined sequence and relatively difficult to trigger intentionally. So the best solution here is to simply ignore the release event and move straight back to state HOLD - unless the second finger is released within the timeout. If the finger is set down again during the timeout, we move straight to TOUCH_2_HOLD - this could eventually be interpreted as a tap, but not for now. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-08-31 11:10:58 +10:00
TOUCH_DEAD</text>
</g>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<path d="M 61191.5 43899.7 C 61207.62 43905.91 61225.38 43905.91 61241.5 43899.7 C 61257.62 43893.5 61275.38 43893.5 61291.5 43899.7 L 61291.5 43952.28 C 61275.38 43946.08 61257.62 43946.08 61241.5 43952.28 C 61225.38 43958.49 61207.62 43958.49 61191.5 43952.28 L 61191.5 43899.7 Z" fill="#ffd966" stroke="#000000" stroke-width="2" stroke-miterlimit="10" pointer-events="none"/>
touchpad: don't tap for 2fg down, followed by a single finger up The following sequence currently generates a right-button event: finger 1 down finger 2 down finger 1 up finger 2 held down This is easily triggered with short scroll events. There are two issues here: first is that the tapping code elsewhere treats any tap with a second finger down as a left-button tap, not a right button one. So if anything, we should generate a left button click here, not a right button click. Arguably, generating a button click here is wrong though, it's not a very well defined sequence and relatively difficult to trigger intentionally. So the best solution here is to simply ignore the release event and move straight back to state HOLD - unless the second finger is released within the timeout. If the finger is set down again during the timeout, we move straight to TOUCH_2_HOLD - this could eventually be interpreted as a tap, but not for now. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-08-31 11:10:58 +10:00
<g fill="#000000" font-family="Helvetica" text-anchor="middle" font-size="12px">
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<text x="61241.25" y="43929.75">
touchpad: don't tap for 2fg down, followed by a single finger up The following sequence currently generates a right-button event: finger 1 down finger 2 down finger 1 up finger 2 held down This is easily triggered with short scroll events. There are two issues here: first is that the tapping code elsewhere treats any tap with a second finger down as a left-button tap, not a right button one. So if anything, we should generate a left button click here, not a right button click. Arguably, generating a button click here is wrong though, it's not a very well defined sequence and relatively difficult to trigger intentionally. So the best solution here is to simply ignore the release event and move straight back to state HOLD - unless the second finger is released within the timeout. If the finger is set down again during the timeout, we move straight to TOUCH_2_HOLD - this could eventually be interpreted as a tap, but not for now. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-08-31 11:10:58 +10:00
TOUCH_DEAD</text>
</g>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
<path d="M 61171.5 43885.83 L 61185.98 43894.14" fill="none" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 61190.53 43896.75 L 61182.72 43896.3 L 61185.98 43894.14 L 61186.2 43890.23 Z" fill="#000000" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 61291.5 43931.69 L 61705.92 43978.88" fill="none" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 61711.14 43979.47 L 61703.79 43982.16 L 61705.92 43978.88 L 61704.58 43975.2 Z" fill="#000000" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 61097 43936.49 L 61173.55 43965.67" fill="none" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 61178.46 43967.54 L 61170.67 43968.32 L 61173.55 43965.67 L 61173.16 43961.78 Z" fill="#000000" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 61279.5 43987 L 61705.88 43987" fill="none" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
<path d="M 61711.13 43987 L 61704.13 43990.5 L 61705.88 43987 L 61704.13 43983.5 Z" fill="#000000" stroke="#000000" stroke-miterlimit="10" pointer-events="none"/>
touchpad: disable tapping for fingers exceeding the timeout/motion threshold The current code triggers multi-finger tapping even if the finger released was previously held on the touchpad for a while. For an event sequence of: 1. first finger down 2. first finger move past threshold/wait past timeout 3. second finger down 4. first finger up The second finger initiates the two-finger tap state, but the button event is sent when the first finger releases - despite that finger not meeting the usual tap constraints. This sequence can happen whenever a user swaps fingers. Add the finger state to the actual touchpoints and update them whenever the constrains are broken. Then, discard button events if the respective touch did not meet the conditions. http://bugs.freedesktop.org/76760 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2014-06-20 14:16:13 +10:00
</g>
</svg>
touchpad: fix the number of button clicks in multitap tap-tap-down-move should emit 1 click + press, not 2 clicks + press https://bugs.freedesktop.org/show_bug.cgi?id=92016 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-09-18 09:14:43 +10:00
Reference in a new issue Copy permalink