Open inactive123 opened 5 years ago
For OSX - I ran XCode with threading error debugging turned on and it returned this info, hope this can be of use -
(Android) Hardware back button: does nothing. Should invoke going back (B button etc).
This one's a can't fix.
Many (most?) Android gamepads map the select button to back
. If we assign any other functionality to back
, we basically disable proper gamepad support on Android. (This is a crippling shortcoming on most stand-alone emulators - PPSSPP, DraStic, ReDream, etc. RetroArch really leads the pack in this regard)
MaterialUI will be getting an enhanced navigation bar (with a back button), so we probably don't need to worry about this anyway :)
Threaded video: Doesn't show FPS, just reads N/A - it only shows FPS when we are running a hardware accelerated core, not a software core or no core loaded (menu).
I'm pretty sure HW cores disable threaded video or did at some point.
(Android) Hardware back button: does nothing. Should invoke going back (B button etc).
This one's a can't fix.
Many (most?) Android gamepads map the select button to
back
. If we assign any other functionality toback
, we basically disable proper gamepad support on Android. (This is a crippling shortcoming on most stand-alone emulators - PPSSPP, DraStic, ReDream, etc. RetroArch really leads the pack in this regard)MaterialUI will be getting an enhanced navigation bar (with a back button), so we probably don't need to worry about this anyway :)
Well actually you could do something when a gamepad is not mapped I had that working in some capacity at some point but it was never fully fleshed out.
I'm pretty sure HW cores disable threaded video or did at some point.
This issue has been fixed now though, and has been in 1.7.8 v4 I believe.
Android:Help ->Show Controls: shows just a white dialog screen, text doesn't show.
Android/Vulkan): When we change orientation inside the menu (landscape to portrait or vice versa, doesn't matter) - screen gets stretched out across the screen and touch no longer works properly until you change the orientation back to the orientation the app was started with.
Cosmetic issues
Android
Misc
User Interface/Experience
Threading bugs/errors
Menu input bugs
Usability/UI
Memory issues