It behaves the same way that InputMap behaves. There is no Cancel button. Only an Ok button.
You can set the Cancelable parameter to False and then the user will only be able to close it with the Ok button (this is more logical than allowing to close it with the back key as the changes are always applied).
It behaves the same way that InputMap behaves. There is no Cancel button. Only an Ok button.
You can set the Cancelable parameter to False and then the user will only be able to close it with the Ok button (this is more logical than allowing to close it with the back key as the changes are always applied).
I really wanted the option to use back key to cancel. However, that will be an issue. When user selects from the list and cancels, the map GetValueAt will always be at true for the selections that was canceled. I prefer to use InputMulti to store the selections in the list. I wish you can implement the InputMultiAsync in the future.