On 31/05/2015 12:59, Michael Black wrote:
Hi Mike,
> How about putting some sort of rev# in the INI so that WSJT-X knows when it
> needs to update/change something in it?
> So..
> If (revnumber < XXX) {
> MessageBox("Frequencies need to be reset");
> If (ok) {
> Reset freq...
> Etc...
> Update rev....
> }
> }
I don't like this idea as it adds a whole new class of potential
configuration bugs like the fact that your logic only deals with forward
moves and not backward moves. It is fairly easy to make settings keys
both forward and backwards compatible and in this case before any
release I would change the key name which is better than any type of
schema number.
I think it is quite reasonable for developers and self building testers
to have to make so internal adjustments while development code settles down.
If you are really keen to not have to reset the frequency list at all I
can change the key name every time the format or default content changes
but to me it seems wasted effort that just clutters up all the
developers settings files.
>
> This would cover the upgrade too.
>
> 73
> Mike W9MDB
73
Bill
G4WJS.
>
> -----Original Message-----
> From: Joe Taylor [mailto:j...@princeton.edu]
> Sent: Sunday, May 31, 2015 6:50 AM
> To: WSJT software development
> Subject: Re: [wsjt-devel] Wsjt-x r5469 & r5472
>
> Hi Josh, Steve --
>
> On 5/31/2015 1:24 AM, Steven Franke wrote:
>> Hmm. 80m is still not working after r5473 (fix for wrong frequency
> entries).
>
> After starting v1.6 r5473 you will need to (once) go to the Frequencies tab
> and hit the Reset button.
>
> -- Joe
------------------------------------------------------------------------------
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
