Thanks for all the good ideas. I suspect that getting the roster-management features working is going to take a couple of go-rounds, so I should probably get started on that first.
So the next question is: what needs to be there, and how should it look?
My original idea was that the "update roster" button would remake the index, so any files you've inserted or deleted in the prefs/roster directory would be known. That seems way too simple now.
It sounds like people want that, plus:
a) A way to delete an entry
b) A way to duplicate an entry (so they can make a new loco that's "the same except ...")
c) Import and export of roster files, so you can carry them around with the locomotive itself.
d) Starting values for specific decoders, so when a new file is created its default contents are what you'd like as a starting point for that model of decoder.
e) A way to copy an entry ("Make this one like the other one that I just updated ..."). I'm not sure how to actually use that, so I'd appreciate it if somebody could walk me through what you have in mind. The tricky bit seems to be updating just part of the contents; which part?
f) Clearer documentation, esp. the connections between files, filenames and the roster contents.
That seems like enough to start.
I'll probably create a "Roster" window that has buttons to do all these things, along with a (scrolling) list of defined locomotives. Or maybe a small table where you can edit things directly?
Suggestions are always welcome!
Bob
--
--------------
Bob Jacobsen (Bob_Jacobsen@..., 510-486-7355, fax 510-495-2957)
Bob Jacobsen