[Elecraft] K3 Utility settings transfer

[Dick Dievendorff]

.ini files have their own problems, that's why they have long been
deprecated for new application development. Raymond Chen explains why in
http://blogs.msdn.com/oldnewthing/archive/2007/11/26/6523907.aspx.  

There are issues with the Registry as well, but it's the solution a whole
lot of software authors choose for rapid hierarchal access to configuration
data.

If I were writing the K3 Utility with extensive library support (pick your
run-time library, VBRUN, .Net, Java, RealBasic, Qt, whatever), I might have
used an XML configuration file, as I did with K3 Voice.  One of the
constraints I accepted for the K3 Utility was a relatively small download
size (currently it's just over a megabyte, and about 2/3 of that is help
text and help file images), and to avoid prerequisite downloads and
installation issues commonly referred to as the "DLL Hell" problem.

Writing XML configuration files when things change is quite slow when
compared with registry writes as controls change.

YMMV for the software you write, Thom.

Dick, K6KR


-----Original Message-----
From: Thom LaCosta [mailto:k3hrn at zerobeat.net] 
Sent: Thursday, September 10, 2009 3:19 PM
To: Dick Dievendorff; Chris M0PSK
Cc: Elecraft Reflector
Subject: Re: [Elecraft] K3 Utility settings transfer

At 12:06 PM 09/10/09, Dick Dievendorff wrote:
>You can use the registry editor (regedit) to export the registry key

If the software used a config  or an .ini file, then one qould not 
have to do the registry dance.

73,
Thom k3hrn