Simple script to make codeplug changes easier.

[OH1KH]

(while waiting that someone writes GUI for dmrconfig).

I have used this script to get a little automation for codeplug fixing process. Seems to work, but GUI would be very very appreciated.

[sergev]

Hi Sakari,
Thank you for the useful script. Looks like a good start for a user friendly interface for dmrconfig. I would propose a few improvements.
(1) On "Read from radio" phase, check that the radio is being connected. Do not progress to the Edit step until a valid configuration is obtained from the radio.
(2) In addition to a text backup, always save a binary backup like 2018.12.04_11:35:55_device.img.
(3) After exiting from editor, ask the user for confirmation before writing to the radio.
(4) Use /usr/bin/dialog for user interaction.

[OH1KH]

Hi!

1. Hmm... lsusb to find it out. Perhaps Do you have better ideas?
   Progress to edit can be done also if jumping directly to .conf (fixing old file ->1st starting parameter), not always via reading it from radio. Lot more quicker.
2. It can be done, but is it really needed? I have used same binary for many .conf versions with success.
   And because we can not change any settings there it should be always same.
3. Good point
4. I do not have that in my Fedora28/LXDE. I have used it few times many years ago (>10). (I Like more command console) I check if it is in repository.

[OH1KH]

1. Hmm.. Afterwards it can be done with exit code and loop back. Yes.
   But before... could we have " dmrconfig -i Radio model info" or something that jus tinforms the radio name we have connected (or exit code 255 if not connected).
   I.E. the same 1st line as in reading "Connected to..." but without device reading after that.