webdesignpaster.blogg.se - Game frontend android kodi

#Game frontend android kodi android#

The second might not make much sense but I could see people doing it anyway, and the third would make sense to any activity that could be started with a number of parameters.

the activity looks at the "extras" bundle in the intent and looks for a pair of values who's key is "ROM" or "FILE" or whatever and the matching value would be the location of the ROM path.

as above but all kinds of additional settings parameters are lumped in, perhaps the author uses a system something approximating a query string.

the activity looks at the "data" from the intent that created it, which it expets to be the location of a ROM file to load.

#Game frontend android kodi android#

In Android all kinds of things could happen. With computer based emulators there's the standard accepted practice that you start the emulator and pass the rom name as a command line argument. The trouble is even if some emulators support it, there's no standard way. Or the 'main' activity calls the file browser with startActivityForResult(), and the file browser sends the file name back to the main activity when it finishes.

The file browser activity calls startActivity() and passes the filename as data Well I may have a look at that emulator as time goes on - it's not high on my list of priorities though. However, I am not aware of anything like this.īest I can suggest is RetroArch which is a multi-system emulator. Of course, I'm not sure if other emulators would work like this (although I'd hazard a guess that many will have separate activities for the actual emulator and the menu), and I'm not overly sure how one would go about making use of this, code-wise, but it should certainly be possible. It should, theoretically, be possible to directly launch that specific activity from another app, and pass it as ROM as a parameter.

And so the shortcut would also launch the emulator activity directly with a particular ROM as the parameter. So the ROM loading menu would then load the emulator activity with the particular ROM as some sort of parameter. I'm not completely sure how it worked, but Android apps tend to work on the basis of "activities", and the actual "emulator" part would be one activity, whereas the ROM loading menu would be a separate activity. Click to expand.I have only tried one emulator (GBCoid), but it definitely did have some way to do it, as it allowed you to create a shortcut on the home screen to directly load one specific ROM.