Opened 10 years ago
Last modified 4 years ago
#6716 new feature request
Implement descriptive error message on save failure
| Reported by: | SF/wishmaster51 | Owned by: | |
|---|---|---|---|
| Priority: | normal | Component: | --Other-- |
| Version: | Keywords: | ||
| Cc: | Game: |
Description
The error messages on game save failures should be more descriptive. I'm running ScummVM on Android and wasn't able to save games because my SD card was full. The error message just reported some game save failure, but it didn't indicate the reason, so I didn't knew why it failed. Moreover, the saved games looked like on the screen (0-4) so the behaviour really looks like a bug.
Ticket imported from: bugs/6716.
Attachments (1)
Change History (7)
by , 10 years ago
| Attachment: | screenshot-20140822-193527.png added |
|---|
comment:1 by , 10 years ago
| Summary: | More descriptive error messages on failures (e.g., save game failure) → ANDROID: Implement descriptive error message on save failure |
|---|
comment:2 by , 10 years ago
comment:3 by , 10 years ago
| Summary: | ANDROID: Implement descriptive error message on save failure → Implement descriptive error message on save failure |
|---|
comment:4 by , 10 years ago
Not an Android-specific bug, Android just uses the DefaultSaveFileManager.
comment:5 by , 6 years ago
| Component: | → --Other-- |
|---|
comment:6 by , 4 years ago
| Type: | defect → enhancement |
|---|
Note:
See TracTickets
for help on using tickets.
There has been a long standing issue to ensure that various errors / warnings are redirected to GUI dialogs rather than standard output, especially for embedded ports lacking these i.e. Smartphones such as Android / IOS.
However, there are a lot of possible warnings i.e. non-fatal errors and thus this needs to be done on a case by case basis to ensure the user is not drowned by irrelevant junk. Patches welcome.
Also, it may only be possible to respond "Save Failed" or similar as the backend and underlying Operating System Filesystem API may not implement or give a more descriptive error message/code back. However, I think Android could be fixed for this... Again, patches would be welcomed for this.