Yep, DISPLAY always needs to be set - and I figured, there's a reason
On Tue, May 26, 2015 at 2:59 AM, Pekka Paalanen ppaala...@gmail.com wrote:
On Tue, 26 May 2015 10:40:15 +0100
Daniel Stone dan...@fooishbar.org wrote:
Hi,
On 26 May 2015 at 10:26, Giulio Camuffo
In some extreme cases with animated cursors at a high frame rate we
could end up filling the wl_display outgoing buffer and end up with
wl_display_flush() failing.
In any case, using the frame callback to throttle ourselves is the
right thing to do.
Signed-off-by: Rui Matos tiagoma...@gmail.com
(Oops, sent too soon by accident.)
Yep, DISPLAY always needs to be set - and I figured, there's a reason it is
that way, so that's actually why I thought it made sense to use the same
convention for WAYLAND_DISPLAY.
Also, regarding Bill's first comment: yeah, that certainly works, but it
feels
On Wed, May 27, 2015 at 10:13:55AM +0300, Pekka Paalanen wrote:
On Tue, 26 May 2015 23:01:49 -0700
Bryce Harrington br...@osg.samsung.com wrote:
Wayland 1.8 RC2 brings one change since RC1, a unit test case to
accompany the new core headers feature.
This core header feature, added
I'm planning on removing this hook and just make compositors deal with
the fallout. Unfortunately, it hasn't been merged yet.
http://patchwork.freedesktop.org/patch/43021/
On Wed, May 27, 2015 at 9:42 AM, Carlos Garnacho carl...@gnome.org wrote:
For these, we must first lookup the DIX sequence
Rui Matos tiagoma...@gmail.com writes:
In some extreme cases with animated cursors at a high frame rate we
could end up filling the wl_display outgoing buffer and end up with
wl_display_flush() failing.
In any case, using the frame callback to throttle ourselves is the
right thing to do.
A DeviceIntPtr with touch valuators is also created in order to deliver
the translated touch events. The lifetime of xwl_touch structs is tied
to the wayland ones, finishing in either wl_touch.up() or wl_touch.cancel()
Signed-off-by: Carlos Garnacho carl...@gnome.org
---
These sequences are forgotten to all purposes.
Signed-off-by: Carlos Garnacho carl...@gnome.org
---
hw/xwayland/xwayland-input.c | 14 ++
hw/xwayland/xwayland.c | 6 +++---
hw/xwayland/xwayland.h | 2 ++
3 files changed, 19 insertions(+), 3 deletions(-)
diff --git
This struct holds information about each individual, ongoing touchpoint.
A list of these is held by the xwl_seat.
Signed-off-by: Carlos Garnacho carl...@gnome.org
---
hw/xwayland/xwayland-input.c | 10 ++
hw/xwayland/xwayland.h | 9 +
2 files changed, 19 insertions(+)
Hey,
Here's some patches to implement/bridge wl_touch in xwayland, sent these
patches some months ago but they went unnoticed and later forgotten. I rebased
on top of master and they still work alright. Not sure if this is a better
timing, but...
Cheers,
Carlos
For these, we must first lookup the DIX sequence from the Sprite, we can
then lookup the DDX ID/xwl_touch from xwayland's touch device.
Signed-off-by: Carlos Garnacho carl...@gnome.org
---
hw/xwayland/xwayland-input.c | 68 +++-
1 file changed, 55
This is the second release candidate for the Weston 1.8 series.
This requires Wayland 1.7.93.
The main change since RC1 is the introduction of a new headless
rendering test framework feature. This allows test cases to run weston
synthetically, and instead of drawing to a physical monitor, to
On Tue, 13 Jan 2015 10:29:06 +0800
Jonas Ådahl jad...@gmail.com wrote:
Noted. It should be semi safe to push as long as it's on libinput
master. Weston master can depend libinput master, can't it, Pekka?
Ahhah, sorry, this question had stuck in my long-time backlog.
I think Weston master can
On Wed, May 27, 2015 at 09:48:50AM +0300, Pekka Paalanen wrote:
On Tue, 26 May 2015 17:06:49 -0700
Bryce Harrington br...@osg.samsung.com wrote:
On Tue, May 26, 2015 at 03:52:59PM +0300, Pekka Paalanen wrote:
On Tue, 26 May 2015 07:24:04 -0500
Derek Foreman der...@osg.samsung.com
On Tue, 26 May 2015 22:23:32 -0700
Bryce Harrington br...@osg.samsung.com wrote:
None of the following stuff looks important enough to block the release,
but looks a little untidy. Would be nice to have this cleaned up for
1.9.
== Weston ==
Pretty clean actually.
* Raspberry Pi stubs
Wayland 1.8 RC2 brings one change since RC1, a unit test case to
accompany the new core headers feature.
This core header feature, added previously this release cycle, is a new
scanner option --include-core-only, which creates new headers
wayland-client-core.h and wayland-server-core.h to avoid
On Tue, 26 May 2015 12:10:07 -0500
Derek Foreman der...@osg.samsung.com wrote:
On 26/05/15 03:30 AM, Pekka Paalanen wrote:
On Mon, 25 May 2015 15:19:38 -0500
Derek Foreman der...@osg.samsung.com wrote:
We no longer have a race with shell startup because we create our own
colored
On Tue, 26 May 2015 17:06:49 -0700
Bryce Harrington br...@osg.samsung.com wrote:
On Tue, May 26, 2015 at 03:52:59PM +0300, Pekka Paalanen wrote:
On Tue, 26 May 2015 07:24:04 -0500
Derek Foreman der...@osg.samsung.com wrote:
On 26/05/15 03:54 AM, Pekka Paalanen wrote:
Now, when there
On Tue, May 26, 2015 at 07:03:30PM -0700, Bryce Harrington wrote:
Signed-off-by: Bryce Harrington br...@osg.samsung.com
looks good, a side-note here: while I was looking up something unrelated I
found that the default suffix for TEST_EXTENSIONS in automake is .test.
That variable enables setting
On Wed, May 27, 2015 at 09:07:14AM +0300, Pekka Paalanen wrote:
On Tue, 13 Jan 2015 10:29:06 +0800
Jonas Ådahl jad...@gmail.com wrote:
Noted. It should be semi safe to push as long as it's on libinput
master. Weston master can depend libinput master, can't it, Pekka?
Ahhah, sorry, this
On Tue, 26 May 2015 23:01:49 -0700
Bryce Harrington br...@osg.samsung.com wrote:
Wayland 1.8 RC2 brings one change since RC1, a unit test case to
accompany the new core headers feature.
This core header feature, added previously this release cycle, is a new
scanner option
On Tue, 26 May 2015 23:59:41 -0700
Bryce Harrington br...@osg.samsung.com wrote:
On Wed, May 27, 2015 at 09:48:50AM +0300, Pekka Paalanen wrote:
One thing worth to note: if Weston is using none background meaning
that we get undefined (garbage) content, then removing a wl_surface may
not
After a spectacular rebase/pull failure combination I accidentally pushed
the tablet-support branch to master. The erroneous commit was 8d7a1c1.
I've done a reset --hard back to the previous HEAD 0c8d761, please ignore
and git pull complains about non-fast-forwards.
Sorry about that.
Cheers,
23 matches
Mail list logo
