Yes/No Screen Keymap: add fallbacks to targets lacking them

With the addition of ignoring unknown actions to the yes/no
screen, several (mostly older) targets won't have keys defined
to cancel out of the yes/no screen.

Adding fallbacks to standard context to correct this.

Targets:
Shanling Q1 - changed, untested (doesn't appear sim has buttons mapped)
Sansa Connect - changed, untested (can't figure out sim keys)

HM60x - changed, untested (sim won't build)
HM801 - changed, untested (sim won't build)
ihifi - changed, untested (sim won't build)
MA - changed, untested (sim won't build)

M3 - changed, tested on sim
X5 - changed, tested on sim
MPIO HD300 - changed, sim tested
MPIO HD200 - changed, sim tested (remote not tested)
Vibe 500 - changed, sim tested

Change-Id: Ib5290ada8e12bb845d3840e481e8533515b42e95

1 files changed, 4 insertions, 1 deletions

diff --git a/apps/keymaps/keymap-mpio-hd300.c b/apps/keymaps/keymap-mpio-hd300.c
index cdb617bed0..7941d1704b 100644
--- a/apps/keymaps/keymap-mpio-hd300.c
+++ b/apps/keymaps/keymap-mpio-hd300.c
@@ -109,8 +109,11 @@ static const struct button_mapping button_context_settings[]  = {
 static const struct button_mapping button_context_yesno[]  = {
     { ACTION_YESNO_ACCEPT,       BUTTON_ENTER,                  BUTTON_NONE },
     { ACTION_YESNO_ACCEPT,       BUTTON_PLAY,                   BUTTON_NONE },
+    { ACTION_STD_CANCEL,         BUTTON_REW,                    BUTTON_NONE },
+    { ACTION_STD_CANCEL,         BUTTON_FF,                    BUTTON_NONE },
+    { ACTION_STD_CANCEL,         BUTTON_REC,                    BUTTON_NONE },
 
-    LAST_ITEM_IN_LIST
+    LAST_ITEM_IN_LIST__NEXTLIST(CONTEXT_STD)
 }; /* button_context_yesno */
 
 static const struct button_mapping button_context_bmark[]  = {