| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
This updates the gitreview file in the project
.
Change-Id: I30d1e459a9d23fbdece8575ad9e7b51d26677e8d
Signed-off-by: Jan-Simon Möller <jsmoeller@linuxfoundation.org>
|
|
Bug-AGL: SPEC-791
Avoid demo screen being stretched and distorted on non full-HD display.
Instead, we should fit it on target display but also keeping demo screen aspect ratio.
This change has no impact on fiull-HD displays since the behavior is the same.
In addition to "fit" option (now default), "stretch" (previous default) and "no" modes are provided for convenience.
Update:
Add content modes that seems to be common.
Instead of integer value but string ids are used to specify desired mode.
Update2:
Do not rely on copmiler for redundant calls to strcmp
Use signed type to avoid redundant type casting
Update3:
Fixing typo, adding comments, error case handling
Update4: (Tadao Tanikawa)
Calculating the geometry of layer (named root layer) once when
WindowManager initialized and each app's layer inherits it.
Update5: (Tadao Tanikawa)
Clean up compiler warnings
Update6: (Tadao Tanikawa)
Clean up compiler warnings
Change-Id: Ibb797ebea65062fdda7eccc5b7fc246a6b602e98
Signed-off-by: Takashi Matsuzawa <tmatsuzawa@xevo.com>
Signed-off-by: Tadao Tanikawa <tanikawa.tadao@jp.panasonic.com>
|
|
WindowManager uses the pid to manage app's surface
and layer and the pid is from creatorPid of
ivi-surface. It used to be the same value as
afm-util returns when apps launched via HomeScreen.
After new AGL application framework has come,
afm-util no longer returns the same value as
creatorPid.
So commit 4cb274 and bb3369 are introduced, then
WindowManager started to use process group or
session instead of pid which is returned by afm-util.
But inside WindowManager pid which returned by afm-util
is still used to detect ivi surface for app. It is
registered when app is launched via HomeScreen and
it is retrived by app's process group or session
from creatorPid when ivi-surface has been created.
Because this logic of pid conversion was incomplete,
it caused the issue which early launched app has
never been shown even when user try to launch
it via HomeScreen.
This patch introduces quick hack to resolve this
issue and improve the surface management in
WindowManager.
Bug-AGL: SPEC-745
Change-Id: Iafa2e56c07b3c3a2eff23ff75cdedb3226d7f55a
Signed-off-by: Tadao Tanikawa <tanikawa.tadao@jp.panasonic.com>
|
|
This reverts commit c1e525621d49621421f79bc2134a9cb00b4cf2cb.
The commit f95ec0 depends on the change of apps/homescreen.
(https://gerrit.automotivelinux.org/gerrit/#/c/9829/).
Change-Id: Iff48e71a902823e17d032c55ecfc431429151f49
Signed-off-by: Tadao Tanikawa <tanikawa.tadao@jp.panasonic.com>
|
|
This reverts commit f95ec0c0142472aeaa1de8994ee4ad860fd3ad54.
Breaks visibility. Reverting on dab and master.
Please resubmit a fixed version. Tnx.
Change-Id: Ic5afcd1034ab7af45b44e45bb8164f1827788afb
|
|
Current window manager make own ivi-layer to each application
and adjust the order when rendering (screen's render order of
layers).
E.g. When showing apps launcher, window manager has only 1
ivi-layer for homescreen under screen 0. When showing an app,
window manager add 1 ivi-layer for it and set render order
of 2 layers, front: app's and back: homescreen layer.
And when app hides, it's layer is removed from render order.
But if removed from render order, excecuting QML also stopped.
It is caused why the media player doesn't play next song
when it is not shown.
This patch changes how to make render order to keep media
player/navigation's layer in render order even when it is
not shown.
Bug-AGL: SPEC-395
Change-Id: I01f9705a8d2f6c6fbee317b5297ce8f3715a7d39
Signed-off-by: Tadao Tanikawa <tanikawa.tadao@jp.panasonic.com>
|
|
The service run has systemd user unit, so "User=" is useless
Bug-AGL: SPEC-546
Change-Id: Iea3d9b3a26a85cdad55ac2e22115fe361695491c
Signed-off-by: Ronan Le Martret <ronan.lemartret@iot.bzh>
|
|
Recording surfaces even for unknown applications
improves the system by eliminating possible
race conditions and by allowing applications to
be started in background.
AGL-Issue: SPEC-520
Change-Id: I7ee77d0c2fe419fa2dfaa48b1590e7ef4e82f8e6
Signed-off-by: José Bollo <jose.bollo@iot.bzh>
|
|
This is needed to allow the new application framework
to display surfaces. The mechanism is as follows:
if the pid of the creator of a surface isn't registered,
the master of the process group it belongs to is used
instead or else the master of the session group.
Change-Id: I696e2519f919fb671e8a325615609e35a3c7ffe2
Signed-off-by: José Bollo <jose.bollo@iot.bzh>
|
|
The code factorized was present 4 times in the code.
Factorizing it improves the overall.
Change-Id: I94833679fcd366796b332259ebac5ecac5fc047c
Signed-off-by: José Bollo <jose.bollo@iot.bzh>
|
|
* WindowManager must start only when
weston is ready.
[SPEC-470]
Change-Id: I441719acd72f022eb150ebb73047d805fc644dbc
Signed-off-by: Ronan Le Martret <ronan.lemartret@iot.bzh>
|
|
Signed-off-by: Bocklage, Jens <Jens_Bocklage@mentor.com>
|
|
Signed-off-by: Bocklage, Jens <Jens_Bocklage@mentor.com>
|
|
Taken from https://gerrit.automotivelinux.org/gerrit/p/staging/HomeScreen.git
Signed-off-by: Bocklage, Jens <Jens_Bocklage@mentor.com>
|
|
Signed-off-by: Bocklage, Jens <Jens_Bocklage@mentor.com>
|
|
|
Jan-Simon Möller
Takashi Matsuzawa
Tadao Tanikawa
Ronan Le Martret
José Bollo
Bocklage, Jens