There is a return from ui_process_keypad without a clean ui_mode switch. I've seen that this happen in the special case when the touch_y > 48 * 4: probably the original intention was to switch from UI_KEYPAD to UI_NUMERIC whenever the user touch the numeric area. (the bottom part of the screen).
For the moment I commented out the part of the code causing the problem.
There is a return from ui_process_keypad without a clean ui_mode switch. I've seen that this happen in the special case when the touch_y > 48 * 4: probably the original intention was to switch from UI_KEYPAD to UI_NUMERIC whenever the user touch the numeric area. (the bottom part of the screen).
For the moment I commented out the part of the code causing the problem.