Post by slashlos on Jun 13, 2005 16:39:52 GMT -5
This weekend I had lost a game; actually I'd overwritten in by accident. Here's the scenario from memory, but I was totally bummed when this happened, but perhaps it could help someone else:
1. A team I was following was to play 3 games in 1 day
2. I didn't know the line-up so I entered the visitor/home
for the first game and entered player info as I got their
#'s and position as always.
3. I had completed scroing game #1, then went onto
game #2 by doing a 'New game' and said yes to the
save dialog.
I had also check the 'last batter' beforehand. This I
considered a final game and could have been marked
read-only..
4. I had entered the home and visitor team names as
before, but didn't notice that it didn't take one team
name entry but instead recognized a team name
entered earlier!
5. I noticed that at the first batter that the I home/visitor
slots had to be swapped, which I did at my normal end
of inning save.
6. BAM!, my prior game was gone.
I guess I should have noticed the wrong team name when entering the team names in game information, but was a surprise nonetheless, when the overwrite occured. I guess
I wish the act of checking 'last batter' had some safety significance. I think a feature to act upon the 'last batter' checkbox, would be to prompt to save and mark file read-only. True this can be done manually albeit externally.
However, the feature that would have saved me was that whenever a new game is etiher implicity started by starting the program, or explicity via the New game menu option, the first save should act as if a "SAVE-AS" was ordered. This would have caught the earlier games existence and prompted me to confirm the overwrite.
As all games took place on the same date, and incorrectly by the same teams, it got overwritten. In hindsight I should have marked the earlier complete game scored as read-only using the file explorer but hindsight is 20-20 as they say.
So, I wish for
1. an implicit initial save-as on all new games.
2. checking 'last batter' creates a final read-only save
Of course I presume read-only games cannot be overwritten unless the protection mode is explicity unchecked by the file-explorer.
1. A team I was following was to play 3 games in 1 day
2. I didn't know the line-up so I entered the visitor/home
for the first game and entered player info as I got their
#'s and position as always.
3. I had completed scroing game #1, then went onto
game #2 by doing a 'New game' and said yes to the
save dialog.
I had also check the 'last batter' beforehand. This I
considered a final game and could have been marked
read-only..
4. I had entered the home and visitor team names as
before, but didn't notice that it didn't take one team
name entry but instead recognized a team name
entered earlier!
5. I noticed that at the first batter that the I home/visitor
slots had to be swapped, which I did at my normal end
of inning save.
6. BAM!, my prior game was gone.
I guess I should have noticed the wrong team name when entering the team names in game information, but was a surprise nonetheless, when the overwrite occured. I guess
I wish the act of checking 'last batter' had some safety significance. I think a feature to act upon the 'last batter' checkbox, would be to prompt to save and mark file read-only. True this can be done manually albeit externally.
However, the feature that would have saved me was that whenever a new game is etiher implicity started by starting the program, or explicity via the New game menu option, the first save should act as if a "SAVE-AS" was ordered. This would have caught the earlier games existence and prompted me to confirm the overwrite.
As all games took place on the same date, and incorrectly by the same teams, it got overwritten. In hindsight I should have marked the earlier complete game scored as read-only using the file explorer but hindsight is 20-20 as they say.
So, I wish for
1. an implicit initial save-as on all new games.
2. checking 'last batter' creates a final read-only save
Of course I presume read-only games cannot be overwritten unless the protection mode is explicity unchecked by the file-explorer.
