Re: [wsjt-devel] Configurations

[Joe Taylor]

Hi Ed,

On 5/19/2020 8:49 PM, j...@comcast.net N4II wrote:


Exactly.  The difficulty is, at present there's no way for the new user to
know what you've just written -- other than by receiving an email from you,
or one of the other cognoscenti -- since it's not documented anywhere.  (I
learned about Configuration operation from a WSJT-X beta tester -- a local
club member.)

Note that "There is no need to re-enter most of your setup details" is
exactly opposite the instruction given in the User Manual:  "Rename it as
desired, and then make all desired settings for that configuration."


I must disagree.  Good use of the Configuration capability is certainly 
not "exactly opposite the instruction given in the User Manual". 
Thousands of WSJT-X users have used what's in the User Guide, together 
with the on-screen menu options, to make effective and convenient use of 
Configurations.


If you find something in the User Guide instructions that is confusing 
or hard to follow, by all means tell us!  How else will we know?  At the 
time we wrote it, we thought is was clear enough.


-- 73, Joe, K1JT


___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Configurations

[jan0]

Joe,

Exactly.  The difficulty is, at present there's no way for the new user to
know what you've just written -- other than by receiving an email from you,
or one of the other cognoscenti -- since it's not documented anywhere.  (I
learned about Configuration operation from a WSJT-X beta tester -- a local
club member.)

Note that "There is no need to re-enter most of your setup details" is
exactly opposite the instruction given in the User Manual:  "Rename it as
desired, and then make all desired settings for that configuration."

If you need help with the writing or editing, I'd be happy to pitch in.

Ed N4II.

-Original Message-
From: Joe Taylor  
Sent: Tuesday, May 19, 2020 7:03 PM
To: WSJT software development 
Subject: Re: [wsjt-devel] Configurations

Hi Ed,

Thanks for your comments, they are much appreciated.  A few comments inline
below.

On 5/19/2020 4:59 PM, j...@comcast.net N4II wrote:
> I sense a bit of, er, annoyance on behalf of WSJT-X developers with 
> the fact that relatively few users seem to be using Configurations -- 
> at least, the solution proposed to a fair number of user interface 
> issues raised here recently seems to be the same:  "Use Configurations".
> 
> When I first used the software, years ago, I didn't use configurations 
> for three reasons:
> 
> (1)  I couldn't find a list anywhere in the manual of just what "settings"
> were being "configured" (the File/Settings... settings?  To include 
> the main window check boxes?  Frequencies?  I still don't know the 
> complete list, even today);

Configurations save all settings that are normally restored after a program
restart, including which of the defined configurations is currently active.

> (2)  The manual didn't explain that I could avoid a lot of UI 
> annoyances by doing so, just that "[m]any users prefer to create and 
> use entries on the Configurations menu for switching between modes," 
> without saying why they have that preference; and
> 
> (3)  The Configurations menu picks didn't seem to do what I *thought* 
> I would want to do to start, which was to CREATE a configuration for 
> the settings I already had, followed by SAVE a configuration.  (I knew 
> I didn't want to CLONE anything . . . .)  If one has the manual at 
> hand, one has the single-sentence instruction to "Simply Clone the 
> Default entry, Rename it as desired, and then make all desired 
> settings for that configuration."  But even then, one has to make an 
> assumption on how the settings are saved, since the manual says 
> nothing about what one has to do to save a configuration (change modes or
bands?  Switch to a different configuration?
> Exit the program?).  Without an EDIT menu pick, it's also not at all 
> clear how one might modify a configuration to correct an error, which 
> makes experimenting with the feature a high-risk endeavor for new users.

CLONE is a much better description than CREATE for what happens.  You should
start with a working setup, configured the way you like it for some mode.
(If the only entry on your Configuration menu is "Default", you might want
to rename it as, say FT8.  Or Clone it, and rename the copy to FT8.)  There
is no need to re-enter most of your setup details.

After making clone, rename it to something sensible, switch to it, and then
change anything you want to be different in the new configuration.

Modifying a configuration requires nothing more than changing whatever you
want changed.  The active configuration is saved whenever you terminate the
program.  The next program restart will put you back where you were.

> Note that, when the user has finally found a collection of settings he 
> likes, as currently implemented the configurations feature requires 
> the user to go back to the default settings and then change the 
> settings back to the values he likes, *again*, in order to create the 
> configuration.  For most new users, all this does is break the 
> software, since they likely have not made a list in advance of all the
changes they've made from the default.

If you follow the instructions above, nonw of this is true.

> All of these points discourage the new user from experimenting with, 
> and eventually using, the Configuration feature, which eventually 
> leads to a lot of threads on this reflector that end with someone 
> writing, "Use configurations".
> 
> Anyway, if I'm wrong, and the user email load has not become annoying, 
> well, then, never mind, and I apologize for the bandwidth.  However, 
> if it has become annoying, I have two possible remedies, both leading 
> to increased usage of Configurations over time:
> 
> (1)  Change the UI of the Configurations menu to the more intuitive 
> CREATE / SAVE / EDIT model; or

See above.

&g

Re: [wsjt-devel] Configurations

[Al]

"*One feature I never understood is the "Clone Into" "
Me neither...
But it would make more sense to me if it allowed entering a new name 
thus  "Clone" and "Rename" in one step ( "Clone to new name" ). Sort of 
like "create new using existing settings".


AL, K0VM

*
On 5/19/2020 6:30 PM, Hasan al-Basri wrote:
I use configurations for every mode as well as DXpeditions. They work 
great.


*One feature I never understood is the "Clone Into"*
*
*
I guessed that it might be a simultaneous Clone and Rename, but I've 
never used it.


The way I make new configurations is to start from a known perfectly 
working configuration (in my case FT8).


Start with FT8 Config
Configuration > FT8 > Clone
Cursor to: Configuration > FT8 - Copy
> Rename  (Test for my example)
Configuration > Test > Switch To

Now make all the changes for the configuration you are wanting to 
"save" or "create"the changes are applied immediately without any 
save command. Each change is applied as it is made. e.g. Mode, Radio , 
Audio, etc. etc.


Select the mode and any other settings you want "remembered" in the 
new configuration.


To use the new config: in this example MSK144.

Configuration > MSK144 > Switch To

I have separate configurations for:

FT8
160M JA   (no longer needed)
Default
F+H 9J2LA (Fox and Hound mode with only their known frequencies)
F+H EX0QR (ditto)
F+H TO7DL (ditto)
FT4
FreqCal
MSK144
WSPR

One can add or delete configs as they are no longer useful, as in the 
Fox and Hound DXpeditions shown above.


If there is a better or faster way to do this, let me know and I'll 
write all this up as a simple guide and post it to the main list.


73, N0AN
Hasan


On Tue, May 19, 2020 at 6:08 PM Joe Taylor > wrote:


Hi Ed,

Thanks for your comments, they are much appreciated.  A few comments
inline below.

On 5/19/2020 4:59 PM, j...@comcast.net 
N4II wrote:
> I sense a bit of, er, annoyance on behalf of WSJT-X developers
with the fact
> that relatively few users seem to be using Configurations -- at
least, the
> solution proposed to a fair number of user interface issues
raised here
> recently seems to be the same:  "Use Configurations".
>
> When I first used the software, years ago, I didn't use
configurations for
> three reasons:
>
> (1)  I couldn't find a list anywhere in the manual of just what
"settings"
> were being "configured" (the File/Settings... settings? To
include the main
> window check boxes?  Frequencies?  I still don't know the
complete list,
> even today);

Configurations save all settings that are normally restored after a
program restart, including which of the defined configurations is
currently active.

> (2)  The manual didn't explain that I could avoid a lot of UI
annoyances by
> doing so, just that "[m]any users prefer to create and use
entries on the
> Configurations menu for switching between modes," without saying
why they
> have that preference; and
>
> (3)  The Configurations menu picks didn't seem to do what I
*thought* I
> would want to do to start, which was to CREATE a configuration
for the
> settings I already had, followed by SAVE a configuration.  (I
knew I didn't
> want to CLONE anything . . . .)  If one has the manual at hand,
one has the
> single-sentence instruction to "Simply Clone the Default entry,
Rename it as
> desired, and then make all desired settings for that
configuration."  But
> even then, one has to make an assumption on how the settings are
saved,
> since the manual says nothing about what one has to do to save a
> configuration (change modes or bands?  Switch to a different
configuration?
> Exit the program?).  Without an EDIT menu pick, it's also not at
all clear
> how one might modify a configuration to correct an error, which
makes
> experimenting with the feature a high-risk endeavor for new users.

CLONE is a much better description than CREATE for what happens.  You
should start with a working setup, configured the way you like it for
some mode.  (If the only entry on your Configuration menu is
"Default",
you might want to rename it as, say FT8.  Or Clone it, and rename the
copy to FT8.)  There is no need to re-enter most of your setup
details.

After making clone, rename it to something sensible, switch to it,
and
then change anything you want to be different in the new
configuration.

Modifying a configuration requires nothing more than changing
whatever
you want changed.  The active configuration is saved whenever you
terminate the program.  The next program restart will put you back
where
you were.

> Note that, when the user has finally found a collection of
settings he
> likes, as currently 

Re: [wsjt-devel] Configurations

[Hasan al-Basri]

I use configurations for every mode as well as DXpeditions. They work
great.

*One feature I never understood is the "Clone Into"*

I guessed that it might be a simultaneous Clone and Rename, but I've never
used it.

The way I make new configurations is to start from a known perfectly
working configuration (in my case FT8).

Start with FT8 Config
Configuration > FT8 > Clone
Cursor to: Configuration > FT8 - Copy
> Rename  (Test for my example)
Configuration > Test > Switch To

Now make all the changes for the configuration you are wanting to "save" or
"create"the changes are applied immediately without any save command.
Each change is applied as it is made. e.g. Mode, Radio , Audio, etc. etc.

Select the mode and any other settings you want "remembered" in the new
configuration.

To use the new config: in this example MSK144.

Configuration > MSK144 > Switch To

I have separate configurations for:

FT8
160M JA   (no longer needed)
Default
F+H 9J2LA  (Fox and Hound mode with only their known frequencies)
F+H EX0QR (ditto)
F+H TO7DL (ditto)
FT4
FreqCal
MSK144
WSPR

One can add or delete configs as they are no longer useful, as in the Fox
and Hound DXpeditions shown above.

If there is a better or faster way to do this, let me know and I'll write
all this up as a simple guide and post it to the main list.

73, N0AN

Hasan


On Tue, May 19, 2020 at 6:08 PM Joe Taylor  wrote:

> Hi Ed,
>
> Thanks for your comments, they are much appreciated.  A few comments
> inline below.
>
> On 5/19/2020 4:59 PM, j...@comcast.net N4II wrote:
> > I sense a bit of, er, annoyance on behalf of WSJT-X developers with the
> fact
> > that relatively few users seem to be using Configurations -- at least,
> the
> > solution proposed to a fair number of user interface issues raised here
> > recently seems to be the same:  "Use Configurations".
> >
> > When I first used the software, years ago, I didn't use configurations
> for
> > three reasons:
> >
> > (1)  I couldn't find a list anywhere in the manual of just what
> "settings"
> > were being "configured" (the File/Settings... settings?  To include the
> main
> > window check boxes?  Frequencies?  I still don't know the complete list,
> > even today);
>
> Configurations save all settings that are normally restored after a
> program restart, including which of the defined configurations is
> currently active.
>
> > (2)  The manual didn't explain that I could avoid a lot of UI annoyances
> by
> > doing so, just that "[m]any users prefer to create and use entries on the
> > Configurations menu for switching between modes," without saying why they
> > have that preference; and
> >
> > (3)  The Configurations menu picks didn't seem to do what I *thought* I
> > would want to do to start, which was to CREATE a configuration for the
> > settings I already had, followed by SAVE a configuration.  (I knew I
> didn't
> > want to CLONE anything . . . .)  If one has the manual at hand, one has
> the
> > single-sentence instruction to "Simply Clone the Default entry, Rename
> it as
> > desired, and then make all desired settings for that configuration."  But
> > even then, one has to make an assumption on how the settings are saved,
> > since the manual says nothing about what one has to do to save a
> > configuration (change modes or bands?  Switch to a different
> configuration?
> > Exit the program?).  Without an EDIT menu pick, it's also not at all
> clear
> > how one might modify a configuration to correct an error, which makes
> > experimenting with the feature a high-risk endeavor for new users.
>
> CLONE is a much better description than CREATE for what happens.  You
> should start with a working setup, configured the way you like it for
> some mode.  (If the only entry on your Configuration menu is "Default",
> you might want to rename it as, say FT8.  Or Clone it, and rename the
> copy to FT8.)  There is no need to re-enter most of your setup details.
>
> After making clone, rename it to something sensible, switch to it, and
> then change anything you want to be different in the new configuration.
>
> Modifying a configuration requires nothing more than changing whatever
> you want changed.  The active configuration is saved whenever you
> terminate the program.  The next program restart will put you back where
> you were.
>
> > Note that, when the user has finally found a collection of settings he
> > likes, as currently implemented the configurations feature requires the
> user
> > to go back to the default settings and then change the settings back to
> the
> > values he likes, *again*, in order to create the configuration.  For most
> > new users, all this does is break the software, since they likely have
> not
> > made a list in advance of all the changes they've made from the default.
>
> If you follow the instructions above, nonw of this is true.
>
> > All of these points discourage the new user from experimenting with, and
> > eventually using, the Configuration feature, which 

Re: [wsjt-devel] Configurations

[Joe Taylor]

Hi Ed,

Thanks for your comments, they are much appreciated.  A few comments 
inline below.


On 5/19/2020 4:59 PM, j...@comcast.net N4II wrote:

I sense a bit of, er, annoyance on behalf of WSJT-X developers with the fact
that relatively few users seem to be using Configurations -- at least, the
solution proposed to a fair number of user interface issues raised here
recently seems to be the same:  "Use Configurations".

When I first used the software, years ago, I didn't use configurations for
three reasons:

(1)  I couldn't find a list anywhere in the manual of just what "settings"
were being "configured" (the File/Settings... settings?  To include the main
window check boxes?  Frequencies?  I still don't know the complete list,
even today);


Configurations save all settings that are normally restored after a 
program restart, including which of the defined configurations is 
currently active.



(2)  The manual didn't explain that I could avoid a lot of UI annoyances by
doing so, just that "[m]any users prefer to create and use entries on the
Configurations menu for switching between modes," without saying why they
have that preference; and

(3)  The Configurations menu picks didn't seem to do what I *thought* I
would want to do to start, which was to CREATE a configuration for the
settings I already had, followed by SAVE a configuration.  (I knew I didn't
want to CLONE anything . . . .)  If one has the manual at hand, one has the
single-sentence instruction to "Simply Clone the Default entry, Rename it as
desired, and then make all desired settings for that configuration."  But
even then, one has to make an assumption on how the settings are saved,
since the manual says nothing about what one has to do to save a
configuration (change modes or bands?  Switch to a different configuration?
Exit the program?).  Without an EDIT menu pick, it's also not at all clear
how one might modify a configuration to correct an error, which makes
experimenting with the feature a high-risk endeavor for new users.


CLONE is a much better description than CREATE for what happens.  You 
should start with a working setup, configured the way you like it for 
some mode.  (If the only entry on your Configuration menu is "Default", 
you might want to rename it as, say FT8.  Or Clone it, and rename the 
copy to FT8.)  There is no need to re-enter most of your setup details.


After making clone, rename it to something sensible, switch to it, and 
then change anything you want to be different in the new configuration.


Modifying a configuration requires nothing more than changing whatever 
you want changed.  The active configuration is saved whenever you 
terminate the program.  The next program restart will put you back where 
you were.



Note that, when the user has finally found a collection of settings he
likes, as currently implemented the configurations feature requires the user
to go back to the default settings and then change the settings back to the
values he likes, *again*, in order to create the configuration.  For most
new users, all this does is break the software, since they likely have not
made a list in advance of all the changes they've made from the default.


If you follow the instructions above, nonw of this is true.


All of these points discourage the new user from experimenting with, and
eventually using, the Configuration feature, which eventually leads to a lot
of threads on this reflector that end with someone writing, "Use
configurations".

Anyway, if I'm wrong, and the user email load has not become annoying, well,
then, never mind, and I apologize for the bandwidth.  However, if it has
become annoying, I have two possible remedies, both leading to increased
usage of Configurations over time:

(1)  Change the UI of the Configurations menu to the more intuitive CREATE /
SAVE / EDIT model; or


See above.


(2)  Add a few sentences to the WSJT-X documentation, at least describing
the benefits of using Configurations; how changes are saved; the importance
of using Configurations/Default/Clone **before** changing settings; what
functions the "Clone Into . . ." and "Reset" undocumented menu picks
perform; and providing a list of the parameters controlled by the
Configurations feature.


We'll try to make the User Guide instructions more detailed and more 
specific.


-- Joe, K1JT



___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] Configurations

[jan0]

I sense a bit of, er, annoyance on behalf of WSJT-X developers with the fact
that relatively few users seem to be using Configurations -- at least, the
solution proposed to a fair number of user interface issues raised here
recently seems to be the same:  "Use Configurations".

When I first used the software, years ago, I didn't use configurations for
three reasons:  

(1)  I couldn't find a list anywhere in the manual of just what "settings"
were being "configured" (the File/Settings... settings?  To include the main
window check boxes?  Frequencies?  I still don't know the complete list,
even today); 

(2)  The manual didn't explain that I could avoid a lot of UI annoyances by
doing so, just that "[m]any users prefer to create and use entries on the
Configurations menu for switching between modes," without saying why they
have that preference; and 

(3)  The Configurations menu picks didn't seem to do what I *thought* I
would want to do to start, which was to CREATE a configuration for the
settings I already had, followed by SAVE a configuration.  (I knew I didn't
want to CLONE anything . . . .)  If one has the manual at hand, one has the
single-sentence instruction to "Simply Clone the Default entry, Rename it as
desired, and then make all desired settings for that configuration."  But
even then, one has to make an assumption on how the settings are saved,
since the manual says nothing about what one has to do to save a
configuration (change modes or bands?  Switch to a different configuration?
Exit the program?).  Without an EDIT menu pick, it's also not at all clear
how one might modify a configuration to correct an error, which makes
experimenting with the feature a high-risk endeavor for new users.  

Note that, when the user has finally found a collection of settings he
likes, as currently implemented the configurations feature requires the user
to go back to the default settings and then change the settings back to the
values he likes, *again*, in order to create the configuration.  For most
new users, all this does is break the software, since they likely have not
made a list in advance of all the changes they've made from the default.  

All of these points discourage the new user from experimenting with, and
eventually using, the Configuration feature, which eventually leads to a lot
of threads on this reflector that end with someone writing, "Use
configurations".

Anyway, if I'm wrong, and the user email load has not become annoying, well,
then, never mind, and I apologize for the bandwidth.  However, if it has
become annoying, I have two possible remedies, both leading to increased
usage of Configurations over time:

(1)  Change the UI of the Configurations menu to the more intuitive CREATE /
SAVE / EDIT model; or

(2)  Add a few sentences to the WSJT-X documentation, at least describing
the benefits of using Configurations; how changes are saved; the importance
of using Configurations/Default/Clone **before** changing settings; what
functions the "Clone Into . . ." and "Reset" undocumented menu picks
perform; and providing a list of the parameters controlled by the
Configurations feature.

73,

Ed Callaway, N4II.

-Original Message-
From: Reino Talarmo  
Sent: Tuesday, May 19, 2020 2:04 PM
To: k...@arrl.net; 'WSJT software development'

Subject: Re: [wsjt-devel] Hold TX Frequency Default

>From: Jim Brown [mailto:k...@audiosystemsgroup.com] 
Sent: 19. toukokuuta 2020 20:25

>On 5/19/2020 6:35 AM, Joe Taylor wrote:
>> I operate on 6m a lot, using FT8, MSK144, and recently also FT4.  I 
> >never have the problem you describe.

>Can you please tell me how your setup prevents the problem I've described?
Is there a reason that you cannot >change the behavior I've described?

Jim,
>From User Guide: " Simply Clone the Default entry, Rename it as desired, and
then make all desired settings for that configuration. These settings will
be restored whenever you select that configuration. "
Each configuration behaves as if you have never used any other mode and so
none of the mode dependent defaults will not affect to other configurations.
It should implement your wish and need, just in another fully working
manner. 

73, Reino OH3mA


___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel



___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel



___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Configurations

[Charles Suckling]

Thanks, Bill


-Original Message-
From: Bill Somerville [mailto:g4...@classdesign.com] 
Sent: 12 September 2017 19:27
To: wsjt-devel@lists.sourceforge.net
Subject: Re: [wsjt-devel] Configurations

On 12/09/2017 17:51, char...@sucklingfamily.free-online.co.uk wrote:
> Is there any limit on the number of configurations that can be stored?

Hi Charlie,

not really but managing the list on screen will become unwieldy after a 
hundred or so.

73
Bill
G4WJS.



--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Configurations

[Bill Somerville]

On 12/09/2017 17:51, char...@sucklingfamily.free-online.co.uk wrote:

Is there any limit on the number of configurations that can be stored?


Hi Charlie,

not really but managing the list on screen will become unwieldy after a 
hundred or so.


73
Bill
G4WJS.


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Configurations

[Gary McDuffie]

> On Sep 12, 2017, at 10:51 AM, char...@sucklingfamily.free-online.co.uk wrote:
> 
> Is there any limit on the number of configurations that can be stored?

I don’t know the answer to that, but I’ve had as many as 15 with no problem.  
I’m down to a dozen now.  Once I learned to use Configurations, it was quite 
simple to experiment with different settings without screwing up my normal ones.

73, Gary - AG0N
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] Configurations

[charlie]

Hi Bill

Is there any limit on the number of configurations that can be stored?

73

Charlie


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] configurations

[Alessandro Gorobey]

Hi Bill,

r6660 work

Thanks!!!

Il 01/05/2016 01:25, Bill Somerville ha scritto:
> On 30/04/2016 23:20, Steven Franke wrote:
>> Playing with configurations a little bit here. When I switch configurations 
>> I see a flurry of errors that look like this:
>>
>> Hamlib:  kenwood_transaction: Retrying shortly
>> Hamlib:  kenwood_transaction: Unknown command or rig busy
>>
>> followed by two of these:
>> Hamlib:  serial_setup: tcsetattr failed: Input/output error
>
> Hi Steve, Sandro & all,
>
> this defect should be repaired by r6660.
>
> 73
> Bill
> G4WJS.
>
>
> --
> Find and fix application performance issues faster with Applications Manager
> Applications Manager provides deep performance insights into multiple tiers of
> your business applications. It resolves application problems quickly and
> reduces your MTTR. Get your free trial!
> https://ad.doubleclick.net/ddm/clk/302982198;130105516;z
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>

-- 
73
Sandro
IW3RAB

--
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial!
https://ad.doubleclick.net/ddm/clk/302982198;130105516;z
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] configurations

[Bill Somerville]

On 01/05/2016 00:31, Steven Franke wrote:

this defect should be repaired by r6660.

Confirmed!


Hi Steve & all,

fixing this reminds me that we have many cases where a static variable 
has been used where a class instance variable is what is needed. These 
are all potential defects when switching configurations if they are used 
as one-time initialization flags. I am working through all the statics 
and will have a fix later that hopefully squashes a number of latent 
defects.


73
Bill
G4WJS.

--
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial!
https://ad.doubleclick.net/ddm/clk/302982198;130105516;z___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] configurations

[Steven Franke]

> Hi Steve, Sandro & all,
> 
> this defect should be repaired by r6660.

Confirmed! Thanks Bill,
Steve k9an

> 
> 73
> Bill
> G4WJS.
> 
> 
> --
> Find and fix application performance issues faster with Applications Manager
> Applications Manager provides deep performance insights into multiple tiers of
> your business applications. It resolves application problems quickly and
> reduces your MTTR. Get your free trial!
> https://ad.doubleclick.net/ddm/clk/302982198;130105516;z
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel


--
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial!
https://ad.doubleclick.net/ddm/clk/302982198;130105516;z
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] configurations

[Bill Somerville]

On 30/04/2016 23:20, Steven Franke wrote:
> Playing with configurations a little bit here. When I switch configurations I 
> see a flurry of errors that look like this:
>
> Hamlib:  kenwood_transaction: Retrying shortly
> Hamlib:  kenwood_transaction: Unknown command or rig busy
>
> followed by two of these:
> Hamlib:  serial_setup: tcsetattr failed: Input/output error

Hi Steve, Sandro & all,

this defect should be repaired by r6660.

73
Bill
G4WJS.


--
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial!
https://ad.doubleclick.net/ddm/clk/302982198;130105516;z
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] configurations

[Bill Somerville]

On 30/04/2016 23:20, Steven Franke wrote:
> Playing with configurations a little bit here. When I switch configurations I 
> see a flurry of errors that look like this:
>
> Hamlib:  kenwood_transaction: Retrying shortly
> Hamlib:  kenwood_transaction: Unknown command or rig busy
>
> followed by two of these:
> Hamlib:  serial_setup: tcsetattr failed: Input/output error
>
> The end result is that I get the Rig Control Error box, and I have to 
> re-enter the CAT control port each time.

Hi Steve & all,

I have not worked out why this is going wrong yet but to work around 
this for now if you quit and restart WSJT-X immediately after switching 
to a new configuration it should work as intended.

73
Bill
G4WJS.


--
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial!
https://ad.doubleclick.net/ddm/clk/302982198;130105516;z
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] configurations

[Bill Somerville]

On 30/04/2016 23:20, Steven Franke wrote:
> The end result is that I get the Rig Control Error box, and I have to 
> re-enter the CAT control port each time.

Hi Steve,

this seems to be related to the issue that Sandro has. Somehow the CAT 
serial COM port is not being copied correctly when a configuration is 
cloned. I'll have a look now and see what is going on.

73
Bill
G4WJS.


--
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial!
https://ad.doubleclick.net/ddm/clk/302982198;130105516;z
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] configurations

[Steven Franke]

Hi Bill - 

Playing with configurations a little bit here. When I switch configurations I 
see a flurry of errors that look like this:

Hamlib:  kenwood_transaction: Retrying shortly
Hamlib:  kenwood_transaction: Unknown command or rig busy

followed by two of these:
Hamlib:  serial_setup: tcsetattr failed: Input/output error

The end result is that I get the Rig Control Error box, and I have to re-enter 
the CAT control port each time.

This is with the latest hamlib from your repository and the latest wsjt-x 
(r6659).

Steve k9an
--
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial!
https://ad.doubleclick.net/ddm/clk/302982198;130105516;z
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel