2016-04-22, 22:27
(2016-04-22, 02:35)garbear Wrote:(2016-04-21, 20:01)Montellese Wrote: I've given the latest git a try and I'm still having the problem that when I try to activate a button to be mapped in the controller configuration that the button press is handled twice and the button gets assigned immediately. That makes it impossible to assign any other button to the first button in the list than the button already mapped to the "Select" action.
Not this again a problem on master too?
Seems to work perfeclty fine in current master. I've also run into a lot of other bad behaviour in the retroplayer-17alpha1 branch where the axis inputs are constantly being triggered while the analogue stick is actually perfectly still. It then goes aroudn crazy in the GUI until I press another button (moving the analogue stick doesn't make a difference) at which point it stops going crazy.