<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div>I'm adding support for split duplex on the Icom IC-7000 (a live mode radio) but I'm unhappy with the user experience. Now I'm trolling for suggestions.</div><div id="AppleMailSignature"><br></div><div id="AppleMailSignature">As I understand things, Memory.freq holds the receive frequency, Memory.offset holds the difference between the transmit and receive frequency, and Memory.duplex tells us to add, subtract, or ignore the offset to get our transmit frequency. Except when Memory.duplex equals "split", then Memory.offset holds the transmit frequency.</div><div id="AppleMailSignature"><br></div><div id="AppleMailSignature">Now my dilemma. The IC-7000 does not support per memory offset values but I set RadioFeature.has_offset True to get the memory editor to show the Offset column.</div><div id="AppleMailSignature"><br></div><div id="AppleMailSignature">The user can set duplex to split and enter the transmit frequency in the offset column, which sets the radio's memory channel correctly. So far, so good.</div><div id="AppleMailSignature"><br></div><div id="AppleMailSignature">What I don't like is that the user can edit the offset with the duplex set to "", "+", or "-". IcomCIVRadio.set_memory silently drops the offset but the user's change is displayed until the next refresh.</div><div id="AppleMailSignature"><br></div><div id="AppleMailSignature">Any corrections to my basic assumptions or suggestion on how leave the user less confused?<br><br><div><span style="font-size: 13pt;">-- wireless <<a href="mailto:Joseph.P.Scanlan@n7xsd.us">Joseph.P.Scanlan@n7xsd.us</a>> +1-702-896-0507</span></div>-- work <<a href="mailto:Joseph.P.Scanlan@clarkcountynv.gov">Joseph.P.Scanlan@ClarkCountyNV.gov</a>> +1-702-455-3679<br><div>-- </div><div>These mechanics</div><div>and mathematics</div><div>they give me comfort</div><div>when I'm afraid.</div><div> —Venus Hum</div></div></body></html>