Yeah, I think this looks ok.
Reviewed-by: Jason Ekstrand
On Mon, Jul 28, 2014 at 4:06 AM, Pekka Paalanen wrote:
> From: Pekka Paalanen
>
> It looks like that in the great conversion introducing weston_view, one
> conditional was forgotten from the code that builds the global flat list
> of v
On Mon, 28 Jul 2014 16:40:31 -0700
Bill Spitzak wrote:
> On 07/28/2014 02:49 PM, Jasper St. Pierre wrote:
>
> > Try looking at the code next time. It creates a temporary file, unlinks
> > the file, writes the XKB description to it using xkb_map_get_as_string,
> > and sends it over.
>
> Okay I t
On 29 July 2014 00:40, Bill Spitzak wrote:
> I am unconvinced that any real clients will actually do this
>
They do. They all do.
> It seems like this should be implemented by having "Alt+V" translate to
> the "Paste" keysym.
>
No, this falls apart because ... well, no, I'm not going to repea
On 07/28/2014 02:49 PM, Jasper St. Pierre wrote:
Try looking at the code next time. It creates a temporary file, unlinks
the file, writes the XKB description to it using xkb_map_get_as_string,
and sends it over.
Okay I think I see this now. I'm not sure why there is a cutoff between
sizes sen
On Mon, Jul 28, 2014 at 11:36 PM, Bill Spitzak wrote:
> Yes I saw that, but it is a file descriptor. My reading was that a client
> machine must have somewhere in it's file system every possible keyboard
> that could be on a remote machine. That is actually what led to my question.
>
Try looking
Yes I saw that, but it is a file descriptor. My reading was that a
client machine must have somewhere in it's file system every possible
keyboard that could be on a remote machine. That is actually what led to
my question.
I suppose the xkb description can be sent: the local compositor would
Init cursor size to 64x64 if drmGetCap() fails.
Use Mesa GBM_BO_USE_CURSOR define (which removes 64x64 restriction)
Signed-off-by: Alvaro Fernando García
---
src/compositor-drm.c | 41 ++---
1 file changed, 34 insertions(+), 7 deletions(-)
diff --git a/src/c
On Mon, Jul 28, 2014 at 7:44 PM, Bill Spitzak wrote:
> I am just going to have to study this further, because I am still
> completely stumped as to why so many people think this is an acceptable
> solution.
>
> This sounds to me like either the ability to transmit an entire xkb
> description acro
On 07/28/2014 09:41 AM, Jason Gerecke wrote:
Normalizing the data is fine, but the resolution data needs to be
available somewhere as well. The GTK+ API doesn't require anything
more than the former, but Qt requires that there be some way to turn
the normalized value into degrees. For libinput t
I am just going to have to study this further, because I am still
completely stumped as to why so many people think this is an acceptable
solution.
This sounds to me like either the ability to transmit an entire xkb
description across the wire is added to the wayland protocol, or that
there i
On 07/27/2014 11:48 PM, Ran Benita wrote:
Hi Jonas,
On Sun, Jul 27, 2014 at 11:28:28PM +0200, Jonas Ådahl wrote:
The kernel may send a 'release' event without ever having sent a key
'pressed' event in case the key was pressed before libinput was
initiated. Ignore these events so that we alway
On Wed, Jul 16, 2014 at 5:08 PM, Lyude wrote:
> On Mon, 2014-07-14 at 13:25 -0700, Jason Gerecke wrote:
>> On Sun, Jul 13, 2014 at 12:17 PM, Lyude wrote:
>> >wl_tablet specifications
>> > Version 2
>> >
>> > General notes:
>> > - Many
From: Pekka Paalanen
It looks like that in the great conversion introducing weston_view, one
conditional was forgotten from the code that builds the global flat list
of views. Sub-surfaces are added to the view list specially, as they are
not governed by their presence in a layer's view list, and
2014-07-28 13:19 GMT+03:00 Daniel Stone :
> Hi Eugen,
>
> On 27 July 2014 22:16, Eugen Friedrich wrote:
>>
>> Hi Daniel,
>>
>> thanks, i understood we should add the wl_display_dispatch_pending call in
>> the application
>> there is currently no way to avoid this and basically it does not harm.
>>
Hi Eugen,
On 27 July 2014 22:16, Eugen Friedrich wrote:
> Hi Daniel,
>
> thanks, i understood we should add the wl_display_dispatch_pending call
> in the application
> there is currently no way to avoid this and basically it does not harm.
> I only wanted to understand if there is something miss
Le 25/07/2014 22:08, Bill Spitzak a écrit :
> On 07/25/2014 11:59 AM, Daniel Stone wrote:
>> Since you're just repeating yourself without taking on anything that's
>> been said, so will I: that won't work.
>
> This I am finding hard to believe.
>
> My proposal is that the compositor maintain a xk
On Mon, Jul 28, 2014 at 09:48:05AM +0300, Ran Benita wrote:
> Hi Jonas,
>
> On Sun, Jul 27, 2014 at 11:28:28PM +0200, Jonas Ådahl wrote:
> > The kernel may send a 'release' event without ever having sent a key
> > 'pressed' event in case the key was pressed before libinput was
> > initiated. Ignor
2014-07-27 22:50 GMT+03:00 Eugen Friedrich :
> O thanks for the hint about mailing list,
> and for clarification on the dispatching logic(I'm not original English
> speaker and assume "havok" is like behavior? )
"to break havoc" means creating trouble ;).
>
>
>
> 2014-07-27 21:33 GMT+02:00 Giulio
18 matches
Mail list logo
