Closed GoogleCodeExporter closed 9 years ago
in fact, its as if the default button configuration is wrong for the experia
play, like this from bottom to top.... b,a,c
really you need megadrive buttons b and c next to each other, like the original
joypad :-)
so for lots of games the buttons that should be next to each other arent.
I would also like to praise you on an EXCELLENT app, im very impressed, and im
a developer too.
Original comment by charliei...@googlemail.com
on 10 Aug 2011 at 11:02
I have the simillar issue on Samsung Galaxy Tab 10.1 with connected Genius
MaxFire G-08XU. The arrow buttons work fine but other doesn't.
To be more specify, my steps are:
1. go to define keys menu
2. touch list item for sega controller button 'c'
3. after first push of any button on controller, the button 'Yes' on screen is
focused.
4. after second push of any button, the button 'Yes' is clicked without setting
the binding
5. device goes 'back one step' and Code of button is set to 0.
I think that problem is that the Genius controller's buttons behave like
'enter' key.
Using version 1.7 and Android 3.1
But anyway really, really, really great app! Thanks!
Original comment by ma...@pasicnyk.com
on 15 Sep 2011 at 1:46
Sorry for the late response on this.
I accept all these bugs and I believe I know the solution. I should hopefully
push a solution out for this. It is unfortunate I can't cause the bug on any
of my devices so I could test in real time.
The problem sometimes is the wrong IME set. For example if you connect a
Wiimote using WiiMote Connect but do not switch to the WiiMote IME it will
cause the problem of setting to 0 when using the Wiimote.
Original comment by shinhals...@gmail.com
on 19 Sep 2011 at 4:03
Accepted and fixed in version 1.8 (hopefully).
Please verify and comments here.
Original comment by shinhals...@gmail.com
on 28 Sep 2011 at 5:04
Yep fixed!!!
I can now configure my buttons on an xperia play.
excellent work my friend.
Original comment by charliei...@googlemail.com
on 11 Oct 2011 at 12:38
Fixed awhile ago!
Original comment by shinhals...@gmail.com
on 24 Feb 2012 at 3:59
Original issue reported on code.google.com by
charliei...@googlemail.com
on 10 Aug 2011 at 10:50