Dick:
How many lines of code would it take to write a "script" to
accomplish this process behind the UI? Would this
significantly add to the download overhead of the Utility
application? Would it take an inordinate ammount of time to
develop?
I use a Laptop and a Desktop both with configuration
programs (along with K3-EZ) with my radio. A "Export
Utilities settings" and a "Import Utility settings" script
set with a big square "button" for each (OK, put it in the
file menu!) would be a handy addition to the software
package's feature set. There is plenty of room on the sheet
as it apears now, so its not a question of sheet real
estate.
Although I personally feel comfortable working with RegEdit,
many do not, and keeping registry manipulation away from
users is usually a good thing.
Serious damage can occur if you dont pay attention any time
youre messing with the Windows' Registry.
Just a thought for your development "features list".
Thanks for letting me know that this process is doable at
the registry level. Wish I would have known about it two
weeks ago :(
-Lu Romero - W4LT-
K3 #3192
-----------------
Date: Thu, 10 Sep 2009 16:13:04 -0700
From: "Dick Dievendorff" <die...@comcast.net>
Subject: Re: [Elecraft] K3 Utility settings transfer
To: "'Thom LaCosta'" <k3...@zerobeat.net>, "'Chris
M0PSK'"
<chrism0...@googlemail.com>
Cc: 'Elecraft Reflector' <elecraft@mailman.qth.net>
Message-ID: <000001ca326c$40aa7490$c1ff5d...@net>
Content-Type: text/plain; charset="us-ascii"
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 [k3...@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
______________________________________________________________
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:Elecraft@mailman.qth.net
This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html
