It's my view that the .ini file for radio configuration was an excellent choice, particularly for the time of it's original inception. This has allowed Dxbase users to add and tweak support for most new radios as the came out.
I think it could be extended a bit, better documented and modernised (perhaps as a human readable XML file?) It would be nice if this also allowed easy control over the order in which commands were sent in response to functions in Dxbase and allowed for some error handling if no response is received (I.e fail silently or retry 'X' times before giving up ) For example most radios with per band memories don't respond properly when the mode change is sent before the frequency change if a band change is also involved, I got around this with the K2/ K3 entries by including the mode set at the end of the frequency set line and left the mode set line as 'null' but it's a bit of a hack. the decision NOT to blindly poll the radio continuously was a very good one, especially now that the logging program may not be the only device connected to the radio's com port For example the K3 / P3 combo can get a bit sluggish if polled too aggressively it would also be nice if firing up DXbase whilst some other program has control of the radio did NOT permanently disable the radio port and suspending the radio should temporarily free up the com port for other applications lastly, it might be nice if Icom someday got around to supporting reading the split status of the radio.. -- 73 Brendan EI6IZ ______________________________________________________________ Dxbase mailing list Home: http://mailman.qth.net/mailman/listinfo/dxbase Help: http://mailman.qth.net/mmfaq.htm Post: mailto:[email protected] This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html
