summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* inputproto 2.2inputproto-2.2Peter Hutterer2012-03-021-1/+1
| | | | Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
* specs: XI 2.2 release date is March 2012Peter Hutterer2012-03-021-1/+1
| | | | | Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Chase Douglas <chase.douglas@canonical.com>
* specs: Remove work in progress warningPeter Hutterer2012-03-021-2/+0
| | | | | | | We're close enough to a release now. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Chase Douglas <chase.douglas@canonical.com>
* specs: remove "since" from TouchOwnershipEventPeter Hutterer2012-03-021-1/+1
| | | | | | | It's already in a section "Events introduced in version 2.2" Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Chase Douglas <chase.douglas@canonical.com>
* specs: remove TouchOwnership mention from DeviceEventPeter Hutterer2012-03-021-2/+1
| | | | | | | TouchOwnership is described separately below. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Chase Douglas <chase.douglas@canonical.com>
* specs: whitespace fix to avoid wrong asciidoc formattingPeter Hutterer2012-03-021-4/+3
| | | | | Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Chase Douglas <chase.douglas@canonical.com>
* specs: fix link to touch ownership sectionPeter Hutterer2012-03-021-4/+5
| | | | | | | Introduced in 535a4377ddb4c2680d54b4cbbb273134bb5f58a3 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Chase Douglas <chase.douglas@canonical.com>
* specs: GrabtypeTouchBegin was added in XI 2.2Peter Hutterer2012-03-021-1/+1
| | | | | Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Chase Douglas <chase.douglas@canonical.com>
* specs: formatting fix, move AcceptTouch and RejectTouch onto their own linePeter Hutterer2012-03-021-2/+2
| | | | | Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Chase Douglas <chase.douglas@canonical.com>
* specs: replace † with ²Peter Hutterer2012-03-021-15/+15
| | | | | | | | | | † looks too much like a letter and we can't use * and ** because asciidoc interprets it as lists. Use numbers instead, and replace all current * with ¹. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Chase Douglas <chase.douglas@canonical.com>
* specs: XITouchClass doesn't have propertiesPeter Hutterer2012-03-021-7/+1
| | | | | | | Leftover from an earlier version. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Chase Douglas <chase.douglas@canonical.com>
* specs: Formatting fixPeter Hutterer2012-03-021-2/+4
| | | | | | | | asciidoc requires caption to be on one line but this one here is too long. Split it up instead. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Chase Douglas <chase.douglas@canonical.com>
* specs: some wording fixesPeter Hutterer2012-03-021-13/+10
| | | | | | | | | | | | | | | | | | Button press events are insufficient even on scroll wheels, so don't say they are good enough. Remove duplicate claim of event emulation Don't claim we send touch events "without delay" Touch screens hardly ever "physically move" an object. Hyphenate "implementation-dependent" Remove unnecessary "however" Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Chase Douglas <chase.douglas@canonical.com>
* specs: fix typos 'hierachy' → 'hierarchy'Peter Hutterer2012-03-021-8/+8
| | | | | Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Chase Douglas <chase.douglas@canonical.com>
* Unbreak protocol ABI for XIAllowEvents - inputproto 2.1.99.6inputproto-2.1.99.6Peter Hutterer2012-02-092-3/+18
| | | | | | | | | | | | | | XIAllowEvents was extended with touchid and grab_window in 2ea2f99f4fe1dcd3b8e539ca41c482fc40a0533d. This extended the size of the request from 12 to 20 but also broke the ABI. Older server match the request size exactly, so compiling libXi 1.5 against inputproto 2.2 and then running it against a pre-XI 2.2 server causes a BadLength for any XIAllowEvent request. Add a new request for the new data. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Keith Packard <keithp@keithp.com>
* specs: explain touch behaviour for dependent devicesPeter Hutterer2012-02-021-0/+50
| | | | | | | | | | | | | | | | | | | Dependent devices don't send touch events until the interaction is a true touch interaction (i.e. doesn't just serve to move the pointer). Once that happens, all touchpoints send touch events exclusively. Pointer movement restarts once we're down to one touch that controls the pointer again. For clients listening to touch events in addition to pointer events, this also means that a two-finger tap looks identical to holding one finger down and tapping with a second-finger. Both actions will result in short TouchBegin/TouchEnd sequences for both fingers. The above is the default behaviour we expect from touchpads, the protocol is more generically worded to leave more room for drivers to decide when a touch only controls the pointer and when it doesn't. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Chase Douglas <chase.douglas@canonical.com>
* specs: move touch support details to "Touch device support" sectionPeter Hutterer2012-01-311-20/+23
| | | | | | | Keep the changelog small. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Chase Douglas <chase.douglas@canonical.com>
* specs: remove superfluous "Changes introduced by ..."Peter Hutterer2012-01-311-2/+0
| | | | | | | The line right above says the same thing. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Chase Douglas <chase.douglas@canonical.com>
* specs: move touch mode explanations to where it belongsPeter Hutterer2012-01-311-14/+7
| | | | | | | | | Rather than have two different explanations to the touch modes, remove it from the "Changes in version 2.2" section and merge the content into the text. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Chase Douglas <chase.douglas@canonical.com>
* specs: replace hard coded number in some "See section" referencesGaetan Nadon2012-01-261-8/+10
| | | | | | | | The glossary does not accept <<links>> however. Signed-off-by: Gaetan Nadon <memsize@videotron.ca> Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Chase Douglas <chase.douglas@canonical.com>
* specs: fix Appendix A titleGaetan Nadon2012-01-261-1/+1
| | | | | | | | This section starts a new numbered sequence. Signed-off-by: Gaetan Nadon <memsize@videotron.ca> Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Chase Douglas <chase.douglas@canonical.com>
* specs: remove older manually typed in section numberGaetan Nadon2012-01-261-6/+6
| | | | | | | | These would come out in html as 5.2, 6.3 and 6.4.3.4 Signed-off-by: Gaetan Nadon <memsize@videotron.ca> Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Chase Douglas <chase.douglas@canonical.com>
* specs: use subsections to group use cases descriptionGaetan Nadon2012-01-261-28/+28
| | | | | | | | | It makes an entry in the appendix for quick navigation. It looks more readable with subtitles. Signed-off-by: Gaetan Nadon <memsize@videotron.ca> Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Chase Douglas <chase.douglas@canonical.com>
* specs: Edit titles for section 3 and 4Gaetan Nadon2012-01-261-4/+4
| | | | | | | | | | | In the htlm version, the section number appeared to be 3.2.1 and 4.2.2 because of the generated section number. A section title should not begin with a number. Signed-off-by: Gaetan Nadon <memsize@videotron.ca> Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Chase Douglas <chase.douglas@canonical.com>
* inputproto 2.1.99.5inputproto-2.1.99.5Peter Hutterer2012-01-061-1/+1
| | | | Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
* Set a flag on the pointer-emulating touch eventPeter Hutterer2012-01-032-2/+7
| | | | | | | | | | | | | | | | | Toolkits need to know which touch event emulated a pointer event and which ones do not. To quote Carlos Garnacho: GTK+ does client-side windows by default (GdkWindows without a backing X window), for this to work the toplevel window in the client needs to select for more events that it wouldn't normally select for in order to cater for the event masks in such child "windows". This means that ideally GTK+ should set the touch events mask in the toplevel, and then find out whether the "window" would receive pointer or touch events for the sequence emulating the pointer, and perform the emulation itself. Reported-by: Carlos Garnacho <carlosg@gnome.org> Reviewed-by: Chase Douglas <chase.douglas@canonical.com> Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
* specs: purge leftover TouchAccepted notePeter Hutterer2012-01-031-3/+0
| | | | | | | This flag does not exist anymore. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Chase Douglas <chase.douglas@canonical.com>
* specs: only pointer events have a PointerEmulated flagPeter Hutterer2012-01-031-1/+1
| | | | | Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Chase Douglas <chase.douglas@canonical.com>
* specs: Clarify rejection for touch events on current ownerPeter Hutterer2012-01-031-5/+10
| | | | | | | | | | The current owner never gets a TouchUpdate(PendingEnd), that event is superfluous for the owner. The owner receives a TouchEnd when the touch physically ends. If the touch is still active, the owner receives a TouchEnd after rejecting the touch. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Chase Douglas <chase.douglas@canonical.com>
* inputproto 2.1.99.4inputproto-2.1.99.4Peter Hutterer2011-12-211-1/+1
| | | | Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
* Merge branch 'multitouch-devel'Peter Hutterer2011-12-214-109/+750
|\ | | | | | | | | | | Conflicts: configure.ac specs/XI2proto.txt
| * specs: add XI 2.1 release to history sectionPeter Hutterer2011-12-211-0/+2
| | | | | | | | Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
| * Remove --enable-unstable-protocol configure optionPeter Hutterer2011-12-211-8/+0
| | | | | | | | | | | | | | | | Protocol is reasonably stable and about to be merged onto the master branch. People should be used to stuff on master being a tad unstable, don't require any specific configure flags. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
| * specs: remove parts of the "Work in progress" warningPeter Hutterer2011-12-211-12/+0
| | | | | | | | | | | | The protocol is stable enough now that a simple warning should be enough. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
| * Reinstate libXi's version definesmultitouch-develPeter Hutterer2011-12-201-0/+11
| | | | | | | | | | | | | | | | | | | | | | Realistically, we can't remove these from the protocol without breaking older libraries. Introduced in a02566ca7fd37d279b957037e1251a3b3419866d Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Chase Douglas <chase.douglas@canonical.com> Signed-off-by: Chase Douglas <chase.douglas@canonical.com>
| * Drop wrong comment for sourceid in TouchOwnershipEventsPeter Hutterer2011-12-201-1/+1
| | | | | | | | | | | | | | | | Copy/paste error from DeviceChangedEvent Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Chase Douglas <chase.douglas@canonical.com> Signed-off-by: Chase Douglas <chase.douglas@canonical.com>
| * specs: Fix tiny typo.Cyril Brulebois2011-12-161-1/+1
| | | | | | | | | | | | Signed-off-by: Cyril Brulebois <kibi@debian.org> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
| * specs: clarify button state in touch eventsPeter Hutterer2011-12-141-2/+7
| | | | | | | | | | | | | | | | | | Emulated pointer events will have button 1 logically down, but touch events only represent the actual button state, irrespective of the touches. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Chase Douglas <chase.douglas@canonical.com> Signed-off-by: Chase Douglas <chase.douglas@canonical.com>
| * specs: drop leftover from active_touches removalPeter Hutterer2011-12-141-5/+0
| | | | | | | | | | | | Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Chase Douglas <chase.douglas@canonical.com> Signed-off-by: Chase Douglas <chase.douglas@canonical.com>
| * inputproto 2.1.99.3inputproto-2.1.99.3Chase Douglas2011-12-131-1/+1
| | | | | | | | Signed-off-by: Chase Douglas <chase.douglas@canonical.com>
| * State that future touch IDs are indeterminateChase Douglas2011-12-121-3/+5
| | | | | | | | | | | | | | | | | | | | | | This just makes it absolutely clear that clients should not make any assumptions about future touch ID values. I also added "strictly monotonically" increasing to the definition of touch IDs. It's a more precise definition of the protocol. Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> Signed-off-by: Chase Douglas <chase.douglas@canonical.com>
| * Touch IDs must be globally uniqueChase Douglas2011-12-121-1/+1
| | | | | | | | | | | | | | | | | | | | XIAllowEvents with a master device and a touch ID must uniquely identify a touch sequence. If touch IDs were unique per slave device, multiple slave devices could have valid sequences with the same touch ID, and the sequences may both be grabbed through the same master device grab. Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> Signed-off-by: Chase Douglas <chase.douglas@canonical.com>
| * Remove XI2.1 and XI2.2 warnings and errorsPeter Hutterer2011-12-121-10/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | This is too much of a pain, anyone who includes XI headers needs to define this. And that affects input and output drivers as well as legacy clients that don't even need the new stuff. Removing the need for defines would be enough but then the warnings clog up the output and hide real warnings. Just ditch them and laugh at those that use an experimental branch and expect it to work. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Chase Douglas <chase.douglas@canonical.com> Signed-off-by: Chase Douglas <chase.douglas@canonical.com>
| * inputproto 2.1.99.2inputproto-2.1.99.2Peter Hutterer2011-11-111-1/+1
| | | | | | | | Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
| * XI2: Use touchid, not touch_id in XIAllowEventsPeter Hutterer2011-11-042-3/+3
| | | | | | | | | | | | | | Be consistent with other usages of touchid. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Chase Douglas <chase.douglas@canonical.com>
| * XI2: swap (Raw)TouchUpdate and (Raw)TouchEndPeter Hutterer2011-11-031-6/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | Not having the event codes in the order begin/update/end does my head in when debugging. It also means there's no symmetry between raw and normal touch events as the ownership event is wedged in between. Rearrange event codes to be Begin/Update/End for both, with the OwnershipEvent being in between. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Chase Douglas <chase.douglas@canonical.com> Reviewed-by: Jeremy Huddleston <jeremyhu@apple.com> Signed-off-by: Chase Douglas <chase.douglas@canonical.com>
| * Revert addition of active_touches to device eventsChase Douglas2011-09-162-7/+0
| | | | | | | | | | | | | | | | | | | | | | I can't remember why it's there, and I don't see how it may be useful. If a client really wants to know how many touches are on the device, they can listen to raw events and count the number of active touches. (Real reason: extending events is hard :) Signed-off-by: Chase Douglas <chase.douglas@canonical.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net>
| * Fix Xi 2.x version comment in XI2.hChase Douglas2011-09-141-1/+1
| | | | | | | | Signed-off-by: Chase Douglas <chase.douglas@canonical.com>
| * inputproto 2.1.99.1 (first snapshot of 2.2)inputproto-2.1.99.1Chase Douglas2011-09-141-1/+1
| | | | | | | | | | | | | | Note that this is built on top of 2.0.99.1, which is a development snapshot of 2.1. Signed-off-by: Chase Douglas <chase.douglas@canonical.com>
| * Allow grabbing clients to accept or reject touches any timeChase Douglas2011-09-142-11/+20
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This is potentially both a performance and client complexity improvement. An example is a gesture recognizer using touch grabs on each window with a subscription. If events on a child window are known to not match any subscription on the child window, then the client should be able to reject the touch grab even if the parent window hasn't accepted any of the touches, perhaps because the parent window gesture hasn't timed out or crossed other thresholds yet. As an inverse example, the events may match a child window subscription before the root window has rejected ownership. The child window should be able to accept the touch proactively. This allows for further clients to receive a TouchEnd event earlier, and means the client may be able to reduce state being tracked. If this were not allowed, the client would need to wait until it received ownership before accepting the sequence. Signed-off-by: Chase Douglas <chase.douglas@canonical.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net>
View Lorry Controller Status