Idiot proofing (replied)
Posted: Sun May 28, 2017 5:57 am
After losing an entire game because I imported before exporting I found a flaw. The app should WARN what the consequences will be OR Export data BEFORE importing on request.
Here is the scenario,
Bottom of the 3rd, 2 Outs, Runner on First, Full Count, Pitcher throws, runner on first steals, second, Catcher throws down runner at Second for an Out, Ends the inning, Umpire Calls Game on time... The umpire never called the Pitch a Strike or Ball... I tried to fix this in game edit but adjusting pitch counts isn't easy. I did and undo but when I recored the pitch as a strike (what I thought it was), the rest of the game disappeared. I then made the BIGGEST mistake, I 'Imported' before Exporting the game losing all data. But, IMO, the app should have at least known a pitch was thrown (not a strike, ball, etc...) but a pitch. Otherwise, there is no way the catcher could have thrown down to Second for the Out...
Without the Umpire calling the pitch, it was impossible for me to score the pitch, so I put this on the Umpire but I understand why he didn't because of the situation. Perhaps a (rare Not Called selection in the app) to keep the pitch count updated properly... It's more important that the count is correct than whether it's a ball, strike, or foul... In Youth Leagues, the pitch count is IMPORTANT... Games are forfeited if you make a mistake...
Another easy way to keep the Pitch count correct is to Put a 'Pitch' button, and then Select whether it was a Ball, Strike, Foul, etc... Just because of this type of scenario. It's important to keep some data sacred for Youth Leagues, Pitch Count is one of them... Actually the MOST important, in the end no one cares what the batting average, ERA, etc... are, but a wrong Pitch Count can cost you the game...
Here is the scenario,
Bottom of the 3rd, 2 Outs, Runner on First, Full Count, Pitcher throws, runner on first steals, second, Catcher throws down runner at Second for an Out, Ends the inning, Umpire Calls Game on time... The umpire never called the Pitch a Strike or Ball... I tried to fix this in game edit but adjusting pitch counts isn't easy. I did and undo but when I recored the pitch as a strike (what I thought it was), the rest of the game disappeared. I then made the BIGGEST mistake, I 'Imported' before Exporting the game losing all data. But, IMO, the app should have at least known a pitch was thrown (not a strike, ball, etc...) but a pitch. Otherwise, there is no way the catcher could have thrown down to Second for the Out...
Without the Umpire calling the pitch, it was impossible for me to score the pitch, so I put this on the Umpire but I understand why he didn't because of the situation. Perhaps a (rare Not Called selection in the app) to keep the pitch count updated properly... It's more important that the count is correct than whether it's a ball, strike, or foul... In Youth Leagues, the pitch count is IMPORTANT... Games are forfeited if you make a mistake...
Another easy way to keep the Pitch count correct is to Put a 'Pitch' button, and then Select whether it was a Ball, Strike, Foul, etc... Just because of this type of scenario. It's important to keep some data sacred for Youth Leagues, Pitch Count is one of them... Actually the MOST important, in the end no one cares what the batting average, ERA, etc... are, but a wrong Pitch Count can cost you the game...