summaryrefslogtreecommitdiffstats
path: root/interfaces/windowmanager.xml
AgeCommit message (Collapse)AuthorFilesLines
2017-07-05Revert "Revert "Fix issue of app's unexpected stop while background""Tadao Tanikawa1-0/+1
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>
2017-06-30Revert "Fix issue of app's unexpected stop while background"Jan-Simon Moeller1-1/+0
This reverts commit f95ec0c0142472aeaa1de8994ee4ad860fd3ad54. Breaks visibility. Reverting on dab and master. Please resubmit a fixed version. Tnx. Change-Id: Ic5afcd1034ab7af45b44e45bb8164f1827788afb
2017-06-27Fix issue of app's unexpected stop while backgroundTadao Tanikawa1-0/+1
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>
2017-01-18Initial source commitBocklage, Jens1-0/+208
Taken from https://gerrit.automotivelinux.org/gerrit/p/staging/HomeScreen.git Signed-off-by: Bocklage, Jens <Jens_Bocklage@mentor.com>