One way to solve this is to show the results in a more verbose
widget. Maybe a scrollable list of decoder names, with up to 10
showing? That would make it clear that there are multiple choices,
because you could see the alternatives. The scroll bars would make
it clear what to do to see the rest of them if the list is too long.
You'd select one by highlighting it.<
Sometimes these problems can be solved with instructions and/or
training. As I think my clinic proved just a little time with DecoderPro
and it becomes very easy to use. The concept between trying to identify
what is in the engine vs just selecting the decoder doesn't become a large
problem. Of course if you just bought an engine and want to know what's in
it then that becomes a different matter.
The problem of the famous 255 reading (and other happenings) is not
unique to DecoderPro even throttles will do that. I think instructions or
text can work here. Of course I'm like everyone and don't read stuff
either<VBG>.
The small group that was at my house quickly adapted to which list to
pull down. Maybe I'm getting a little political here but it seems to me
that the time needs to be spent on areas that tend (and here is where IMHO
comes in) to need a lot of help. Having DecoderPro work with the MS100,
which I think is probably not an easy job. Getting more decoders in the
list. Tying the decoder listings to families.
Now I'm sounding like a ***! Seriously though, thoughts
on this. It's ok to tell me to go back to my cage!
Jon Miller
AT&SF
For me time has stopped in 1941
Digitrax DCC owner, Chief system
NMRA Life member #2623
Member SFRH&MS
