On Mon, 6 Jul 2015 11:25:53 -0700
Bill Spitzak wrote:
> On Fri, Jul 3, 2015 at 3:10 AM, Jonas Ådahl wrote:
>
> >
> > > This would work, but it still feels wrong to me. It has the same
> > > priority-inversion as before (the less privileged clients gets to see
> > > the more privileged one). It
On Mon, Jul 06, 2015 at 09:02:40PM +0100, Burton, Ross wrote:
> On 6 July 2015 at 20:40, Bryce Harrington wrote:
>
> > An even cleaner solution would be to break the scanner out as a separate
> > source package from libwayland. Then all this mess can be handled
> > through normal package depende
On 6 July 2015 at 20:40, Bryce Harrington wrote:
> An even cleaner solution would be to break the scanner out as a separate
> source package from libwayland. Then all this mess can be handled
> through normal package dependencies.
>
For such a small tool with a fairly simple solution in cross c
On Wed, Jul 01, 2015 at 10:51:01PM +0100, Ross Burton wrote:
> The previous idiom for building a cross-compiled Wayland is to build once for
> the build host (with --enable-scanner --disable-libraries) to get a
> wayland-scanner binary that can then be used in a cross-compile (with
> --disable-scan
On Fri, Jul 3, 2015 at 3:10 AM, Jonas Ådahl wrote:
>
> > This would work, but it still feels wrong to me. It has the same
> > priority-inversion as before (the less privileged clients gets to see
> > the more privileged one). It also limits what the "open file dialog"
> > client can do. For insta
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
Those values are optionally support
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
Those values are optionally support
This device provides a circular touch point size and and hence lacks
orientation. It will be used to test default value handling.
Signed-off-by: Andreas Pokorny
---
test/Makefile.am | 1 +
test/litest-nexus4-touch-screen.c | 99 +++
test/lite
Adds a device with various touch related axes and respective device features
to litest.
Signed-off-by: Andreas Pokorny
---
test/Makefile.am | 1 +
test/litest-touch-screen.c | 105 +
test/litest.c | 2 +
test/litest.h
Hi,
This updates step 2/5, 3/5 and includes a new version of step 5/5. The former
two did not apply cleanly so I updated those. The latter one should contain
all of the review findings resolved. I switch to zero as the default value,
and removed the automatic 'minor == major if not set' - behavio
On Sun, 21 Jun 2015 21:25:15 +0200
Mario Kleiner wrote:
> If a stopped repaint loop gets restarted due to posting of new
> damage, and this restart of the repaint loop happens late in the
> video refresh cycle, ie. already inside the repaint-window and
> thereby after the composition deadline for
This patchset add support for driving multiple framebuffers from weston. First
patch drops the intermediate shadow buffer in the fbdev compositor, which
turned out to be both unneeded and buggy with non-0x0 rooted outputs second
patch actually adds multiple output support.
Sjoerd Simons (2):
com
On startup enumerate the available framebuffer devices using udev and
setup an output for each device, unless a specific device is passed with
--device in which case just create one for that device.
Signed-off-by: Sjoerd Simons
---
src/compositor-fbdev.c | 80
Currently the fbdev compositor has its own shadow buffer when rendering
with pixman, causing the following copies to occur:
[pixman shadow buffer] -> [fbdev shadow buffer] -> [fbdev hardware]
As the pixman render already does all output translation when
compositing the intermediate shadow buffer
14 matches
Mail list logo
