path: root/src/frontend/mame/ui/inputmap.h
diff options
author Vas Crabb <>2019-11-20 03:55:28 +1100
committer Vas Crabb <>2019-11-20 03:55:28 +1100
commite87447e37d80a26df102a85dcc5e46bdafd5571d (patch)
treed307738d5d751442549684f28b7bc6c43c462997 /src/frontend/mame/ui/inputmap.h
parent593b3d9fe1d8fe301b55463f1d7f1d1521f88199 (diff)
UI: when modifying an input mapping, only cycle default/none if UI_CANCEL is the first thing pressed
(nw) It's annoying that if you accidentally start to change an input, there's no way to back out at all. You need to press something before it will do anything. Also, if you go to add an additional "or" combination and press the wrong thing, you can't back out just the change - hitting UI_CANCEL takes you back to the default. This at least partially addresses it: if you hit UI_SELECT to modify an input then hit UI_CANCEL immediately, it will cycle default/none; however if you press any other input first and then hit UI_CANCEL, it will just back out the change. The implementation is a bit whacky at the moment, but doing better would require another emu.h change which I don't want to do right now.
Diffstat (limited to 'src/frontend/mame/ui/inputmap.h')
1 files changed, 1 insertions, 0 deletions
diff --git a/src/frontend/mame/ui/inputmap.h b/src/frontend/mame/ui/inputmap.h
index 4c6064f037b..bd96bbe7edc 100644
--- a/src/frontend/mame/ui/inputmap.h
+++ b/src/frontend/mame/ui/inputmap.h
@@ -70,6 +70,7 @@ private:
input_item_data * lastitem;
bool record_next;
input_seq starting_seq;
+ input_seq init_poll_seq;
virtual void custom_render(void *selectedref, float top, float bottom, float x1, float y1, float x2, float y2) override;
virtual void handle() override;