Hi,
> Even more so, because as far as I can see, to actually see the badly sized
> surface
> you have to do this in ivi-layout API:
> 1. add the surface to a layer
> 2. set visibility true
> 3. commit_changes
> 4. set source rectangle
> 5. commit_changes
>
> At step 3, the surface will be shown.
> > ivi-shell/ivi-layout.c | 3 +++
> > 1 file changed, 3 insertions(+)
> >
> > diff --git a/ivi-shell/ivi-layout.c b/ivi-shell/ivi-layout.c index
> > 1601787..ef7ee02 100644
> > --- a/ivi-shell/ivi-layout.c
> > +++ b/ivi-shell/ivi-layout.c
> > @@ -250,6 +250,9 @@ init_surface_properties(struct
> iv
Hi all,
I have a question about one of events from ivi-hmi-controller.xml -
workspace_end_control.
What is the meaning of its argument - "is_controlled" ?
It's not documented anywhere and looking at implementation in hmi-controller.c,
it seems that this is set according to move of layer during
Hi
> On Wed, Apr 8, 2015 at 2:03 AM, Bryce Harrington
> wrote:
> > On Wed, Apr 01, 2015 at 08:10:44AM +0100, mateuszx.potr...@intel.com
> wrote:
> >> From: Mateusz Polrola
> >>
> >> After weston-launch is executing weston it cannot close TTY file,
> >> because it is still required to properly ha