You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Let's consider the case, when game consists of multiple screens. If we consider one screen stored in database, we might modify screen, using database objects. But if we switch back from other screen, the screen
will remain modified. That could be solved, is user will reset database from simple snapshot.
However several conditions should be preserved:
Existing objects must not be erased from database, only have their properties reset to a properties from snapshot (so the other components of a game may not re-query game objects from database).
New objects must be erased from database.
Removed objects must be recovered in database.
m_max_id field must be set as we were loading stuff from database.
Methods for loading must save snapshot, each time they were called.
Methods like makeSnapshot, restoreFromSnapshot should be added.
The text was updated successfully, but these errors were encountered:
Let's consider the case, when game consists of multiple screens. If we consider one screen stored in database, we might modify screen, using database objects. But if we switch back from other screen, the screen
will remain modified. That could be solved, is user will reset database from simple snapshot.
However several conditions should be preserved:
The text was updated successfully, but these errors were encountered: