diff options
author | Tadao Tanikawa <tanikawa.tadao@jp.panasonic.com> | 2017-07-13 03:01:41 +0900 |
---|---|---|
committer | Tadao Tanikawa <tanikawa.tadao@jp.panasonic.com> | 2017-07-13 15:23:29 +0000 |
commit | b28064e1f04eac99995e1462771fb43b7bba8545 (patch) | |
tree | a004b18679d80d3af2b564f5246e739365648a58 /config.tests/ivi_layermanagement_api | |
parent | 7e47c84270b7bd22aab1f6bd20e01e9e8f68f489 (diff) |
Fix the issue early launched apps before HomeScreendab_4.0.0dab_3.99.3dab/4.0.0dab/3.99.34.0.03.99.3
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>
Diffstat (limited to 'config.tests/ivi_layermanagement_api')
0 files changed, 0 insertions, 0 deletions