On Thu, Feb 20, 2014 at 08:39:08AM +0100, Jonas Ådahl wrote:
> On Thu, Feb 20, 2014 at 02:53:18PM +1000, Peter Hutterer wrote:
> > On Wed, Feb 19, 2014 at 10:04:10PM +0100, Jonas Ådahl wrote:
> > > Since a Wayland compositor have to represent all touch devices of a seat
> > > as one virtual device,
On Thu, Feb 20, 2014 at 02:53:18PM +1000, Peter Hutterer wrote:
> On Wed, Feb 19, 2014 at 10:04:10PM +0100, Jonas Ådahl wrote:
> > Since a Wayland compositor have to represent all touch devices of a seat
> > as one virtual device, lets make that easier by also providing seat wide
> > slots with tou
On Thu, Feb 20, 2014 at 12:21:53PM +0600, Alexander E. Patrakov wrote:
> 20.02.2014 11:14, Peter Hutterer wrote:
> >On Wed, Feb 19, 2014 at 11:55:28AM +0600, Alexander E. Patrakov wrote:
> >>19.02.2014 04:52, Peter Hutterer wrote:
> >>>The set of touchpad patches I sent out recently already handle
20.02.2014 11:14, Peter Hutterer wrote:
On Wed, Feb 19, 2014 at 11:55:28AM +0600, Alexander E. Patrakov wrote:
19.02.2014 04:52, Peter Hutterer wrote:
The set of touchpad patches I sent out recently already handle this by
default. When the physical clickpad button is depressed, the driver picks
On Wed, Feb 19, 2014 at 11:55:28AM +0600, Alexander E. Patrakov wrote:
> 19.02.2014 04:52, Peter Hutterer wrote:
> >The set of touchpad patches I sent out recently already handle this by
> >default. When the physical clickpad button is depressed, the driver picks
> >the finger that is pressing the
On Wed, Feb 19, 2014 at 10:04:11PM +0100, Jonas Ådahl wrote:
> Instead of having one touch events representing different types of touch
> events by providing a touch type, have one separate event type per touch
> type. This means the LIBINPUT_EVENT_TYPE_TOUCH is replaced with
> LIBINPUT_EVENT_TYPE_
On Wed, Feb 19, 2014 at 10:04:10PM +0100, Jonas Ådahl wrote:
> Since a Wayland compositor have to represent all touch devices of a seat
> as one virtual device, lets make that easier by also providing seat wide
> slots with touch events.
>
> Seat wide slots may be accessed using
> libinput_event_t
On Tue, Feb 18, 2014 at 07:44:54PM -0800, Thiago Macieira wrote:
> Em ter 18 fev 2014, às 22:33:26, Jasper St. Pierre escreveu:
> > ... and what if it fails? I'd say that requiring CLOCK_MONOTONIC is fine.
> >
> > Are there any popular Linux setups that don't have CLOCK_MONOTONIC?
>
> I'm guessin
On Wed, Feb 19, 2014 at 07:19:15PM +0100, Rui Tiago Cação Matos wrote:
> On 19 February 2014 13:35, Daniel Stone wrote:
> > Can this be CLOCK_MONOTONIC_COARSE instead, to avoid griefing HPET and
> > thus causing much higher power usage?
>
> Makes sense and indeed the X server seems to use _COARSE
Instead of having one touch events representing different types of touch
events by providing a touch type, have one separate event type per touch
type. This means the LIBINPUT_EVENT_TYPE_TOUCH is replaced with
LIBINPUT_EVENT_TYPE_TOUCH_DOWN, LIBINPUT_EVENT_TYPE_TOUCH_MOTION,
LIBINPUT_EVENT_TYPE_TOU
Since a Wayland compositor have to represent all touch devices of a seat
as one virtual device, lets make that easier by also providing seat wide
slots with touch events.
Seat wide slots may be accessed using
libinput_event_touch_get_seat_slot().
Signed-off-by: Jonas Ådahl
---
src/evdev.c
On 19 February 2014 13:35, Daniel Stone wrote:
> Can this be CLOCK_MONOTONIC_COARSE instead, to avoid griefing HPET and
> thus causing much higher power usage?
Makes sense and indeed the X server seems to use _COARSE if it's
available and has good enough resolution:
http://cgit.freedesktop.org/x
On 02/19/2014 02:42 AM, Pekka Paalanen wrote:
Besides, it's not that much code, really. clients/nested.c is 1140
lines, and that includes support for EGL-passthrough so that
nested-client.c can efficiently use GLES rendering.
Sample code like this does help a lot.
I would still be worried tha
Hi Guys,
Following to the giant and impossible to read "Authorized clients"
thread, I said I would take the time and write everything we talked
about down, for convenience and to check I took everyone's idea and
needs into account.
I published the whole article on my blog [1] but I also want
Hi.
About 10 months or so ago, there where patches submitted by Rob Bradford. I
chose to ping the list as I think that what they implement is useful to desktop
users.
http://lists.freedesktop.org/archives/wayland-devel/2013-April/008836.html
http://lists.freedesktop.org/archives/wayland-devel/2
Hi Pekka, and thanks a lot for your review !
I changed my code, taking your comments into consideration. Here are the
details :
> New events should be added last, so they do not change the opcodes of
existing events.
Ouch. You are right. I just reversed the order, so "add_managed_surface" is
now
Hi,
On 18 February 2014 22:47, Peter Hutterer wrote:
> Avoids erroneous timestamps when the system time is reset. This used to a be a
> problem with the X.Org synaptics driver where taps, scrolling and a couple of
> other things would potentially lock up.
Can this be CLOCK_MONOTONIC_COARSE inste
On Tue, 18 Feb 2014 23:58:41 -0800
Bill Spitzak wrote:
> Okay, a bit more luck, in that I can compile weston.
>
> I mostly discovered that there are parts of mesa you just cannot turn
> off, no matter how much you are certain they are not used. Mesa
> internally has calls into various function
On Wed, 19 Feb 2014 06:18:18 +0100
Manuel Bachmann wrote:
> We create a new "managed_surface" object which will track
> a surface compositor-side, and receive events shell-side
> to handle 3 cases :
> - a toplevel surface has been created ;
> - a toplevel surface has been destroyed ;
> - a toplev
On Tue, 18 Feb 2014 19:09:45 + (GMT)
Mark Thomas wrote:
> On Mon, 17 Feb 2014, Bill Spitzak wrote:
>
> > I do believe users are looking for something more like this than for
> > implementing a subcompositor. Subcompositor really worries me as it relies
> > on
> > the buffers being passed
On Tue, 18 Feb 2014 11:12:01 -0800
Bill Spitzak wrote:
> Maybe you can correct my guess as to how all this software talks to each
> other:
>
> 1. An EGL-using wayland client talks to mesa's libEGL.
You have to ensure it actually gets the Mesa version of libEGL.
> 2. Somehow mesa decides to us
On Tue, 18 Feb 2014 16:43:15 +0200
Pekka Paalanen wrote:
> From: Pekka Paalanen
>
> "the callback event will arrive after the next output refresh" is wrong,
> if you interpret "output refresh" as framebuffer flip or the moment when
> the new pixels turn into light the first time. Weston has pro
On 10/02/14 21:17, Daniel Stone wrote:
> Hi,
>
> On 10 February 2014 13:23, Emilio Pozuelo Monfort wrote:
>> When a view was destroyed while we were on exposay, we didn't
>> remove it from the list of views, and so when leaving exposay
>> we were trying to animate (and sometimes activate) a
>> no
On Tue, 18 Feb 2014 18:34:24 +0100
Axel Davy wrote:
> Hi,
> > If you read the above paragraph carefully, you see that the last
> > sentence CHANGES EXISTING WAYLAND CORE PROTOCOL BEHAVIOUR.
> >
> > The change is very subtle. It means, that without a wl_surface.attach,
> > the buffer state is no l
24 matches
Mail list logo
