opengress / slimgress Goto Github PK

Problem:
Activities in Android aren't guaranteed to remain alive when they're not being used. Slimgress switches to an OPS activity to show inventory (etc) and it switches to a PORTAL activity to show portal information. In some cases, the Scanner activity can be killed when the user is in OPS/PORTAL, which will result in a crash, loss of sync, or undefined behaviour.
I think that you can test it by turning on "do not keep background activities" in Developer Tools.

Proposed solution 1:
Convert OPS, PORTAL and any future game child-screens to dialogs, make the game run in a single activity. Doing this would remove the hassle of inter-activity communication, and allow the map to be drawn in DEPLOY/RECHARGE screens, which would be handy. It could also solve the problem of remote portal viewing.
Not sure about downsides of this method. Memory use, etc? Also, potentially a lot of work once remote viewing/recharging becomes possible. Then again, remote viewing/recharging are in the future at the moment so maybe not really relevant to analysis of this solution.

Proposed solution 2:
Do nothing. The problem will generally go unnoticed, and this client is intended for PoC/development, so making it run perfectly in all situations is out of scope

In any event, I'm aware of this potential problem and making a note of it here for later.