Re: [wsjt-devel] Spanish translation

Hi Borja, On 12/31/2015 4:46 AM, ea2...@gmail.com wrote: > While getting acquainted with the project sources, there is a > contribution I can make, translating the manual to Spanish. > Has it ever been considered? > > 73, > Borja EA2EKH In general we have been delighted to have translations of

[wsjt-devel] Spanish translation

Hello, While getting acquainted with the project sources, there is a contribution I can make, translating the manual to Spanish. Has it ever been considered? 73, Borja EA2EKH --

Re: [wsjt-devel] QT55

On 31/12/2015 16:14, Michael Black wrote: > Any thought to letting 1.7.0 be QT 5.5? > Is there a technical reason not to? > I've been running it here and all seems well on Windows 10. > Anybody else using it on another OS? Hi Mike, the official WSJT-X v1.6.0 for Windows & OS X is already

Re: [wsjt-devel] QT55

On 31/12/2015 16:42, Michael Black wrote: > Is it possible to put something similar to #ifdef in the ui code? Hi Mike, not that I'm aware of but the uic generated code is build against whatever version of Qt & C++ being used. The only advantage of such a construct I could think of would be

Re: [wsjt-devel] QT55

I'm currently using some sounds for different events (Transmitting, Watchdog alarm, and Rx Frequency message not addressed to my call). I've found them quite useful. For example when monitoring an offset I can have other windows in front and WSJT-X tells me when a message comes in on the

Re: [wsjt-devel] QT55

On 31/12/2015 17:17, Bill Somerville wrote: > On 31/12/2015 16:54, Michael Black wrote: >> Wanted to add an audio card checkbox & chooser and was going to use >> QT55 ability to do so on the audio chooser. > Hi Mike, > > it is possible to add widgets to the existing layouts from code so you >

[wsjt-devel] QT55

Any thought to letting 1.7.0 be QT 5.5? Is there a technical reason not to? I've been running it here and all seems well on Windows 10. Anybody else using it on another OS? 73 Mike W9MDB --

Re: [wsjt-devel] QT55

Is it possible to put something similar to #ifdef in the ui code? RRR Mike W9MDB On Thu, Dec 31, 2015 at 10:32 AM, Bill Somerville wrote: > On 31/12/2015 16:14, Michael Black wrote: > > Any thought to letting 1.7.0 be QT 5.5? > > Is there a technical reason not to? > >

Re: [wsjt-devel] QT55

On 31/12/2015 16:54, Michael Black wrote: > Wanted to add an audio card checkbox & chooser and was going to use > QT55 ability to do so on the audio chooser. Hi Mike, it is possible to add widgets to the existing layouts from code so you don't necessarily have to have the whole UI designed in

Re: [wsjt-devel] Spanish translation

> On 31 Dec 2015, at 15:27, Joe Taylor wrote: > > Hi Borja, > > > If these starting points present no serious obstacles for you, we here > on the email list will happy to help you get started! Ewword would be a problem, but a markup such as this one or LaTeX is not

Re: [wsjt-devel] JT65 decoder status

On 12/31/2015 1:09 PM, Guy G4DWV/4X1LT wrote: > Joe Taylor writes: > > > >> Normal operation at HF should set "Aggressive decoding level" to 0. >> If you try operating on HF with higher values, be sure to set Ftol=1000. >>With higher values of Aggressive decoding level you will

Re: [wsjt-devel] JT65 decoder status

On 31/12/2015 19:21, Joe Taylor wrote: > Set Mode to JT65 (not JT9+JT65). The Ftol widget is then made visible. You will need to check "Enable VHF/UHF Features" in "Settings->General" as well. 73 Bill G4WJS. --

Re: [wsjt-devel] JT65 decoder status

Hi Steve and all, In case you have built WSJT-X v1.7 from r6329 and used it on the HF bands, you'll surely see many more false decodes than usual. As committed, the code uses aggressive values for the parameters d_0 and r_0. These values may be appropriate for EME-like conditions, but

Re: [wsjt-devel] Spanish translation

> On 31 Dec 2015, at 15:53, Bill Somerville wrote: > > > I would suggest, for now, copying the whole content of the > ^/branches/wsjtx/doc/user_guide/ directory including the images. It > might be worthwhile for technical reasons to move the current sources > down one

Re: [wsjt-devel] JT65 decoder status

Joe Taylor writes: > Normal operation at HF should set "Aggressive decoding level" to 0. > If you try operating on HF with higher values, be sure to set Ftol=1000. > With higher values of Aggressive decoding level you will see a few > more decodes, and also some false decodes.

Re: [wsjt-devel] JT65 decoder status

On 31/12/2015 22:04, Michael Black wrote: > It seems as though once aggressive decoding is turned on you can't > decode JT65 with JT9 any more. All you get is JT9 decodes in the > combo mode. Hi Mike, for now that is not unreasonable. Aggressive decoding is intended for VHF & up where you

Re: [wsjt-devel] JT65 decoder status

On 31/12/2015 22:32, Michael Black wrote: > The it's backwardsif you're only supposed to do JT65 with > aggressivebut all you can receive is JT9. > > I kind of thought Joe's point was to allow some aggressive decoding on HF. You can try out the JT65 decoder in aggressive mode on HF if

Re: [wsjt-devel] JT65 decoder status

The it's backwardsif you're only supposed to do JT65 with aggressivebut all you can receive is JT9. I kind of thought Joe's point was to allow some aggressive decoding on HF. RRR Mike W9MDB On Thu, Dec 31, 2015 at 4:18 PM, Bill Somerville wrote: > On 31/12/2015

Re: [wsjt-devel] JT65 decoder status

It seems as though once aggressive decoding is turned on you can't decode JT65 with JT9 any more. All you get is JT9 decodes in the combo mode. RRR Mike W9MDB On Thu, Dec 31, 2015 at 1:42 PM, Bill Somerville wrote: > On 31/12/2015 19:21, Joe Taylor wrote: > > Set Mode

Re: [wsjt-devel] JT65 decoder status

Confirmed here. Aggressive decodes set to "1", FTol 1000. Returning Aggressive setting to "0" restores function. 6330 under Mac OS X 10.11.3 Geo/KF2T -- Original Message -- From: "Michael Black" To: "WSJT software development"

Re: [wsjt-devel] JT65 decoder status

On 31/12/2015 23:09, Michael Black wrote: > OKcapeeshbut does that mean mode should be forced to JT65 and > combo mode disabled? Perhaps with a dialog box to 'splain things? Hi Mike, until it is decided if the aggressive mode is of any use on HF, no. If it is not useful i.e. creates

Re: [wsjt-devel] JT65 decoder status

OKcapeeshbut does that mean mode should be forced to JT65 and combo mode disabled? Perhaps with a dialog box to 'splain things? RRR Mike W9MDB On Thu, Dec 31, 2015 at 4:51 PM, Bill Somerville wrote: > On 31/12/2015 22:32, Michael Black wrote: > > The it's