![]() |
Quote:
|
On most current clocks the horn sounds at 0.0 that would mean if the clock was stopped at showed 0.1 then the time would be somewhere greater than 0.0 but less than or equal to 0.1 therefore if the clock shows 0.3 the time would be somewhere from greater than 0.2 to less than or equal to 0.3 In short it would be 0.3 or less which in turn matches up with the wording of the rule. If the clock didn't work like this then it would be a full tenth after 0.0 was displayed until the horn.
|
Seems like the only logical solution is to just do things the way they have been done. Carry on.
|
Quote:
Peace |
Quote:
That's why there are cases (at least in some codes) where the clock shows 0:00.0 but the horn / lights haven't gone off / on. |
Quote:
I live in a state where the rules exam is a huge deal, to the extent that it pretty much determines the rating order. It's ridiculous, but I acknowledge that we can't scrap testing completely, otherwise you're likely to have rules kicked such as this one on a big stage even more often. |
Quote:
That's why I started my statemen with most clocks. I have never in my entire life been present at a game where there were zeros on the clock and no horn unless auto horn had been turned off. |
Quote:
Peace |
Quote:
Peace |
Quote:
|
Quote:
|
Quote:
|
Tick Tick Tick
Quote:
|
Quote:
|
Quote:
|
All times are GMT -5. The time now is 05:52am. |