step() semantics have changes, should not use step() in Snow Dots

[GoogleCodeExporter]

I'm revisiting flow control in Tower of Psych, and making clearer user of the 
terms "run" and "step" as methods of run()nable and step()pable classes.  So 
these terms are acquiring more specific meanings and step() as used in Snow 
Dots is not really the same thing.

So I should rename step() methods in Snow Dots classes.  In each case there is 
probably a more specific name to describe the behavior, like readData, or 
readMessages.  Or at the very worst, "update".

Unless, that is, one of the Snow Dots classes wants to implement the steppable 
interface, which would be another kettle of corn.

Original issue reported on code.google.com by Benjamin.Heasly on 1 Jul 2010 at 9:32

[GoogleCodeExporter]

I went with that kettle of corn.  dotsAllRemoteObjectManagers implement the 
topsConcurrent interface (which is the renamed topsSteppable).  And it 
implements a runBriefly() (which is the renamed step()).

Otherwise, the Snow Dots no longer uses "step".  In particular, mexHID now uses 
"check" instead of "step".

Original comment by Benjamin.Heasly on 3 Aug 2010 at 6:12

• Changed state: Fixed