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
Ideally, pressing Save would immediately write to the "gbm.s3db" file instead of waiting to write until the Game Manager window closes. Currently, it's possible to Save, kill the GBM process, re-run GBM and find that your changes were not saved.
Maybe there's a good reason why it's built like this? If so, perhaps Save should be renamed something like "Save on close"? Or, simply "Update" and perhaps add some text to the title bar or footer to say "Saves on close"?
As it stands, after pressing Save, there is no indication that the changes have not yet been written to the disk. For example, an asterisk somewhere, or italicised text on edited games in the list would help indicate uncommitted data.
Thanks.
GBM 1.3.1
Windows 11
The text was updated successfully, but these errors were encountered:
Ideally, pressing Save would immediately write to the "gbm.s3db" file instead of waiting to write until the Game Manager window closes. Currently, it's possible to Save, kill the GBM process, re-run GBM and find that your changes were not saved.
Maybe there's a good reason why it's built like this? If so, perhaps Save should be renamed something like "Save on close"? Or, simply "Update" and perhaps add some text to the title bar or footer to say "Saves on close"?
As it stands, after pressing Save, there is no indication that the changes have not yet been written to the disk. For example, an asterisk somewhere, or italicised text on edited games in the list would help indicate uncommitted data.
Thanks.
GBM 1.3.1
Windows 11
The text was updated successfully, but these errors were encountered: