http://iscoresports.com/

Can not recall if this has been surfaced before or not. ...

Potential Glitch
most current iPad version 3.54
(ok on iphone version 3.54, not sure on Andorid)

With runner on base, When ball in play (hit or error) followed by force out lead runner, the prompt screen to touch each fielder involved in the out is missing...

(example runner on first, no outs, in play, safe, single, spot hit, what happen to runner at first? Out, 2nd, Force Out, jumps to What happen to batter ? screen, safe, held Up.)

When the ball is hit in play, the touches are asked for as part of the batter. When you have a Force Out during a play, the batter can not Reach on Error by definition (if a force out occurs ahead of the batter, it is a Fielder's Choice, not an Error).

Same with a single... you can not have a Single AND a force out on a lead runner. That by definition would not be a single. It would be a Fielder's Choice.

If you enter Fielder's Choice (as would be the correct scoring for all force out of leading runner situations), then iScore does prompt for the touches that took place.

This answer is in line with the other post on how to score a play hit to SS. In that case there was a force out at third. FC!

I understand your logic on the "Force out vs fielders choice" (in other thread) and then the derivatove why no "touch each position that handled the ball" screen.. but still think there is a potential issue in the software versions . let me try again and separate into two parts.

1) the Appliction is behaving differently on the two different platforms - ipone and ipad. the same set of key strokes on ipad and iphone produce different screen flow (don't have an android handy to decide the icebreaker). One of them would seem to be correct and the other not. that was the softare issue i wanted to surface in this thread.

2) As to which it should be, (that gets to the other thread) .. I like the iphone method because most flexible as it lets the user assign assit and put outs to any baserunners out situation. even if it is technically not correct. if there are no exceptions to the rule .. then not having it (like on ipad) make sense . even better if a force out is technically not possible after a reach on error, why not gray out Force Out in that logic flow.


thanks

There are several places where we allow users to enter something the way they see it as a scorekeeper rather than preventing it and getting asked questions about it over and over. One very common example is Sacrifice Fly. Many people think advancing a runner is all that is required to give a sacrifice fly, but that is not true - the runner must score. We allow a user to enter it however.

This is another case like that where we allow the user to enter what they want.

Sadly, here is the problem with not allowing it... people write a review in iTunes saying "software does not allow me to do such and such" (in this case, people would say "software does not allow me to enter a force out - piece of garbage" or something similar). We then have no way to respond in iTunes saying that the review is not valid or that it is user error, or whatever the case may be.

While we do not allow this kind of silliness to drive the product, it is a very real consideration that we have to deal with. So our philosophy is to allow people to score within the rules, but we do not prevent people from scoring something incorrectly in all cases as it is still scorekeeper's judgment (even coaches will tell a scorekeeper to score something different than the reality).

Went a bit on a tangent here --- we may add the touches to the iPad version in a future update, but again, this is more evidence of the point that we need to allow things even when they are not valid or people will say that iScore is broken when it is not.

Tangent understood and appreciated.

So the bottom line is you are aware the screen flow is different in the two versions, iPad and iPhone. and it is that way either by design or on the list for future consideration to make same (one way or the other)

Curious, which way is it on the android platform ? Is it same as iPad or iPhone?

We will continue making the experiences as close to the same as possible in future updates. Don't have an Android device at my side currently, but it most likely works the way the iPhone version does.