Add workaround for top panel button highlighting 49/25049/1 10.91.0 9.99.2 9.99.3 9.99.4 jellyfish/9.99.2 jellyfish/9.99.3 jellyfish/9.99.4 jellyfish_9.99.2 jellyfish_9.99.3 jellyfish_9.99.4 koi/10.91.0 koi_10.91.0
authorScott Murray <scott.murray@konsulko.com>
Thu, 23 Jul 2020 02:27:21 +0000 (22:27 -0400)
committerScott Murray <scott.murray@konsulko.com>
Thu, 23 Jul 2020 02:39:25 +0000 (22:39 -0400)
commita37400d73417dc02511813833b8f4d9b91e40a11
treea5ee5964d970fba4c377bd4d697be91dc43d8133
parentbdcd052f995d46abeeeda3171759aabad7dd8a75
Add workaround for top panel button highlighting

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
homescreen/src/homescreenhandler.cpp
homescreen/src/homescreenhandler.h
homescreen/src/main.cpp