home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
The Datafile PD-CD 5
/
DATAFILE_PDCD5.iso
/
utilities
/
c
/
cbs
/
CSB
/
Editor
< prev
next >
Wrap
Text File
|
1995-09-09
|
4KB
|
114 lines
Cricket.Docs.Editor / Fri 8th September 1995
WHY?
Some things cannot be neatly expressed in a ball code. For example, a
no-ball from which two leg-byes are taken before one of the batsmen is run
out. 'n2' gives batsman credit instead of noballs; 'l2' is worse - bowler
isn't penalised and the over will end up short, and we haven't started
talking about the wicket.
We all make mistakes. You think a leg-bye was scored, but when you look up
from the screen/book, the umpire is looking at you as he crosses his arms
below his waist - dead ball. Or the 'short run' signal from the square-leg
umpire. Or... the list goes on.
Say you forget to click 'Halt' at the end of a day's play?
Or get the next batsman in wrong?
Or the umpire changes his mind about a call?
Or you get to a match part-way through and want to record it all?
All of these - and more - can be fixed using the Editor.
HOW?
Here are some examples.
"Edit->Area->option" means "Open the editor, select the current innings,
select 'Area' and put the caret in 'option'."
"+= n" means "add n to the thing before the plus".
"-= n" means "take off n from the thing before the minus".
Click OK (inner) before you change area.
"OK" means "Click the outer OK button".
1) One legbye recorded; should have been a dot-ball.
Ball code: [already entered] l
Edit->score->legbyes -= 1
OK
Swap batsmen
2) You click 'OK' by accident before entering the '1' ball code.
Ball code: [already entered] ""
Edit->score->runs off the bat += 1
->batting[current striker]->runs += 1
->bowling[current bowler]->runs conceded += 1
->fow[current]->partership += 1
3) A no-ball is bowled. It goes past the 'keeper for two legbyes.
Ball code: n2
Edit->batting[current striker]->runs -= 2
->score->runs off bat -= 2
->noballs += 2
OK
4) A no-ball is bowled. It goes for two legbyes & then a runout happens.
Ball code: w
Wicket window: run out (relevent batsman)
no runs scored.
Edit->score->noballs += 2
->last wicket += 2
->innings->balls this over -= 1
->bowling[current bowler]->runs against += 2
->noballs bowled += 1
->overs bowled -= one ball (eg 4.3 => 4.2)
->fow[the wicket that just fell]->partnership += 2
OK
5) You get to a 1-innings match part-way through the 2nd innings - they are
42 for 3. A friendly scorer (paper & pencil) has been there all along. The
side which batted first was bowled out for 244.
Run CSB, supply teamfiles, select the match type, choose the toss winner.
Enter the 'Start Innings' information for the first (finished) innings.
Edit->[first innings]score->runs off the bat
->extras
->innings->wickets down = 10
->change innings now = 1
OK
Enter the 'Start Innings' information for the team batting second, but
enter the batsmen CURRENTLY at the crease.
Edit->score-> extras/runs = 42
->innings->wickets down = 3
->batting[first man at crease]->all information, inc. BO
[other man at crease]->all information, inc. BO
OK
You are now in a position to score from the present position while you use
the Editor to enter the details of the first innings and those of the
first which have already transpired.
6) You've mistakenly put Brown in as the batsman instead of White.
Brown's batting order is 5.
Use the 'Swap' button so Brown is on strike.
Edit->batting[Brown]->batting order = 0
->how out = ""
->batting[White]->batting order = 5
->how out = "not out"
->innings->facing batsman = {Click menu button to right of 'Innings
details'; choose "White";}
OK
Note that this would still work if it was a few overs before you noticed
'Brown' was White; by altering the 'facing batsman' field, all details of the
man in (who shouldn't be) are added to those of the new man (who should have
been in all along).