What if the label for that column in the UI were changed to something like "TX"? Then you'd have a column 'TX' with the options "+", "-", "split", "(None)", "Off".
Or, expanding on that, call it "TX offset", and change "Offset" to "Offset MHz"? Might make things a little clearer without needing to change anything else- the labels in the CSV wouldn't match the UI, but I'm not sure that would really be an issue. Even if so, it should be possible to change the import logic to recognize "duplex" = "tx_offset" and "offset" = "offset_mhz" (or whatever).
 
Ben


On Tue, Aug 26, 2014 at 7:28 PM, jon <jon@jonshouse.co.uk> wrote:

> > Personally I would re-structure the GUI to have a TX and RX frequency
> > and drop the entire duplex section, make an TX frequency of 0 be "no
> > transmit". That would be a large change though and might just be my own
> > personal preference :-)
>
> That preference would confuse like 90% of the users who are used to
> programming a receive frequency and offset.
:-D

> > Can't you simply change the text in the GUI and leave the the token (or
> > whatever moniker the language you write in calls it) as "off"
>
> Of course, but then we'd have None, Off, *and* NO_TX to explain to people :)
Yes, on the other hand only the people trying to reconcile a CSV file
against the source code ?  A number I suspect much smaller than the than
people seeing "Duplex=off" and thinking 'what on earth does that mean?'

That is what comments in source are for :-) ?

Or am I just getting old....

Thanks,
Jon




_______________________________________________
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