On Wed, 16 Mar 2016 18:41:12 -0700
Bryce Harrington wrote:
> On Thu, Mar 17, 2016 at 07:21:57AM +0800, comic fans wrote:
> > I've created a bug here https://bugs.freedesktop.org/show_bug.cgi?id=94562
> >
> >
> > >From 5cbdcc9e099d8da4e5a27aa9049029d98dbaf32c Mon Sep 17 00:00:00 2001
> > Fro
On Thu, 17 Mar 2016 15:30:46 +
"Ucan, Emre (ADITG/SW1)" wrote:
> It is an internal API, which returns ivi_layout_screen
> for a pregiven weston_output.
>
> Signed-off-by: Emre Ucan
> ---
> ivi-shell/ivi-layout.c | 20 +---
> 1 file changed, 17 insertions(+), 3 deletions(-
Signed-off-by: Emre Ucan
---
ivi-shell/ivi-layout.c | 19 +++
1 file changed, 3 insertions(+), 16 deletions(-)
diff --git a/ivi-shell/ivi-layout.c b/ivi-shell/ivi-layout.c
index f9135eb..2782346 100644
--- a/ivi-shell/ivi-layout.c
+++ b/ivi-shell/ivi-layout.c
@@ -1895,10 +1895,
Hi Pekka,
> -Original Message-
> From: Pekka Paalanen [mailto:ppaala...@gmail.com]
> Sent: Freitag, 18. März 2016 12:24
> To: Ucan, Emre (ADITG/SW1); wataru_natsume
> Cc: wayland-devel@lists.freedesktop.org; Friedrich, Eugen (ADITG/SW1)
> Subject: Re: [PATCH weston 0/8] IVI Screen refactor
On Sun, 13 Mar 2016 18:22:18 +0100
Armin Krezović wrote:
> Hello Pekka, Quentin and Kat (sorry, don't know the real name yet).
>
> Pekka and Quentin have volounteered to review my GSoC application
> draft for the Wayland project. Pekka also suggested to add Kat to
> the list of reviewers.
>
> A
Switches from inline to pre-processor definitions in order to utilize
__FILE__ and __LINE__ from the .c file in order to display the location
of memory allocation failures when failing.
Now xmalloc, et al calls will produce:
[weston-info] clients/weston-info.c:714: out of memory (1024)
Signe
On Wed, Mar 16, 2016 at 10:57:53AM +0100, Hans de Goede wrote:
> Hi,
>
> On 11-03-16 01:24, Peter Hutterer wrote:
> >The touchpad's sensors are too far apart (or the firmware interferes),
> >causing
> >in a jerky movement visible especially on slow motion. We get a bunch of
> >normal motion event
It is not necessary to check ivi object IDs of
pregiven ivi objects (surface, layer). The controller modules are
responsible to provide valid pointers to ivi objects.
Checking object IDs do not protect us from invalid pointers.
Emre Ucan (5):
ivi-shell: simplify ivi_layout_remove_surface
ivi