resource problems after OnResume

[dellis1972]

http://monogame.codeplex.com/discussions/281277

When - in the android app lifecycle - you hit an onresume after an onstop because another app came forward I am seeing all the textures that were previously loaded being corrupt but any textures loaded from that point are fine.

[KonajuGames]

Sounds similar to device reset issues we used to deal with on Windows prior to DirectX10. We may have to reload textures and other affected assets on resume. This should be trivial for assets loaded through the ContentManager as we have a list of them and their asset names. Assets created by the developer outside of the ContentManager will need to be manually reloaded or recreated by the developer. This is what the GraphicsDevice.DeviceReset event is intended for. ContentManager could attach an event handler to this event so that assets loaded by that ContentManager are automatically reloaded as required. Alternatively, each Texture2D and other affected assets attach their own event handler when they are created so the objects reload themselves.

[dellis1972]

Sly, any chance you could take this issue on? I'm going to be looking at the various Orientation issues we had at the moment and a Texture Rectangle issue as well.

[KonajuGames]

Sure

[zdman2022]

What's the status on this? I'm about to tackle device reset for the FRB engine. I was going to reload everything in our ContentManager. The problem with doing it through the engine is it should be done asynchronously otherwise it will freeze the game.

[dellis1972]

Im not sure anything has been done with this si feel free to investigate :-)
On Jan 17, 2012 3:57 PM, "sdancer" <
reply@reply.github.com>
wrote:

What's the status on this? I'm about to tackle device reset for the FRB
engine. I was going to reload everything in our ContentManager. The
problem with doing it through the engine is it should be done
asynchronously otherwise it will freeze the game.

---

Reply to this email directly or view it on GitHub:
#165 (comment)

[KonajuGames]

Thank you for looking at that. The submitted fix appears to be fine.

[dellis1972]

The fix seems to have fixed the issue, nice work sdancer :)