Quote:
Originally Posted by Tullius
It seems to me that including the "undo" button would require a massive change of code. A reason could be that the game uses an older database management system. Modern systems like ADO.net are so designed that between the orginal database and the "database in the memory" is a layer which is something like a placeholder (i have tried to explain it in a very simple way). So when you change something the original database is not affected until you want it. Then it is no problem to cancel changes. Modern database management systems use already transaction logs and so on so that you have as programmer much more opportunities.
What i have learnt here and by looking through some other threads is that the game uses only a very simple model. You change something and it is immediately saved. Period. It works well but is archaic and limits the options.
Now Markus can not simply use ADO.net because he supports also Macs and Linux. I sure there are solutions which can handle all plattforms but such an undertaken would require a rewrite of a big part of the engine.
|
Seems to me that lineup changes (where most of the UNDO problems occur) should be temporary until you return to the game screen. No UNDO button needed, just make returning to the game screen the DO button.
*shrug*