Can I at least get an explanation as to why that is the desired behavior?
Are there any links to a discussion upstream?
As I tried to explain, the essential problem is that "gvba" doesn't save the
game batteries when it should:
if "gvba" doesn't exit cleanly, or you reset the game
within the emulator, the battery file is never created
or updated properly.
I find this to be a usability problem, with potential for data loss.
Think about a word processor analogy, I expect my document to be saved
at the instant I click the button that says "save", not when I close the
entire office application.
--
"gvba" does not write the battery file until the game is closed
https://bugs.launchpad.net/bugs/396792
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
--
universe-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/universe-bugs
