diff options
| author |   Scott Murray <scott.murray@konsulko.com> | 2020-07-22 22:27:21 -0400 |
|---|---|---|
| committer | Scott Murray <scott.murray@konsulko.com> | 2020-07-22 22:39:25 -0400 |
| commit | a37400d73417dc02511813833b8f4d9b91e40a11 (patch) | |
| tree | a5ee5964d970fba4c377bd4d697be91dc43d8133 /test | |
| parent | bdcd052f995d46abeeeda3171759aabad7dd8a75 (diff) | |
Add workaround for top panel button highlightingkoi_10.91.0koi/10.91.0jellyfish_9.99.4jellyfish_9.99.3jellyfish_9.99.2jellyfish/9.99.4jellyfish/9.99.3jellyfish/9.99.29.99.49.99.39.99.210.91.0
The switch to the new compositor removed the callback to update the
top panel button highlight since it was being driven by the
Event_ScreenUpdated event from the old windowmanager. For now, work
around this by driving the ApplicationLauncher's setCurrent method
from the appropriate place in the HomescreenHandler object's
tapShortcut method. If a generic mechanism for notifications on
application expose becomes available via agl-shell-desktop, that
should be used instead.
Additionally, add an explicit call to setCurrent on initialization to
highlight the top panel Launcher button, matching the actual initial
UI state.
Bug-AGL: SPEC-3510
Signed-off-by: Scott Murray <scott.murray@konsulko.com>
Change-Id: Ied5dd8e78195d061585510e60a758559ca4f69b3
Diffstat (limited to 'test')
0 files changed, 0 insertions, 0 deletions