Actually, I think the date should be last, so that different dated versions of the same IMG file will group together in file listings. In general, file names should go from general to specific to assure sorting nicely. Plus, a team, such as a CERT team or search and rescue team, will likely have the same model of radio, so the differences will be in members' names; not radio models. In addition, I would only use a dot just before the file type; not within the file name itelf, to keep it clean looking and avoid unexpected sorting. Thus, I propose the pattern to be: %(vendor)_%(model)_%(userinput)_%(date).img

When someone wants to make a particular one the master, all that's needed is to remove the date portion of the file name, and it will sort at the top of the others just like it.

Examples:

Btech_UV-5R_dad_ht.img
Btech_UV-5R_dad_ht_20151120.img
Btech_UV-5R_dad_ht_20160616.img
Btech_UV-5R_mom_ht.img
Btech_ UV-5R_mom_h t_20160616.img
QYT_KT8900R_dad_car_20160501.img

My $0.02,
Robert
AG6ZZ

Intresting, I vote for that feature!

From my point of view a date segment will be of great help, like this:

%(userinput).%(date).%(vendor)_%(model).img

Examples:

dad_ht.20160616.Btech_UV-5R.img

dad_car.20160501.QYT_KT8900R.img

On Wed, Jun 15, 2016 at 7:28 AM, Pavel Milanes (CO7WT)  wrote: 

So my recommendation is that you NAME the image file like your radio vendor/model; this way you will get get a "tip from the past" when months in the future you hit with this odd behavior. 

You know, we could automate this in the Save dialog. Maybe default to something like %(userinput).%(vendor)_%(model).img.  Tom KD7LXL _______________________________________________ chirp_devel mailing list chirp_devel@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_devel Developer docs: http://chirp.danplanet.com/projects/chirp/wiki/Developers  

--  73 Pavel CO7WT.