Burns, I posted this same response on FB. I asked for this change some time ago and Don made the change in Version 2.30 Beta 4.Here's what I asked for initially..
Don,
This topic has come up by other users asking this question so I'm posing it to you.. Currently users have to refer to a tone list to select the the correct TX tone for editing satellites. In the case of SO-50 for example.. Why can't we manually enter the working or wake-up tone of 67.0 (1 in this case) or 74.4 (3 in this case) rather than cross check a list to find out what tone number 1 or 3 means?
Don's response.. "Version 2.30 Beta 4 requires the actual tone and ctcss values to be stored in mode.dat (e.g. 67.0) and the Modes editor - zero or blank still signifies no tone."
Steve Nordahl, NS3L