Neil Williams wrote

And why can't iBus just be told that a particular stop is closed for
a
particular route, then the announcements work automatically? It
doesn't seem a difficult thing to do - nor would the one about "The

It does happen and IBus can do automatically or so I assumed in my post
of 19 Jan '09, subject iBus

== quote
However I recently noted a logical flaw which affects the above. When a
stop is closed it is still announced but there is no announcement at
the previous stop.

Thus "The next stop is The Dysart"
press bell

burst of music, then "The next stop is closed"

Then the normal announcement "The next stop is closed"

(observed on 65 Kingston-Richmond 10 am Sat 10 Jan and on the 371 on
return)

If the walk back is much the same as the walk from the previous stop
this doesn't matter much but here the next stop for the 65 is 500 m on
and for the 371 it's 600 m and at the top of Star & Garter hill.

So I suggest "The next stop is Petersham Fox & Duck", "The following
stop is closed" and/or "also alight here for The Dysart".

This didn't affect me since when the bus halted at the temporary
traffic lights the driver stretched a point and let me off anyway -
thanks.
==

--
Mike D