On Wed, Sep 23, 2015 at 12:10:02PM -0700, Bill Spitzak wrote:
> Seems like the wl_display.sync() can do the job. The compositor may send
> several configure events, that is harmless. Just use the last one.
>
> A compositor *may* try to predict where the window is going to be mapped.
> This predict
On Fri, Oct 30, 2015 at 09:55:37PM +0100, Carlos Garnacho wrote:
> Currently, there's no means for the DnD origin to know whether the
> destination is actually finished with the DnD transaction, short of
> finalizing it after the first transfer finishes, or leaking it forever.
>
> But this poses o
On Mon, Nov 02, 2015 at 05:46:35PM +0100, Carlos Garnacho wrote:
> Hey!,
>
> On Sat, Oct 31, 2015 at 12:06 AM, Michael Catanzaro
> wrote:
> > On Fri, 2015-10-30 at 21:55 +0100, Carlos Garnacho wrote:
> >> Changes since v1:
> >> - Renamed events to have a common "dnd" namespace.
> >
> > I don't
Hi Bryce,
On Mon, Nov 2, 2015 at 8:44 PM, Bryce Harrington wrote:
> On Fri, Oct 30, 2015 at 10:04:49PM +0100, Carlos Garnacho wrote:
>> Weston now sends wl_data_source.drop_performed and .drag_finished in
>> order to notify about the different phases of DnD.
>>
>> wl_data_source.cancelled is also
On Fri, Oct 30, 2015 at 10:04:49PM +0100, Carlos Garnacho wrote:
> Weston now sends wl_data_source.drop_performed and .drag_finished in
> order to notify about the different phases of DnD.
>
> wl_data_source.cancelled is also used as mentioned in the docs, being
> emitted also on DnD when the oper
On Fri, Oct 30, 2015 at 7:10 PM, Bill Spitzak wrote:
> I think what is wanted is an indication that the drag really did finish. For
That's data_source.drag_finished in the patch you're commenting.
> instance a file browser acting as the source of a "move" action will want a
> confirmation that t
On Sat, Oct 31, 2015 at 12:22 AM, Michael Catanzaro
wrote:
> On Fri, 2015-10-30 at 22:06 +0100, Carlos Garnacho wrote:
>> --- a/clients/dnd.c
>> +++ b/clients/dnd.c
>> @@ -72,6 +72,7 @@ struct dnd_drag {
>> struct item *item;
>> int x_offset, y_offset;
>> int width, height;
>> +
Hey!,
On Sat, Oct 31, 2015 at 12:06 AM, Michael Catanzaro
wrote:
> On Fri, 2015-10-30 at 21:55 +0100, Carlos Garnacho wrote:
>> Changes since v1:
>> - Renamed events to have a common "dnd" namespace.
>
> I don't think this was a great change. The event occurs on drop, and
> the previous name de
event-gui draws the touch contact as two concentric ellipses that indicate
contact pressure through oppacity.
Signed-off-by: Andreas Pokorny
---
tools/event-debug.c | 29 -
tools/event-gui.c | 38 +-
2 files changed, 61 insertions
This change adds four new properties to touch events:
* major: diameter of the touch ellipse along the major axis
* minor: diameter perpendicular to major axis
* pressure: a pressure value mapped into the range [0, 1]
* orientation: the angle between major and the x axis [0, 360]
Those values are
Hi,
This version of the series deals released or not yet pressed touch contacts in
event-gui. Additionally the code that was supposed to scale diameters on devices
when horizontal and vertical axes have a different resolution was revised.
regards
Andreas
Andreas Pokorny (2):
libinput: add orien
Hi,
> -Original Message-
> From: Daniel Stone [mailto:dan...@fooishbar.org]
> Sent: lundi 2 novembre 2015 12:44
> To: Fabien DESSENNE
> Cc: Bryce Harrington; Giulio Camuffo; Vincent ABRIOU; Benjamin Gaignard;
> wayland-devel@lists.freedesktop.org
> Subject: Re: [PATCH] dmabuf: get supported
Hi,
On 2 November 2015 at 09:39, Fabien DESSENNE wrote:
>> On 30 October 2015 at 00:27, Bryce Harrington
>> wrote:
>> > I'd like to better understand what this is going to be used for,
>> > before landing it. Another R-b on this would be nice as well; Giulio
>> > perhaps you could give this pat
Hi,
> -Original Message-
> From: Daniel Stone [mailto:dan...@fooishbar.org]
> Sent: vendredi 30 octobre 2015 09:31
> To: Bryce Harrington
> Cc: Fabien DESSENNE; Giulio Camuffo; Vincent ABRIOU; Benjamin Gaignard;
> wayland-devel@lists.freedesktop.org
> Subject: Re: [PATCH] dmabuf: get suppo
14 matches
Mail list logo
