¿ªÔÆÌåÓý

Locked Re: Storing roster (and other) files under different customized names


 

Joern

I do this regularly by appending some descriptor to the name of the locomotive before I do a "save to roster".??

Tom Wilson

Colorado Springs, CO


On Sun, Jun 2, 2019, 6:56 AM Dr. Joern Behnke <joern.behnke@...> wrote:
@ Ken Cameron, Member JMRI Dev Team
I have been using SPROG together with JMRI DecoderPro 4.15.6 for some weeks now and find both very helpful.
But? - in my way of looking - there is one real drawback in the software:
You can't store roster files under an informative name you pick yourself. Only a file *.xml is created for the current state of decoder-programming plus a file *.xml.bak which describes the last but one state. A command? "save as ...." is missing !
For instance once you program a decoder and deal with BEMF many trials are necessary to find the final solution.Oftimes trial no.5 proves to be better than trial no.10. But you will not find the corresponding file no.5, all you have is no.10.xml and no.9.xml.bak.
The LokProgrammer of ESU is a good example of how to create different files for different states of programming a decoder.

This is just a suggestion, perhaps it could be implemented in futureJMRI software releases.

Kind regards

Joern

Join [email protected] to automatically receive all group messages.