Re: [wsjt-devel] 1.9 RC2 - UI Suggestion

; > comments in line below. > > > On 26/02/2018 21:47, Phil Frost wrote: > > On Mon, Feb 26, 2018 at 9:12 PM Bill Somerville <g4...@classdesign.com> > wrote: > >> BTW this is not our design but standard Qt widget behaviour, which is >> consistent with re

Re: [wsjt-devel] 1.9 RC2 - UI Suggestion

On Mon, Feb 26, 2018 at 9:12 PM Bill Somerville wrote: > BTW this is not our design but standard Qt widget behaviour, which is > consistent with recognized "standard" GUI design principles. > While the double- and triple-click semantics are typical, I'd call including the

Re: [wsjt-devel] bug report: hamlib failure when trying to get mode

On Wed, Feb 8, 2017 at 9:24 AM Bill Somerville wrote: > When the last process closes it should release and destroy the shared > memory section, this can go wrong and leave a stale shared memory section > hanging around. > I've noticed issues with wsjtx instances hanging

Re: [wsjt-devel] bug report: hamlib failure when trying to get mode

On Wed, Feb 1, 2017 at 1:27 PM Bill Somerville <g4...@classdesign.com> wrote: > On 01/02/2017 18:07, Phil Frost wrote: > > I'm using the "Hamlib NET" driver, and it's running and working enough > > for fldigi and direct testing with telnet. Unfortunately, in

[wsjt-devel] Debian source package?

I notice the source has a debian/directory, but not debian/control. I'd like to make a custom build and I figure this is the quickest way to a working build. It seems there's already some process in place for building Debian packages; who maintains that or where can I find it?

Re: [wsjt-devel] bug report: hamlib failure when trying to get mode

I'm on Ubuntu 15.10 64-bit (yeah...been meaning to upgrade), but if enabling the instrumentation is just a configure flag or similar I can build from source. On Wed, Feb 1, 2017 at 1:27 PM Bill Somerville <g4...@classdesign.com> wrote: > On 01/02/2017 18:07, Phil Frost wrote: >