summaryrefslogtreecommitdiff
path: root/Source/Core/VideoBackends/OGL/ProgramShaderCache.cpp
diff options
context:
space:
mode:
authormahdihijazi <mahdi.hijaz@hotmail.com>2017-12-25 01:05:37 +0100
committermahdihijazi <mahdi.hijaz@hotmail.com>2017-12-28 23:50:25 +0100
commit136e835fb489f2b0412c760739dd5c668055fb56 (patch)
tree239248b53e83dfddd82ef592c74f60d8e404104c /Source/Core/VideoBackends/OGL/ProgramShaderCache.cpp
parent82a6701f795a883d80c3b0167b4d3f3e224a5cd8 (diff)
[Android] Support restore emulator state after the emulation screen is killed
1) Most of the times the native heap is kept around even after the activity is killed, we can ask the native code if it is still running and resume the emulation if that is the case. 2) In case the native heap is freed and the emulation can't resume we used a temporary state to load on the game boot. I couldn't find a way to test this, if you want to test this schnario, add this block to EmulationFragment. public void onDestroy() { stopEmulation(); super.onDestroy(); } onDestroy is only called if the acivity killed by the OS and not be rotation change whihch in this case will make sure to kill the emulation and start again when the activiy is re-created.
Diffstat (limited to 'Source/Core/VideoBackends/OGL/ProgramShaderCache.cpp')
0 files changed, 0 insertions, 0 deletions