Hi Neil,
See below
On 06/28/2016 07:16 PM, Neil Zampella wrote:
> Bill,
>
> Had just reloaded Windows 8 on my laptop as the hard disk was starting
> to fail, and installed a new hard drive. Had just reloaded JTSDK from
> scratch, using all the updates, etc.
>
> Michael - I enabled qt55 after
Hi Jeff,
I missed the beginning of this thread, sorry. I am assuming this is
Linux, how did you install JTSDK?
The Nix installation, via the launchpad PPA / meta package(s) should
have installed libqt5multimedia5-plugins, as it is listed in the Debian
control file for jtsdk-minimal, standard and
> Date: Tue, 28 Jun 2016 15:26:30 +0100
> From: Bill Somerville
> Subject: Re: [wsjt-devel] No Audio Options in Dropdown
> To: wsjt-devel@lists.sourceforge.net
> Message-ID:
> Content-Type: text/plain; charset=windows-1252; format=flowed
>
> On 28/06/2016 15:13, Jeff Connelly wrote:
>> I'm getti
On 29/06/2016 7:09 AM, Bill Somerville wrote:
Hi Laurie,
Mike sent me a pre release v2.7.7 so I could replicate the issue, it
turned out that WSJT-X crashed if the Message field (decoded text) of
the UDP Reply message was empty. This happens when a non-general call
alert is double clicked in
Bill,
Had just reloaded Windows 8 on my laptop as the hard disk was starting
to fail, and installed a new hard drive. Had just reloaded JTSDK from
scratch, using all the updates, etc.
Michael - I enabled qt55 after everything was installed, and since it
was a complete reload the directories
On 28/06/2016 21:53, Laurie VK3AMA wrote:
> What is this "small JTAlert defect"?
Hi Laurie,
Mike sent me a pre release v2.7.7 so I could replicate the issue, it
turned out that WSJT-X crashed if the Message field (decoded text) of
the UDP Reply message was empty. This happens when a non-general
On 29/06/2016 1:56 AM, Bill Somerville wrote:
>
> this was a small JTAlert defect in an as yet unreleased version
> combined with a defect in WSJT-X. The WSJT-X defect has been repaired
> as of r6812 so the crash will no longer occur.
>
> Thanks for reporting this and helping with diagnosing it
On 28/06/2016 05:34, Black Michael wrote:
Using r6810. If you click a non-CQ call slot in JTAlert WSJT-X dies
with a segfault.
Apparently doesn't like parsing a non CQ message.
Hi Mike & all,
this was a small JTAlert defect in an as yet unreleased version combined
with a defect in WSJT-X. T
On 28/06/2016 15:13, Jeff Connelly wrote:
> I'm getting a weird issue with a build of the latest dev version of
> WSJTX.
> Compiling and running work fine, but when it launches I get 4 popup
> audio warnings and there are no options available in the audio
> dropdowns. I'm used to the audio warnings
Hi,
I'm getting a weird issue with a build of the latest dev version of
WSJTX.
Compiling and running work fine, but when it launches I get 4 popup
audio warnings and there are no options available in the audio
dropdowns. I'm used to the audio warnings when the devices aren't set
properly, but i
HI Mike,
comments in line below.
On 28/06/2016 13:00, Black Michael wrote:
Any call slot that isn't from a CQ message. So the reply will be a
non-CQ message.
I'm using a beta version of JTAlert right now but I don't think that
matters except for the fact that you can click on any call slot n
Any call slot that isn't from a CQ message. So the reply will be a non-CQ
message.I'm using a beta version of JTAlert right now but I don't think that
matters except for the fact that you can click on any call slot now which I
don't think you could do at 2.7.5.
I tried to find the segfault usi
On 28/06/2016 05:34, Black Michael wrote:
Using r6810. If you click a non-CQ call slot in JTAlert WSJT-X dies
with a segfault.
Apparently doesn't like parsing a non CQ message.
Hi Mike,
I have not yet been able to reproduce this. Which version of JTAlert are
you using? Can you reproduce the
13 matches
Mail list logo
