Hi Han,
In ivi-shell architecture, there are controller plugins which controls the
layout of surfaces on the display. The controller plugins are using
ivi_layout_interface to do that.
In weston repository, we have hmi-controller plugin which is good for demo
purposes. But it is not suitable for
On Wed, 3 Jan 2018 13:23:49 + "Han, Guowei"
said:
> We are running a multi process application. And GUI is act as a transparent
> top layer. All other process rendering by them self underneath. So its
> important for other process to place the window at right potion.
Then you want to probabl
On 2017-12-28 01:53 PM, Daniel Stone wrote:
From: Derek Foreman
Using the singleton zombie object doesn't allow us to posthumously retain
object interface information, which makes it difficult to properly inter
future events destined for the recently deceased proxy.
Notably, this makes it impo
On 2017-12-28 01:53 PM, Daniel Stone wrote:
Closures created to hold events which will be dispatched on the client,
take a reference to the proxy for the object the event was sent to, as
well as the proxies for all objects referenced in that event.
These references are dropped immediately before
On 2017-12-28 01:53 PM, Daniel Stone wrote:
Commit e273c7cde added a refcount to wl_proxy. The refcount is set to 1
on creation, decreased when the client explicitly destroys the proxy,
and is increased and decreased every time an event referencing that
proxy is queued.
Assuming no bugs, this me
Hi Daniel,
I think drm_pending_state_apply_atomic (or its callers) leak
pending_state:
On Wed, 2017-12-20 at 12:26 +, Daniel Stone wrote:
> +static int
> +drm_pending_state_apply_atomic(struct drm_pending_state *pending_state,
> +enum drm_state_apply_mode mode)
> +
On Wed, 2017-12-20 at 12:26 +, Daniel Stone wrote:
> @@ -2424,9 +2453,16 @@ drm_pending_state_apply_atomic(struct
> drm_pending_state *pending_state,
> case DRM_STATE_APPLY_ASYNC:
> flags |= DRM_MODE_PAGE_FLIP_EVENT | DRM_MODE_ATOMIC_NONBLOCK;
> break;
> +
Thanks for all the help. Will start look into ivi-shell.
From: magc...@gmail.com [mailto:magc...@gmail.com] On Behalf Of Jasper St.
Pierre
Sent: Wednesday, January 03, 2018 12:28 PM
To: Han, Guowei ; wayland
Subject: Re: Window positioning
(Please Reply All in the future so that responses go t
(Please Reply All in the future so that responses go to the mailing list)
Hi Han,
In that case, you should probably use a protocol designed for embedded
surface layout, like ivi-shell, rather than xdg-shell. Embedded,
static-size display is a very different use case than a modern desktop
system w
Hi Han,
Allowing yourselves to place multiple windows where you want it then isn't
going to solve that problem, since users can still drag them around,
minimize them, etc. Multiprocess rendering is a bit tricksy, and there's no
standardized way to do it right now. The traditional technique is to b
it has only developermode option parameter.
The parameter is only used in init_ivi_shell.
Therefore, we can basically remove the struct,
and check the option locally in the function.
Signed-off-by: Emre Ucan
---
ivi-shell/ivi-shell.c | 42 --
1 file change
controller modules can be loaded as weston modules
from the main function of weston.
Signed-off-by: Emre Ucan
---
ivi-shell/ivi-layout.c | 40
ivi-shell/ivi-shell.c | 28
2 files changed, 4 insertions(+), 64 deletions(-)
dif
weston loads hmi-controller as a weston module.
IVI-shell does not need to load it explicitly.
Signed-off-by: Emre Ucan
---
ivi-shell/hmi-controller.c | 33 ++---
ivi-shell/weston.ini.in| 2 +-
2 files changed, 15 insertions(+), 20 deletions(-)
diff --git a/ivi-
Main motivation of these patches is to be able to load controller modules
from the main function of weston as any other weston module.
The controller modules require ivi_layout_interface to interact
with ivi-shell. Therefore, the API has to be registered to
weston plugin registry.
I made also some
controller modules can be loaded from the main function of weston.
They will get the ivi_layout_interface via weston plugin registry.
Signed-off-by: Emre Ucan
---
ivi-shell/ivi-layout-export.h | 13 +
ivi-shell/ivi-layout.c| 6 ++
ivi-shell/ivi-shell.c | 2 --
3
Signed-off-by: Emre Ucan
---
tests/ivi_layout-internal-test.c | 21 -
tests/ivi_layout-test-plugin.c | 20 +++-
2 files changed, 15 insertions(+), 26 deletions(-)
diff --git a/tests/ivi_layout-internal-test.c b/tests/ivi_layout-internal-test.c
index 4d73eff.
Put the interface into hmi_controller struct.
It is better to have it in an object.
Signed-off-by: Emre Ucan
---
ivi-shell/hmi-controller.c | 194 +++--
1 file changed, 100 insertions(+), 94 deletions(-)
diff --git a/ivi-shell/hmi-controller.c b/ivi-shell
Am 03.01.2018 um 14:23 schrieb Han, Guowei:
> We are running a multi process application. And GUI is act as a
> transparent top layer. All other process rendering by them self
> underneath. So its important for other process to place the window at
> right potion.
[Even that issue appears offtopic
We are running a multi process application. And GUI is act as a transparent top
layer. All other process rendering by them self underneath. So its important
for other process to place the window at right potion.
Sent from my iPhone
On Jan 3, 2018, at 2:58 AM, Kai-Uwe mailto:ku.b-l...@gmx.de>>
On Tuesday, 2 January 2018 23:37:08 -02 Han, Guowei wrote:
> Thanks Jasper. Do u know if there's a demo i can learn from? Currently i am
> creating a bigger surface bigger than screen size. and make subsurface so i
> can posion them as i want. Really don't think its a good way to do it.
It isn't.
20 matches
Mail list logo
