My view is that some of the things that may come from this and later LCC
will expand the flexibility of the throttle concept. My thought that
currently it only has one variable value (speed) is one limitation. Things
like brakes, intensity, volume, rotation, etc... these are all things that
might come around needing a second variable (knob on throttle). I don't know
if we'd conceive of a need for string input (voice announcements?) and
multi-state things like radio buttons could ride as Booleans (which we do)
but not as clean.
I think our basic design is flexible enough to gain some more features.
Finding examples that have them will really drive this. If we don't have
hardware to show the path, it is really hard to plot a good course to get
there.
-Ken Cameron, Member JMRI Dev Team
www.jmri.org
www.fingerlakeslivesteamers.org
www.cnymod.org
www.syracusemodelrr.org