Palmcricket Manual

Ball-by-ball Edits

The Edit Button allows full access to every event during the entire match. This means that one can use the Ball-by-ball edit to correct mistakes much later, e.g. a disputed 4 which was actually a 6, 5 overs ago.

Navigation: The ball-by-ball navigation controls allow one to scroll backwards and forwards by ball, over, or innings in order to position the focus of the edit on the exact ball where the error was made. Their operation is described below:

The navigation section of the ball-by-ball edit screen consists of the top row of buttons, which moves the focus of the current ball as follows in button order from left to right: start of innings, previous over, previous event, next event, next over, end of innings.

ruler navigation The ruler section allows on to position the current focus in larger jumps. Just tap anywhere inside the ruler to move the focus to say half way, quarter way etc. To the left and right of the ruler are arrow buttons which allow one to move the focus to previous or next innings, either or both of these will only appear if there are previous or next innings recorded. Normally, by tapping inside the ruler and using the next over/previous over buttons (the double arrows in the row of buttons), it should take only about 3 to 4 taps to locate the right over. Then tap on the next ball/previous ball (the single arrows in the row of buttons) to position the focus on the right event, as shown by the over, ball and event indicators at the top left of the screen.

Corrections affecting current ball: To access any over in the current or previous innings, navigate to the correct over and innings as described above. Changes to the current ball are made by tapping the required buttons, and/or striker. If, for instance, a run was scored to the wrong batter, just tick the correct batter. Extras can be switched on or off, in order to correct the type of extra, or to change it to a normal ball by tapping on the ball button. In the following example in the 50th over, ball 49.6 is changed from a single by batter 7 to 3 runs by batter 3.

Dismissal events provide additional information regarding the method of dismissal and the fielder involved, if any. These can also be corrected when they appear on screen. To correct a fielder selection error, tap on the fielder name (Mark Waugh in the example below) and select the correct player from the pop-up list as shown.

To correct the method of dismissal, tap on the incorrect "how out" field and select the correct dismissal from the drop down menu. The correction of the method of dismissal from "caught" to "stumped" is illustrated below:

Once any changes have been made to the current ball, the Upd (update) button will appear. All changes that affect a single ball are only effected after tapping the update button.

More wide-ranging changes that affect more than one ball are also possible. These corrections relate to the bowler, batter dismissed and ball insertions/deletions, as described below. These wider changes are effected directly after confirmation. The update button is not applicable in these cases and thus does not appear. Although these changes are far-reaching, they are easily "undone" by repeating the correction using the original bowler or batter dismissed, or by applying the opposite action for dot ball insertions and deletions.

Bowler corrections One can also use the ball-by-ball edit screen to correct a bowler player selection error made during the current over, or any previous over in any innings. Position the ball-by-ball focus on any ball in the over of interest, tap on the bowler name and follow the prompts, as shown in the sequence below:

The bowler for the current over in the current innings can also be changed directly from the main screen [Bowler] button as described in Correcting Bowler Selection Errors.

Batter dismissed: Very occasionally, the wrong batter is dismissed and the mistake is only discovered much later, after a number of balls have been bowled or the innings or match has been completed. From a player and scoring perspective, this is quite a significant error, since all runs scored subsequent to the dismissal will be allocated incorrectly to the player that continues to bat and the unfortunate batter dismissed in error will be deprived of those runs. The ball-by-ball edit overcomes this scoring predicament by allowing one to swap the dismissed and not-out players for any dismissal ball in the innings. This correction can be applied at any time. All subsequent balls and all affected batting records in the innings are adjusted automatically and instantaneously. Such corrections are triggered easily by tapping on the Swp button and confirming the correction, as shown below:

This correction applies only to correcting the dismissal of the wrong batter. It must must not be confused with the shuffle action that can be triggered from the batting summary to correct errors made when selecting the next player coming out to bat.

Dot ball insertions and deletions: These functions allow one to add or erase dot balls anywhere in a score-sheet. Indirectly, this allows one to insert or delete any valid ball other than dismissals, since dot balls can be converted to other scoring balls and vice versa, using the normal ball-by-ball edit functions. Such corrections are triggered easily by tapping on either the Ins or Del buttons and confirming the correction using the Yes button, as illustrated below:

Dot balls are inserted with an event time one second earlier or later then the current event's recorded time.

Ball-by-ball edits allow correction of all minor and most major scoring mistakes, quickly and effectively, and is the preferred approach. The advantage of making corrections in this way is that the time for each ball, as recorded originally, is retained. [In contrast, the left arrow button effects a backspace deletion, which loses the previous ball. Hence if one goes too far back, one must re-instate the in-between balls. Not only is it quite difficult to reconstruct events accurately when many different actions took place, but the original timing for every ball re-scored is lost.]

Although ball-by-ball edits are quite powerful in correcting runs, extras, batter on strike, bowler, fielder, method of dismissal or batter dismissed, extra care is still necessary when recording dismissals. A dismissal cannot be erased by a ball-by-ball edit. This can be achieved only by using the left arrow and then re-scoring the dismissal from scratch, directly after the event, as explained under correcting scoring errors and dismissals above.