On Sep 8, 2016, at 12:42 PM, Bryce Harrington wrote:
>
> From: Bryce Harrington
>
> These should all be pretty straightforward; there are no behavioral
> changes.
>
> Signed-off-by: Bryce Harrington
Reviewed-by: Yong Bakos
yong
> ---
> unstable/input-method/input-method-unstable-v1.xml |
When a client has registered idle inhibition on a surface, don't trigger
the fade-out animation on the output(s) the surface is displayed on.
But when the surface is destroyed or the inhibitor itself is destroyed
by client request, re-queue the fade out animation.
Signed-off-by: Bryce Harrington
This API allows clients to create an idle manager that can be used to
create per-surface inhibitor objects. These direct the compositor to
not idle off the output that the surface is displayed on (i.e. don't
blank the surface's screen or show a screensaver). When the inhibitor
object is destroyed
Derive client from simple-shm and hook up the API defined in
wayland-protocols to allow client screensaver inhibition requests.
Signed-off-by: Bryce Harrington
---
.gitignore| 1 +
Makefile.am | 14 +-
clients/simple-idle.c | 573 +
Adds a helper routine weston_output_inhibited_outputs() which returns a
mask of outputs that should inhibit screen idling.
Use this routine to check for inhibiting outputs for handling of idle
behaviors in core: In sleep mode, only halt repainting outputs that
don't have valid inhibits. Don't se
Listen for the drop_idle_inhibitor signal from libweston, and propagate
the call to a corresponding libweston-desktop API.
Shells aren't required to implement handling for destruction of the idle
inhibitor, if they have no additional behaviors (e.g. fade-out
animations) beyond letting the output b
Updated to include review feedback from Quentin on the v5. That
involves refinements to the destructor behavior, reorganizing patches a
bit, and noting that if the idle manager is destroyed by the client, the
individual inhibitor objects remain active. The libweston-desktop API
is renamed from su
Instead of creating a single global fade surface across all outputs,
create a separate surface for each output. This will permit
e.g. individual fades for each output (or blocking the fade-outs if
inhibiting idling as will come in a later patch.)
This also fixes a potential issue if on multihead
From: Bryce Harrington
These should all be pretty straightforward; there are no behavioral
changes.
Signed-off-by: Bryce Harrington
---
unstable/input-method/input-method-unstable-v1.xml | 16
1 file changed, 8 insertions(+), 8 deletions(-)
diff --git a/unstable/input-method/
Hi,
I'm aware that loading external back-ends was removed from Weston some time this
year (in June) but I'd like to ask for reconsidering this decision. I guess
this was driven by the intent to support only back-ends hosted within Weston
tree (easier to maintain) and to encourage openness.
On t
On 08/09/2016 16:45, Krzysztof Konopko wrote:
This commit adds ability to load external back-end implementations which is
required if they are not (and can not be) maintained within 'weston' tree.
libweston-backend is introduced to provide common back-end functionality to
external implementation
This commit adds ability to load external back-end implementations which is
required if they are not (and can not be) maintained within 'weston' tree.
libweston-backend is introduced to provide common back-end functionality to
external implementations. Also few required functions are exported as
On 1 September 2016 at 17:49, Derek Foreman wrote:
> On 01/09/16 04:13 AM, Pekka Paalanen wrote:
>> On Wed, 31 Aug 2016 23:17:09 +0100
>> Emil Velikov wrote:
>>
>>> On 31 August 2016 at 19:10, Derek Foreman wrote:
Thanks for taking a look!
On 31/08/16 04:22 AM, Emil Velikov wrote:
On Tue, 16 Aug 2016 10:46:13 +0900
Michel Dänzer wrote:
> On 16/08/16 10:32 AM, Mario Kleiner wrote:
> > Cc'ing Daniel Stone and Pekka Paalanen, because this relates to wayland.
> >
> > Wrt. having a new pageflip parameter struct, i wonder if it wouldn't
> > make sense to then already prepare so
Hi,
On 08-09-16 07:43, Peter Hutterer wrote:
On Wed, Sep 07, 2016 at 10:22:22AM +1000, Peter Hutterer wrote:
Some trackpoints, notably the one on the Lenovo T460s have a tendency to send
the odd event even when they're not actually used. Trackpoint events trigger
palm detection (see 0210f1fee19
15 matches
Mail list logo