[wsjt-devel] Double click on call behavior

2018-05-18 Thread Black Michael via wsjt-devel
#1 Hold Tx is off, double-click on a msg that does NOT have your call sign and both Tx/Rx offsets jump to the target.#2 Hold Tx is off, double-click on a msg that DOES have your call sign and only Rx offset changes. This seems backwards. Is there some logic here I'm not seeing? What's the intent?

Re: [wsjt-devel] PSKReporter and non-standard CQ messages

2018-05-18 Thread Bill Somerville
Hi Philip, the messages that normally have grids are CQ calls, replies to CQ calls, and QRZ messages. That accounts for roughly 33% of all messages. If we sent spots for all of those instead of just those with grid squares then the overall increase would be quite small as most of them already

Re: [wsjt-devel] PSKReporter and non-standard CQ messages

2018-05-18 Thread Joe Taylor
Hi Al and all, On 5/18/2018 11:21 AM, Al Pawlowski K6AVP wrote: Why not make the FT/JT messages a bit longer to accommodate the compound calls? If a longer tx/rx cycle time would be needed for FT8 - up to 30s would be fine by me. It would be nice to have enough time to manually initiate a deco

Re: [wsjt-devel] Bug or feature?

2018-05-18 Thread Saku
Thanks Joe ! I'm always a bit behind Good work ! -- Saku OH1KH Joe Taylor kirjoitti 18.05.2018 klo 18:41: Hi Saku, I think we may call it a bug. In r8665 I've made Ctrl+F11 and Ctrl+F12 change the Tx freq only when equal to Rx Freq, and the list of Keyboard Shortcuts has been changed acco

Re: [wsjt-devel] Bug or feature?

2018-05-18 Thread Joe Taylor
Hi Saku, I think we may call it a bug. In r8665 I've made Ctrl+F11 and Ctrl+F12 change the Tx freq only when equal to Rx Freq, and the list of Keyboard Shortcuts has been changed accordingly. These keyboard commands override the setting of "Hold TX freq", which seems OK to me. --Jo

Re: [wsjt-devel] PSKReporter and non-standard CQ messages

2018-05-18 Thread Al Pawlowski
Why not make the FT/JT messages a bit longer to accommodate the compound calls? If a longer tx/rx cycle time would be needed for FT8 - up to 30s would be fine by me. It would be nice to have enough time to manually initiate a decodable CQ answer. If a longer cycle time or message improved dec

[wsjt-devel] Bug or feature?

2018-05-18 Thread Saku
Hi ! Wsjt-x  1.9.0-rc4 r8662 TX =461Hz (not specific, any split QRG will do) Hold TX freq = checked Auto Seq = any Call 1st  = any RX = 2296Hz (not specific, any split QRG will do) Settings/general/Allow frequency changes while transmitting = checked Settings/Radio/Split operation = rig Rig = I

Re: [wsjt-devel] PSKReporter and non-standard CQ messages

2018-05-18 Thread Philip Gladstone
I already get a bunch of spots (from other modes) without locators. This will just encourage me to allow people to enter grids on pskreporter. I'm already think that I have to deal with the /B calls and just use the locator of the base callsign. Do you really think that this would be a big inc

Re: [wsjt-devel] PSKReporter and non-standard CQ messages

2018-05-18 Thread Black Michael via wsjt-devel
I don't think it's the location that is important but the "who's seeing me" which doesn't care about your location.  You just can't draw the traces without it.This should only be done for CQ messages so very little traffic increase.Philip probably maintains the last grid reported for a call sign

Re: [wsjt-devel] PSKReporter and non-standard CQ messages

2018-05-18 Thread Bill Somerville
On 18/05/2018 03:43, Philip Gladstone wrote: I've been contacted by a few people with compound callsigns whose transmissions are never reported to PSKReporter. I took a quick look at the WSJT-X code and it appears that the CQ is only reported if there is both a callsign *and* a grid. I suspect