"Better" is always better J -- Especially when you can satisfy everybody's
needs.  

I remember now you saying about the tab knowledge before and I seem to
remember trying to follow the logic in the code as to why that was.but never
satisfied myself.  I wasn't able to see how the client request actually got
processed.

 

73

Mike W9MDB

 

 

From: Bill Somerville [mailto:[email protected]] 
Sent: Monday, July 27, 2015 5:22 AM
To: [email protected]
Subject: Re: [wsjt-devel] Request: UDP change to Free-Text command

 

On 27/07/2015 10:59, Michael Black wrote:
Hi Mike,

The real solution to this is a tri-state meaning of the flag for this.
Right now it's Boolean.  So make it an int and -1,0,1  -- 0 and 1 have the
current meaning, and -1 means don't activate (which is the same as 0 for Tab
2 also).

Then the user can select the typical action they want from the client.  This
really needs to be a user choice.

That is not a good solution as we have discussed in the past, the problem
with it is that it requires knowledge of which of tab one and tab two is
active.

I think I have a better solution, which I am testing right now, and I will
post something soon.



 

73

Mike W9MDB

73
Bill
G4WJS.



 

From: Laurie VK3AMA [mailto:[email protected]] 
Sent: Monday, July 27, 2015 2:07 AM
To: [email protected]
Subject: [wsjt-devel] Request: UDP change to Free-Text command

 

I have a need for the UDP Free-Text command to NOT enable the "Next" Radio
Button on TAB1. Myself and several others often queue a message into the
future, not for the next minute.

As currently implemented the UDP Free-Text command ALWAYS enables that radio
button on TAB1 despite the setting of the "Send" boolean value. On TAB2, the
radio button activation obeys the "Send" flag. I know the radio buttons
behave differently on the Tabs and that the "Send" flag may not be
appropriate, but could be used as it is only used by Tab2.

Bottom-line, I need the ability set or not set the radio button when sending
free-text on Tab1.

Thanks.
de Laurie, VK3AMA

 

------------------------------------------------------------------------------
_______________________________________________
wsjt-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Reply via email to