On Aug 29, 2014 6:25 PM, "Derek Foreman" wrote:
>
> On 29/08/14 06:42 PM, Jason Ekstrand wrote:
> > Derek,
> > I haven't had a chance to look that hard at or play with this patch yet.
> > Hopefully I can look at it before too long. One quick question though:
> > Have you verified that this works
On Sat, 30 Aug 2014 10:33:23 +0800
Hi, Boyan.
I tested this patch with chromium and firefox running on each drm-backend and
x11-backend of weston.
And seems that both chromium and firefox work well.
This patch actually fixes bug 81273 in my environment.
So now:
Tested-by: Ryo Munakata
Thanks.
We shouldn't do WM-y things on an O-R window, including setting input
focus to it.
Fixes: https://bugs.freedesktop.org/show_bug.cgi?id=81273
Signed-off-by: Boyan Ding
---
xwayland/window-manager.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/xwayland/window-manager.c b/xwayland/window-
On 29/08/14 06:42 PM, Jason Ekstrand wrote:
> Derek,
> I haven't had a chance to look that hard at or play with this patch yet.
> Hopefully I can look at it before too long. One quick question though:
> Have you verified that this works with all of the output transforms? I'm
> sorry if this seems
Welcome Matthieu,
On Fri, Aug 29, 2014 at 8:40 AM, Matthieu Gautier wrote:
> Hello All,
>
>
> As usual, a small self introduction...
>
I don't know that it's really "usual" on this list, but meh.
>
> My name is Matthieu Gautier, French developer of 30 years old.
> I'm a developer for years n
Derek,
I haven't had a chance to look that hard at or play with this patch yet.
Hopefully I can look at it before too long. One quick question though:
Have you verified that this works with all of the output transforms? I'm
sorry if this seems premature but a) pixman renderer stuff is hard to get
I should mention I don't have a touch capable screen and am only doing
partial testing with a modified version of libinput. More testing would
be nice. :)
On 29/08/14 01:12 PM, Derek Foreman wrote:
> If a full screen program is fading out and a touch start happens, it
> will result in a NULL poi
If a full screen program is fading out and a touch start happens, it
will result in a NULL pointer dereference when weston_touch_set_focus
tries to derefernce view->surface->resource.
Instead, this patch sets the focus to NULL, which should be the
same as if the program was destroyed during the to
Hello All,
As usual, a small self introduction...
My name is Matthieu Gautier, French developer of 30 years old.
I'm a developer for years now and I've worked on a lot of projects
related to embedded and graphics (video game, scientific visualization
and digital TV). My last job was to work o
Currently if you try to zoom with mod+scrollwheel the pixman
backend will stop rendering anything at all and will continuously
log "pixman renderer does not support zoom", giving the impression
that the server is hung.
Instead, this patch adds the missing zoom functionality.
This should close BUG
Under some certain circumstances, pointer button may have been released
when frame is still being resized/moved. When this happens, the picked
seat is NULL and it will segfault when moving/resizing surfaces. Check
whether the seat is NULL and ignore move/resize in that case.
Fixes: https://bugs.fr
Hi,
On 08/29/2014 02:04 AM, Peter Hutterer wrote:
> On Thu, Aug 28, 2014 at 03:07:26PM +0200, Hans de Goede wrote:
>> Hi,
>>
>> On 08/27/2014 06:31 AM, Peter Hutterer wrote:
>>> The big change here is the requirement to have the translation component in
>>> a
>>> device-normalized coordinate spac
Hi,
On 08/29/2014 01:51 AM, Peter Hutterer wrote:
> On Thu, Aug 28, 2014 at 03:04:30PM +0200, Hans de Goede wrote:
>> Hi,
>>
>> On 08/27/2014 06:31 AM, Peter Hutterer wrote:
>>> Signed-off-by: Peter Hutterer
>>> ---
>>> src/libinput-util.h | 100
>>> +
Hi,
On 08/29/2014 01:50 AM, Peter Hutterer wrote:
> On Thu, Aug 28, 2014 at 03:02:33PM +0200, Hans de Goede wrote:
>> Hi,
>>
>> On 08/27/2014 06:31 AM, Peter Hutterer wrote:
>>> We apply calibration to single-touch and absolute devices, but we might as
>>> well do so for multitouch events.
>>>
>>>
This patch is now obsolete, see
http://lists.freedesktop.org/archives/wayland-devel/2014-August/016966.html
On 28 August 2014 12:20, Marek Chalupa wrote:
> Hmm, thinking about that... Maybe this is not the right solution.
> Programmer should probably do something like:
>
> do {
> ret = wl_dis
This function is used in one test only, but its functionality can be
used in another tests to (create thread and wait until it is sleeping).
We just need to pass the starting function for the thread as an argument.
Signed-off-by: Marek Chalupa
---
tests/display-test.c | 55 ++
If we will try call wl_display_read_events() again,
after we got EAGAIN from previous call, we get deadlock
as shown in test. The bug works like this: after first call
to wl_display_read_events() the display->reader_count is 0
and next call will decrease it to -1 so the thread will make
sleeping it
When wl_display_read_events() returns with errno == EAGAIN, we
naturally try to call it again. But this next call results in deadlock.
Signed-off-by: Marek Chalupa
---
tests/display-test.c | 88
1 file changed, 88 insertions(+)
diff --git a/t
This helper function wraps the always-repeated pattern:
display->read_serial++;
pthread_cond_broadcast(&display->reader_cond);
Signed-off-by: Marek Chalupa
---
src/wayland-client.c | 37 +
1 file changed, 25 insertions(+), 12 deletions(-)
diff --git a/sr
Hi,
I discovered another bug in wl_display_read_events(). In this series
I'm adding a test and fix for it. Hopefully, these are the last patches
regarding threading from me atm (except for the promised documentation).
/* cosmetic changes and code reuse */
[PATCH 1/4] client: add display_wakeu
20 matches
Mail list logo
