On Wed, Jan 31, 2018 at 1:02 AM, Peter Hutterer
wrote:
> On Tue, Jan 30, 2018 at 04:18:26PM +1000, Peter Hutterer wrote:
>> On Wed, Jan 24, 2018 at 10:47:10AM +0100, Johannes Pointner wrote:
>> > On Wed, Jan 24, 2018 at 10:18 AM, Peter Hutterer
>> > wrote:
>> > > On Wed, Jan 24, 2018 at 10:04:52A
On Fri, 26 Jan 2018 18:47:55 +0200
Alexandros Frantzis wrote:
> Properly clean up all sub-objects (e.g., weston_pointer_client objects)
> when a weston_pointer object is destroyed. The clean-up ensures that the
> server is able to safely handle client requests to any associated
> pointer resource
On Fri, 26 Jan 2018 18:47:56 +0200
Alexandros Frantzis wrote:
> Ensure the server can safely handle client requests for wl_keyboard
> resources that have become inert due to a weston_keyboard object
> destruction.
>
> This change involves, among other things, setting the weston_keyboard
> object
On Fri, 26 Jan 2018 18:47:57 +0200
Alexandros Frantzis wrote:
> Ensure the server can safely handle client requests for wl_touch
> resources that have become inert due to a weston_touch object
> destruction.
>
> This change involves, among other things, setting the weston_touch
> object, instead
On Fri, 26 Jan 2018 18:47:58 +0200
Alexandros Frantzis wrote:
> Ensure the server can safely handle client requests for wl_seat resource
> that have become inert due to weston_seat object release and subsequent
> destruction.
>
> The clean-up involves, among other things, unsetting the destroyed
On Wed, Jan 31, 2018 at 03:21:07PM +0200, Pekka Paalanen wrote:
> On Fri, 26 Jan 2018 18:47:58 +0200
> Alexandros Frantzis wrote:
>
> > Ensure the server can safely handle client requests for wl_seat resource
> > that have become inert due to weston_seat object release and subsequent
> > destruct
On Fri, 26 Jan 2018 18:47:59 +0200
Alexandros Frantzis wrote:
> The current test client code waits for all wl_seat globals to arrive
> before checking them and deciding which one is the test seat global to
> use for the input object. This method doesn't support dynamic addition
> of the test seat
On Fri, 26 Jan 2018 18:48:00 +0200
Alexandros Frantzis wrote:
> Support adding a test seat using the weston_test.device_add request.
> This will be used in tests in upcoming commits where we will need to
> re-add the seat after having it removed.
>
> We only support one test seat at the moment,
On Wed, Jan 31, 2018 at 04:25:15PM +0200, Pekka Paalanen wrote:
> On Fri, 26 Jan 2018 18:47:59 +0200
> Alexandros Frantzis wrote:
>
> > The current test client code waits for all wl_seat globals to arrive
> > before checking them and deciding which one is the test seat global to
> > use for the i
Hi Pekka,
On 17 January 2018 at 10:43, Pekka Paalanen wrote:
> I have a recollection of having a rationale that the state_invalid flag
> should stay per-output, but it seems those ideas were just optimization
> that's probably moot anyway. I suppose with atomic, the per-output flag
> would not ma
Having the system suspend or shutdown halfway through a test run is a tad
annoying. So let's talk to logind and tell it to inhibit the various keys
we're testing.
https://bugs.freedesktop.org/show_bug.cgi?id=104720
Signed-off-by: Peter Hutterer
---
meson.build | 7 ++-
test/litest.c | 57
Too easy to trigger with the short button debouncing offsets
Signed-off-by: Peter Hutterer
---
test/litest.c | 8 +++-
1 file changed, 7 insertions(+), 1 deletion(-)
diff --git a/test/litest.c b/test/litest.c
index befb486a..dcbed5c9 100644
--- a/test/litest.c
+++ b/test/litest.c
@@ -691,8
A set of wireless devices that can scramble the timestamps, so we get
press/release within 8ms even though I doubt the user is capable of doing
this. Since they're generally good quality anyway, let's just disable
debouncing on those until someone complains and we need something more
sophisticated.
13 matches
Mail list logo
