Question about multi-displays control on wayland protocol‏

2014-10-08 Thread Yang Andy
Hello everyone I have one question about multi-displays control on wayland protocol. I want to control dual displays on wayland protocol. For example,Display1 which is used to render map,while display2 which is used to render mp3-palyer. Could anyone give me some advice about how to design the

Re: [PATCH libinput] Fix normalization functions

2014-10-08 Thread Peter Hutterer
On Wed, Oct 08, 2014 at 02:53:21PM -0700, Jason Gerecke wrote: > We need to *subtract*, not *add* the minimum to determine the > range-effective value. For example: if (min, current, max) is > (100, 100, 1000) then the normalized value would be 0.0, not 0.2. woopsie. applied, thanks. Cheers, P

Re: [PATCH libinput] Fix normalization functions

2014-10-08 Thread Bill Spitzak
That certainly looks correct, but this code will return a value less than 1.0 when absinfo->value == absinfo->maximum. Is this correct? If it is supposed to be 1.0 then I would remove the +1 in the line that computes range. On 10/08/2014 02:53 PM, Jason Gerecke wrote: We need to *subtract*, n

Re: [PATCH weston] input: don't send to clients key events eaten by bindings

2014-10-08 Thread Bill Spitzak
On 10/08/2014 03:25 PM, Jasper St. Pierre wrote: I was under the impression that what the client got was an xkb state that showed that the keys were held down. Actual events caused by pressing keys were different and distinguishable by the client. X clients cannot distinguish betwee

Re: [PATCH weston] input: don't send to clients key events eaten by bindings

2014-10-08 Thread Jasper St. Pierre
On Wed, Oct 8, 2014 at 3:23 PM, Bill Spitzak wrote: > On 10/08/2014 11:58 AM, Giulio Camuffo wrote: > > A key being held down on focus-in will not produce a "press" event, so I >>> don't see what the problem is. >>> >> >> It produces a KeyPress in xwayland. >> > > Okay that may be a problem. So

Re: [PATCH weston] input: don't send to clients key events eaten by bindings

2014-10-08 Thread Bill Spitzak
On 10/08/2014 11:58 AM, Giulio Camuffo wrote: A key being held down on focus-in will not produce a "press" event, so I don't see what the problem is. It produces a KeyPress in xwayland. Okay that may be a problem. So you are saying the client cannot distinguish between keys that were held d

[PATCH libinput] Fix normalization functions

2014-10-08 Thread Jason Gerecke
We need to *subtract*, not *add* the minimum to determine the range-effective value. For example: if (min, current, max) is (100, 100, 1000) then the normalized value would be 0.0, not 0.2. Signed-off-by: Jason Gerecke --- This patch should be applied to the 'tablet-support' branch, obviously. ..

Re: [PATCH weston] input: don't send to clients key events eaten by bindings

2014-10-08 Thread Giulio Camuffo
2014-10-08 21:00 GMT+03:00 Bill Spitzak : > > > On 10/08/2014 01:41 AM, Giulio Camuffo wrote: >> >> 2014-10-08 0:50 GMT+03:00 Bill Spitzak : >>> >>> I really can't imagine this is a problem, and clients may even expect the >>> current behavior. It certainly is expected for shift keys: if I alt+tab

Re: [PATCH weston] input: don't send to clients key events eaten by bindings

2014-10-08 Thread Bill Spitzak
On 10/08/2014 01:41 AM, Giulio Camuffo wrote: 2014-10-08 0:50 GMT+03:00 Bill Spitzak : I really can't imagine this is a problem, and clients may even expect the current behavior. It certainly is expected for shift keys: if I alt+tab to a program it acts like alt is still held down. A quick tes

Re: [PATCH 2/4] event-loop.c: Use correct OS abstraction function for dupfd()

2014-10-08 Thread Marek Chalupa
Reviewed-by: Marek Chalupa On 28 September 2014 20:49, Karsten Otto wrote: > From: Philip Withnall > > Signed-off-by: Philip Withnall > --- > src/event-loop.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/src/event-loop.c b/src/event-loop.c > index a149db9..1f571ba

Re: [PATCH 3/4] queue-test: Add another assertion

2014-10-08 Thread Marek Chalupa
Hi, yes, this is normal in tests - the fact is that without assert the tests won't compile anyway, as Otto wrote, so the asserts are always present there. This patch is: Reviewed-by: Marek Chalupa On 29 September 2014 08:09, Karsten Otto wrote: > Indeed, I just followed the lead of the other

Re: [PATCH 4/4] wayland-server: Abort if a read from a client gives 0 length

2014-10-08 Thread Marek Chalupa
Yes, in wayland-client it is used this way. wl_connection_read returns number of bytes buffered in connection after reading (which should be positive value if reading was OK), otherwise it returns return value of recvmsg, which allows to distinguish between error and hangup (-1 and 0). What I was

Re: [PATCH wayland 0/4] Implement role conflict errors

2014-10-08 Thread Pekka Paalanen
On Wed, 1 Oct 2014 08:45:50 -0600 "Jasper St. Pierre" wrote: > Thanks for taking this on. I'm disappointed about the duplication, but if > somebody else does the work, I can't really complain. > > The whole series is: > > Reviewed-by: Jasper St. Pierre > > On Wed, Oct 1, 2014 at 7:50 AM, Pekk

Re: [PATCH weston] input: don't send to clients key events eaten by bindings

2014-10-08 Thread Giulio Camuffo
2014-10-08 0:50 GMT+03:00 Bill Spitzak : > I really can't imagine this is a problem, and clients may even expect the > current behavior. It certainly is expected for shift keys: if I alt+tab to a > program it acts like alt is still held down. A quick test on Ubuntu shows > that a program you alt+ta