http://iscoresports.com/

I was keeping score on my sons baseball game. In the fifth inning I realized a runner in the third inning I showed stranded at third base actually scored.

How do I go back and change that runner from stranded at third base to scored?

You would need to back up to that point and re-score from there. You can't make game-changing edits like that otherwise.

Ugh! You'd have to redo everything that happened after the change?

Yes - a runner scoring is a game-changing event.

Yes, exactly! This is a game-changing event. Therefore, it's important to correct it. I've seen this limitation in response to many forum questions about correcting mistakes. Is there something subtle about why the capability for arbitrary edits cannot be added to the program? We use iScore primarily as a statistics-tracker (rather than a scorebook of record). It's way too easy as games get busy to miss a ball or strike or to mis-report the fate of a runner. Please, if it doesn't cause a train wreck, add this capability!!

You can edit the stats easily if that is your main concern. Much easier than rescoring.

Still don't see why there isn't a more flexible editing mode within the pitch-by-pitch view (for example). Insert a missed pitch. Change where a runner ended up after a play. Change whether the run scored or not.

Yes, I suppose you can directly edit the stats, but doesn't that defeat the purpose of the program in the first place? It assumes I've got an independent record of the events (e.g. first pitch strikes is a stat that isn't often recorded in hardcopy books). I would also have to do all the recalculations instead of having the program do them.

@jteastone -
as a third party user, here is my observation on this topic, which comes up periodically from the user community......


that is part of the nature of iscore program. for a number of reasons, the developers have taken a conservative approach and constrained post editing to keep the dependent variables in check and to eliminate unintended consequences. Part of this is i believe is a programing complexity and quality assurance issue and part is that In baseball events are interdependent, making changes can have unintended or illogical consequences. So iscore developers took the approach to enhance real time scoring quality and tradeoff post edit flexibility. (FYI - version one did not have editing, and as the software has evolved from version 1 to 2 to 3 etc, the developers have routinely added more editing capabilities when they can isolate interdependencies, and prove no unintended downstream effects. I expect that trend to continue with future releases. that said, Other software programs for scoring may take a different approach, even allowing free style editing, and those programs like paper and pencil have strengths and weakness, but I do not expect iscore to ever be "free form". that said, the developers monitor these forums and take user input very seriously.