There have been a lot of questions asked lately about versioning of
interfaces and protocol objects. This addition to the documentation should
clear up some of those questions.
Signed-off-by: Jason Ekstrand
---
doc/publican/sources/Protocol.xml | 63 +++
1 fi
The method described of alocation IDs has been wrong at least since version
1.0. This commit updates it to correspond to the way IDs are chosen in
versions >= 1.0.
Signed-off-by: Jason Ekstrand
---
doc/publican/sources/Protocol.xml | 14 ++
1 file changed, 10 insertions(+), 4 deleti
2013/8/17 Peter Hutterer :
> on-screen keyboards have a one-to-one mapping. you press the button, you
> generate a key event. you don't have to worry about speed of pointer
> movement, direction of pointer movemnt, relative position of touchpoints (if
> multiple are present, etc.). the complexit
Hi
On Sat, Aug 17, 2013 at 9:49 AM, Peter Hutterer
wrote:
> On Thu, Aug 15, 2013 at 02:48:48PM -0700, Kristian Høgsberg wrote:
>> On Thu, Aug 15, 2013 at 12:10:30PM +0100, Daniel Stone wrote:
>> > Hi,
>> >
>> > On 15 August 2013 11:52, Peter Hutterer wrote:
>> > > one of the things that should b
On Thu, Aug 15, 2013 at 07:59:29PM +0600, Alexander E. Patrakov wrote:
> 2013/8/15 Peter Hutterer :
>
> > one of the things that should be done is to figure out _where_ features such
> > as this are going to be handled. In the compositor, the compositor's input
> > module, on the client side, ...
On Thu, Aug 15, 2013 at 02:48:48PM -0700, Kristian Høgsberg wrote:
> On Thu, Aug 15, 2013 at 12:10:30PM +0100, Daniel Stone wrote:
> > Hi,
> >
> > On 15 August 2013 11:52, Peter Hutterer wrote:
> > > one of the things that should be done is to figure out _where_ features
> > > such
> > > as this
