Please, I accidentally over written it and want it back.
That is bad luck. The old contents have been overwritten by new data, and unless you use automatic backups or a staging file system, they are lost.
Maybe you should check if any auto-save file was generated during gameplay. That's the only chance to get your savefile back I can imagine right now.
Maybe there should be a warning like this:
"WARNING If you overwrite the savefile, the old one will be deleted."
You, my friend, are a genius. I support your idea.
Well in general you press OK before you read the warning...
Also in simutrans, you have to press a button/enter a name before any saving is done ...
Confirm window is not the only one to avoid human error.
People often click 'Yes', without thinking.
I think we need to investigate why plyers often overwrite savefile by accident.
In next version, button works as normal window system, it will require mouse down and up on the same button. So, ability to hit the wrong button should be less than current version.
But in the case player mistake 'save dialogue' and 'load dialog', we need to use different approach.
For example, remove 'Load' button from 'Options' window, and player must access to 'Load' dialogue via 'Create a new game' window might help.
Another suggestion: when you exit Simutrans let the program ask: do you want to save the changes, Yes/No. That's what most programs in Windows do.
Unresolvable conflict of views and traditions.
I like the unix style. If I click "Quit", just quit. I know what I do, the button label is clear and distinct, no need to bother me with questions.
Hypothetically... one could have a setting for no overwriting of saves. Why would one want to overwrite previous save? There is a conceptual leap from "updated" to "versioned" and once on the other side, you never look back.
How about this solution:
We save two files game.sve and game.sve.backup.
game.sve.backup is always the last save without error.
The gui wil remain as it is.
So, you're saying that those using Windows Are stupid for needing warnings? SELF OPINIONATIVE that was, and when EITHER of you two make a mistake like this, which you claim to have never done because you feel to have a higher IQ than the coders of Windows, then you'll want to sue Unix for making sure that human errors increase. Of course, of which, they won't do anything as that quote is evidence that you actually support the error happening to Windows users worldwide.
I've got antother "great":) idea: there could be an option like: ask_overwrite = 1 in simuconf.tab...
I think it's clear, but for persons who don't understand it:
1 means asking before overwriting
0 means no asking before overwriting
But
mayby maybe it's a bit complicated for this little problem
The simutrans UI cannot have are you sure boxes, they are really a pain to do and will kill the reasonable from of time.
But a setting that any game is overwritten after remaning any exisiting file into xxx.bak is simple to implement. If it helps ...
It was half a joke, but if you really think you must attack me this way, well it's now quoted for even more attention. Readers can read my message up there and see themselves what they want to read from it.
Edit: If it is on any solace, I have lost work, too, since most of my tools do not ask for deleting, quitting or overwriting things. But that is my fault, if I do not think carefully.
Edit 2: I'm sorry that my message hurt you so much. It seemed like a funny idea when I wrote it, but I see that windows users (which I am too since many years) can feel offended. I just played the cliché card without thinking. I want to apologize for having hurt you, but I want to stand to my words that I think there are too many unneeded confirmation boxes in many programs.
Very reasonable indeed! I support this.
IMHO, I really can't see any need for it. I would definetly cl****ify this case as a feature for the read my mind button. I already type in a name when I click the save button; I also can accidentaly overwrite a wanted file and loose it, of course, but it will be that: just an accident.
Accidents are usually bad, not good...
That is an excellent idea. Also a good idea is permitting saved games to be automatically backed up to a different directory so that the saves are present in two locations. For example, in Windows, if one's ordinary save game folder is C:/My Documents/Simutrans/save, one could set so that a copy is saved there
and a further copy saved into (for example) F:/Backup/Simutrans/save. The backup location could be specified in simuconf.tab.
I'm a windows user. I have to have help just turning on a Mac, and I've never even seen the penguin's os. Still, I often find warning messages annoying. I turned off UAC the day after I brought my Vista computer home from Wally World. I have overwritten saved games before, but a warning box wouldn't have stopped me.
i've also killed a lot of hours of work by cautionless rm ...
but if i count them, it is by far not as much time as i wasted in windows with having to confirm everything. wich also did not prevent me at all from errors. the frequent query causes an automatism with confirming, so usually most people notice the mistake only AFTER hitting ok.
my solution in linux was twofold first to >touch -i in all dirs with important files, and second to backup my work on a regular basis (i'm bziping sourcecode and tex with every make, with a dead time of 10 min)
the result is that i'm much safer in the seemingly less safe gui environment, as i took precautions to prevent failure instead of relying on an ilusionary safeguard.
my suggestion for simutrans, as default backup overwritten savegames, and make them visible in the load dialogue. delete the backup after a new savegame is saved or overwrite it if the savegame is overwritten again.
@Hajo & Reddog
maybe rephrase it that way:
btw. i absolutely sure half of the dialogues are also a practical joke of microsoft's devs