Re: [PATCH v2 libinput] touchpad: drop motion hysteresis by default

Hi, On 02-02-16 01:16, Peter Hutterer wrote: Some older touchpad devices jitter a fair bit when a finger is resting on the touchpad. That's why the hysteresis was introduced in the synaptics driver back in 2011. However, the default value of the hysteresis in the synaptics driver ended up being

Re: [PATCH wayland-protocols v2] xdg-shell: Introduce xdg_tooltip

The existing surface. Perhaps this "get_" naming is a bit confusing, and should be renamed to "create_tooltip" or "make_tooltip" or similar. The intended client flow is: toplevel_wl_surface = wl_compositor.create_surface() toplevel_xdg_surface = xdg_shell.get_xdg_surface(toplevel_wl_surface)

Re: [PATCH wayland-protocols v2] xdg-shell: Introduce xdg_tooltip

On Wed, Feb 03, 2016 at 11:02:14AM +0200, Giulio Camuffo wrote: > 2016-02-03 11:00 GMT+02:00 Jasper St. Pierre : > > No? The parent is the surface the tooltip is laid on top of. > > So where do the contents of the tooltip come from? The tooltip is created from an

[PATCH wayland-protocols v2] xdg-shell: Turn xdg_surface into a generic base interface

Split out toplevel window like requests and events into a new interface called xdg_toplevel, and turn xdg_surface into a generic base interface which others extends. xdg_popup is changed to extend the xdg_surface. The configure event in xdg_surface was split up making xdg_surface.configure an

[PATCH wayland-protocols v2] xdg-shell: Introduce xdg_tooltip

An xdg_tooltip is a new window type used to implement tooltip like surfaces. See the interface documentation for details. Signed-off-by: Jonas Ådahl --- Changes since v1: Various wording changes as suggested by Mike. Added missing version attribute and .

Re: [PATCH wayland-protocols v2] xdg-shell: Introduce xdg_tooltip

2016-02-03 11:00 GMT+02:00 Jasper St. Pierre : > No? The parent is the surface the tooltip is laid on top of. So where do the contents of the tooltip come from? > > On Wed, Feb 3, 2016 at 12:59 AM, Giulio Camuffo > wrote: >> 2016-02-03 10:39

Re: Recursive dispatch (Re: [PATCH v2] server: Calculate remaining data size after a closure is processed)

On Wed, Feb 03, 2016 at 11:14:54AM +0200, Pekka Paalanen wrote: > On Wed, 3 Feb 2016 09:56:20 +0900 > "Jaeyoon Jung" wrote: > > > > -Original Message- > > > From: Derek Foreman [mailto:der...@osg.samsung.com] > > > Sent: Wednesday, February 03, 2016 6:56 AM > > >

Re: [PATCH wayland-protocols v2] xdg-shell: Introduce xdg_tooltip

2016-02-03 10:39 GMT+02:00 Jonas Ådahl : > An xdg_tooltip is a new window type used to implement tooltip like > surfaces. See the interface documentation for details. > > Signed-off-by: Jonas Ådahl > --- > > Changes since v1: > > Various wording changes as

Re: [PATCH wayland-protocols v2] xdg-shell: Introduce xdg_tooltip

No? The parent is the surface the tooltip is laid on top of. On Wed, Feb 3, 2016 at 12:59 AM, Giulio Camuffo wrote: > 2016-02-03 10:39 GMT+02:00 Jonas Ådahl : >> An xdg_tooltip is a new window type used to implement tooltip like >> surfaces. See the

Re: Recursive dispatch (Re: [PATCH v2] server: Calculate remaining data size after a closure is processed)

On Wed, 3 Feb 2016 09:56:20 +0900 "Jaeyoon Jung" wrote: > > -Original Message- > > From: Derek Foreman [mailto:der...@osg.samsung.com] > > Sent: Wednesday, February 03, 2016 6:56 AM > > To: Pekka Paalanen; Jaeyoon Jung > > Cc: 'Jonas Ådahl';

Re: Recursive dispatch (Re: [PATCH v2] server: Calculate remaining data size after a closure is processed)

On 3 February 2016 at 09:34, Jonas Ådahl wrote: > On Wed, Feb 03, 2016 at 11:14:54AM +0200, Pekka Paalanen wrote: >> On Wed, 3 Feb 2016 09:56:20 +0900 >> "Jaeyoon Jung" wrote: >> >> > > -Original Message- >> > > From: Derek Foreman

Re: Recursive dispatch (Re: [PATCH v2] server: Calculate remaining data size after a closure is processed)

On Wed, 3 Feb 2016 10:52:07 + Auke Booij wrote: > On 3 February 2016 at 09:34, Jonas Ådahl wrote: > > On Wed, Feb 03, 2016 at 11:14:54AM +0200, Pekka Paalanen wrote: > >> On Wed, 3 Feb 2016 09:56:20 +0900 > >> "Jaeyoon Jung" wrote:

[PATCH wayland-protocols] Add notification area protocol version 1

From: Quentin Glidic Signed-off-by: Quentin Glidic --- I hope the descriptions in the protocol are clear enough. I have working compositor implementations for Weston (as a plugin), Orbment (plugin) and Sway, and a working client

Re: Moving bugs to Phabricator

Hi, On 2 February 2016 at 20:28, Bill Spitzak wrote: > Can you make a clone of the current Bugzilla state in Phabricator so that we > can see what it looks like? Good idea! Here they are: https://phabricator.freedesktop.org/project/board/100/

Re: [PATCH weston] ivi-layout: apply opacity to weston_view correctly

On Sat, 26 Dec 2015 23:52:51 +0900 Nobuhiko Tanibata wrote: > From: Nobuhiko Tanibata > > update_opacity is only called when a ivi-surface is visible. But the > previous code also checks event masks redundantly. However if

Re: [PATCH] xwayland: Only request cursor frame events if the surface is visible

On Tue, 2 Feb 2016 21:06:33 +0100 Rui Matos wrote: > If the wayland compositor hides our cursor surface (e.g. because the > pointer moved over a different wayland client) before our last > submitted buffer gets a chance to be displayed, no frame event will be > sent and

Re: [PATCH wayland-protocols v2] xdg-shell: Introduce xdg_tooltip

2016-02-03 11:07 GMT+02:00 Jonas Ådahl : > On Wed, Feb 03, 2016 at 11:02:14AM +0200, Giulio Camuffo wrote: >> 2016-02-03 11:00 GMT+02:00 Jasper St. Pierre : >> > No? The parent is the surface the tooltip is laid on top of. >> >> So where do the contents of

[PATCH weston] compositor-x11: send pointer frame after axis event

clients that implement pointer interface of version 5 wait for the frame event, so without it the scrolling does not work (GTK+ clients do not scroll now for example). Xcb axis events are discrete, so it's fine to send frame after every single axis event Signed-off-by: Marek Chalupa

Re: [PATCH wayland-protocols v2] xdg-shell: Introduce xdg_tooltip

On 02/03/16 09:39, Jonas Ådahl wrote: An xdg_tooltip is a new window type used to implement tooltip like surfaces. See the interface documentation for details. Signed-off-by: Jonas Ådahl --- Changes since v1: Various wording changes as suggested by Mike. Added missing

Re: Recursive dispatch (Re: [PATCH v2] server: Calculate remaining data size after a closure is processed)

On Wed, Feb 03, 2016 at 01:37:21PM +0200, Pekka Paalanen wrote: > On Wed, 3 Feb 2016 10:52:07 + > Auke Booij wrote: > > On 3 February 2016 at 09:34, Jonas Ådahl wrote: > > > On Wed, Feb 03, 2016 at 11:14:54AM +0200, Pekka Paalanen wrote: > > >> On Wed, 3

Re: [PATCH wayland-protocols v2] xdg-shell: Introduce xdg_tooltip

On Wed, Feb 3, 2016 at 1:00 PM, Bill Spitzak wrote: > > > On Wed, Feb 3, 2016 at 11:36 AM, Jasper St. Pierre > wrote: >> >> set_parent was moved to xdg_toplevel. Perhaps that's a good idea, >> perhaps it's not. This does mean that a tooltip's parent can

Re: [PATCH libinput] evdev: disable the mode button on the Cyborg RAT 5

On Wed, Feb 03, 2016 at 06:47:01PM +, Joel Duncan wrote: > ​​ > Hi guys, > > Not being a libinput dev I was looking for advice on using this patch. > I noticed that a lot of the RAT config was in /test. After compiling the > driver > and installing it the problem still persists. > > I'm

Re: Moving bugs to Phabricator

On Wed, Feb 03, 2016 at 12:25:26PM +, Daniel Stone wrote: > Hi, > > On 2 February 2016 at 20:28, Bill Spitzak wrote: > > Can you make a clone of the current Bugzilla state in Phabricator so that we > > can see what it looks like? > > Good idea! Here they are: >

[PATCH] xwayland: Clear pending cursor frame callbacks on pointer enter

The last cursor frame we commited before the pointer left one of our surfaces might not have been shown. In that case we'll have a cursor surface frame callback pending which we need to clear so that we can continue submitting new cursor frames. Signed-off-by: Rui Matos ---

Re: [PATCH libinput] evdev: disable the mode button on the Cyborg RAT 5

On Wed, Feb 03, 2016 at 10:43:03PM +, Joel Duncan wrote: > Thanks for clearing that up, Can confirm the patch works. > > udev rules were put in /usr/local/lib/udev by make command, moved to > /usr/lib/udev then devadm hwdb --update. > for next time: ./configure --prefix=/usr

[PATCH libinput] touchpad: while a key is held down, don't disable dwt

If a key enables dwt and is held down when the timeout expires, re-issue the timeout. There is a corner case where dwt may not work as expected: 1. key down and held down 2. dwt timer expires, dwt is re-issued 3. touch starts 4. key is released 5. dwt timer expires 6. touch now starts moving the

Re: [PATCH] xwayland: Clear pending cursor frame callbacks on pointer enter

On Wed, Feb 03, 2016 at 05:46:35PM -0800, Bryce Harrington wrote: > On Wed, Feb 03, 2016 at 04:14:09PM +0100, Rui Matos wrote: > > The last cursor frame we commited before the pointer left one of our > > surfaces might not have been shown. In that case we'll have a cursor > > surface frame

Re: Recursive dispatch (Re: [PATCH v2] server: Calculate remaining data size after a closure is processed)

On Wed, Feb 03, 2016 at 01:44:27PM -0800, Bryce Harrington wrote: > On Wed, Feb 03, 2016 at 01:37:21PM +0200, Pekka Paalanen wrote: > > On Wed, 3 Feb 2016 10:52:07 + > > Auke Booij wrote: > > > On 3 February 2016 at 09:34, Jonas Ådahl wrote: > > > > On Wed,

Re: [PATCH] xwayland: Clear pending cursor frame callbacks on pointer enter

On Wed, Feb 03, 2016 at 04:14:09PM +0100, Rui Matos wrote: > The last cursor frame we commited before the pointer left one of our > surfaces might not have been shown. In that case we'll have a cursor > surface frame callback pending which we need to clear so that we can > continue submitting new

Re: [PATCH weston v2] shell: Don't send extra configure events on click

On Thu, Dec 10, 2015 at 01:08:01PM -0600, Derek Foreman wrote: > The click_to_activate handler fires on every mouse click for a surface > so let's be a little quicker to early return if you're clicking on the > surface that already has activation. > > This prevents (among other side effects) the

Re: [PATCH wayland-protocols v2] xdg-shell: Introduce xdg_tooltip

On Wed, Feb 03, 2016 at 07:24:10PM -0800, Bill Spitzak wrote: > On Wed, Feb 3, 2016 at 1:05 PM, Jasper St. Pierre > wrote: > > > On Wed, Feb 3, 2016 at 1:00 PM, Bill Spitzak wrote: > > > > > > > > > On Wed, Feb 3, 2016 at 11:36 AM, Jasper St. Pierre < >

Re: Moving bugs to Phabricator

Hi, It seems that opening any of these links requires a login. A valid use case for bug trackers is something like: * user searches web for issue keywords (eg. "wayland has no ssd!") * results include link to bug * user views bug report Requiring a login will create more hassle and reduce the

Re: Moving bugs to Phabricator

Hi, On 3 February 2016 at 15:56, Mike Blumenkrantz wrote: > It seems that opening any of these links requires a login. A valid use case > for bug trackers is something like: > > * user searches web for issue keywords (eg. "wayland has no ssd!") > * results include link to bug

[PATCH libinput] touchpad: if we have a serio keyboard, override any previous dwt pairing

If a USB keyboard like the YubiKey is found before the internal keyboard, it will be paired with the touchpad when it is seen. The internal keyboard is seen later but ignored because we already have a keyboard paired with the touchpad. This is obviously wrong. For now, give priority to serio

(wayland sever/client) multiple binding to a global resources.

Dear all, I'm still learning of the philosphy of the wayland world. while seeing and writing some codes, I got a question regarding mutiple binding to a global objects. The client should register a event callback for global registry. also the server will announce its global resources. in

Re: [PATCH wayland-protocols v2] xdg-shell: Introduce xdg_tooltip

set_parent was moved to xdg_toplevel. Perhaps that's a good idea, perhaps it's not. This does mean that a tooltip's parent can never change, and a popup's parent can never change. That can help for getting grab semantics right, though it might be an idea if we say that set_parent on a popup /