Date   

Re: QRZ Lookup

Damian M0BKV
 

Same here. QRZ.com bug I believe


Re: QRZ Lookup

Steph, F5NZY
 

Don't worry John,

I've got the same thing here. Probably a small bug from QRZ.COM that will be quickly fixed, I'm sure.

73 de Steph, F5NZY

Le 15/07/2020 à 15:59, John a écrit :

After years of using Logger16 and logger32, I actually have a problem.

 

Starting this morning, the “ NAME “ no longer transfers from qrz.com.

 

Any ideas ??

 

John

WB9PNU

 

 


Virus-free. www.avg.com
-- 
Everything looks impossible to the people who never tried anything.
(Dr J-L Etienne)


QRZ Lookup

John
 

After years of using Logger16 and logger32, I actually have a problem.

 

Starting this morning, the “ NAME “ no longer transfers from qrz.com.

 

Any ideas ??

 

John

WB9PNU

 

 


Virus-free. www.avg.com


Logger32

Tom Wylie
 

Hi Bob

Are there any plans to introduce TCI - Transceiver Control Interface

into Logger 32 - anytime soon or anytime at all?

Tom
GM4FDM


Unanswered emails....

Rick Ellison
 

If any of the users of my software have sent me an email to either rellison@... or n2amg@... since January 1st 2020 and you did not get a reply, I more than likely did not get your email. Tonight my mail provider dumped over 5000 emails on me that I am not sure that I have read or not. I just deleted all of the new emails instead of going thru them. Please send your questions or issues to me again if you did not get a reply from me...

 

73 Rick N2AMG


Virus-free. www.avast.com


Scratchpad - geature request..

Vince Shirley
 

Probably the wrong time to ask for this with V4 on the horizon, however, I'll go for it anyway.

At the moment scratchpad shows QSO time.

I find it very useful for accumulating DX spots for my yearly needed entities list via the "Setup DX Spot Alert Menu".  A handy feature would be for the scratchpad to show the time of the DX spot, in order to eliminate those that have expired.

Just a thought...

Vince, drinking his way through the now semi-lockdown. the Rosebank (https://rosebank.com/) going down well...


Re: A status report ...

F4FQH Olivier
 

Aki thanks for the info, will see Jim.
 
73
Olivier
F4FQH
 
 

From: ja1nlx
Sent: Tuesday, July 14, 2020 3:12 AM
To: hamlogger@groups.io
Subject: Re: [hamlogger] A status report ...
 

Oliver

Ask Jim W5IFP to join L32Test group. L32Test group is dedicated for testing ver4.0.

73

On 2020/07/14 9:51, F4FQH Olivier wrote:
Hi Bob
 
Where could i find the V4 ?
 
Tks
Olivier
F4FQH
 
From: Bob
Sent: Monday, July 13, 2020 9:33 PM
To: hamlogger@groups.io
Subject: [hamlogger] A status report ...
 
Just to update you on the ver 4.0 testing so far ... At the moment we've run out of ver 4.0 bugs. As added incentive to the testers (thanks to all) I have offered free maintenance for a year to any/all who find the next 4.0 bug. And, if it is a really interesting bug, the actual upgrade from 3.5 to 4.0 is offered free.

As a reminder, the primary objectives of 4.0 were to increase the maximum logbook capacity to 1M+ QSOs and to replace the original Microsoft serial port control.
 
Also, just to keep the party exciting, I have finished a little FT4/FT8 add-on ...

It can change JTDX Bands/Modes, and take FT4/FT8 DX Spots and feed them directly into JTDX. Looking at the picture, you can see that JTDX is on 20M/FT4. The developers of JTDX and WSJT have shown little/no interest in opening their external interface to logging programs.  So testing of the Control Panel has been difficult. It works, but not reliably enough to publicly release.
 
So, what we need is for a competent Python savvy programmer to step up and make some simple changes to the JTDX code to allow exchange of messages with Logger32. A word of caution - This is not for the faint hearted. While the actual changes are simple, all the GNU/GPL/BLAH/BLAH rules/regulations/guidelines need to be complied with, and the pay is lousy.
 
We really do need someone to help out. Thanks, 73.
--
73 de aki
JA1NLX


Re: Scratchpad......

Bob
 

Is it possible that the scratchpad option CLOSE SCRATCHPAD WHEN EMPTY is enabled. If it is, attempting to open the scratchpad with an empty callsign field in the logbook entry window will not be overly productive. SeventyThree(s).

On 07/14/2020 4:41 PM Bob <k4cy@...> wrote:


If you right click on the callsign field of the logbook entry window, then click the MOVE LOG ENTRY TO SCRATCHPAD menu does the little bugger come out of hiding? SeventyThree(s).
On 07/14/2020 4:31 PM Vince Shirley <vince.g0orc@...> wrote:


Hi all,

For some reason CTRL-Z is not opening the scratchpad.  Its not underneath anything else and it's not in the list of "lost windows"

Is it me?

Vince G0ORC


Re: Scratchpad......

Bob
 

If you right click on the callsign field of the logbook entry window, then click the MOVE LOG ENTRY TO SCRATCHPAD menu does the little bugger come out of hiding? SeventyThree(s).

On 07/14/2020 4:31 PM Vince Shirley <vince.g0orc@...> wrote:


Hi all,

For some reason CTRL-Z is not opening the scratchpad.  Its not underneath anything else and it's not in the list of "lost windows"

Is it me?

Vince G0ORC


Scratchpad......

Vince Shirley
 

Hi all,

For some reason CTRL-Z is not opening the scratchpad.  Its not underneath anything else and it's not in the list of "lost windows"

Is it me?

Vince G0ORC


Re: A status report ...

kenfilmer@outlook.com
 

For Jim, W5IFP

 

Jim

 

If you need any more bodies to test V4 I will be happy to do so in order to pay something back for many years use of an excellent logging programme.

 

However you need to know that my computer skills are not up there in the higher echelons!

 

73

 

Ken

G3XPO

 

Sent from Mail for Windows 10

 


From: hamlogger@groups.io <hamlogger@groups.io> on behalf of ja1nlx <ayoshida0205@...>
Sent: Tuesday, July 14, 2020 2:12:21 AM
To: hamlogger@groups.io <hamlogger@groups.io>
Subject: Re: [hamlogger] A status report ...
 

Oliver

Ask Jim W5IFP to join L32Test group. L32Test group is dedicated for testing ver4.0.

73

On 2020/07/14 9:51, F4FQH Olivier wrote:
Hi Bob
 
Where could i find the V4 ?
 
Tks
Olivier
F4FQH
 
From: Bob
Sent: Monday, July 13, 2020 9:33 PM
To: hamlogger@groups.io
Subject: [hamlogger] A status report ...
 
Just to update you on the ver 4.0 testing so far ... At the moment we've run out of ver 4.0 bugs. As added incentive to the testers (thanks to all) I have offered free maintenance for a year to any/all who find the next 4.0 bug. And, if it is a really interesting bug, the actual upgrade from 3.5 to 4.0 is offered free.

As a reminder, the primary objectives of 4.0 were to increase the maximum logbook capacity to 1M+ QSOs and to replace the original Microsoft serial port control.
 
Also, just to keep the party exciting, I have finished a little FT4/FT8 add-on ...

It can change JTDX Bands/Modes, and take FT4/FT8 DX Spots and feed them directly into JTDX. Looking at the picture, you can see that JTDX is on 20M/FT4. The developers of JTDX and WSJT have shown little/no interest in opening their external interface to logging programs.  So testing of the Control Panel has been difficult. It works, but not reliably enough to publicly release.
 
So, what we need is for a competent Python savvy programmer to step up and make some simple changes to the JTDX code to allow exchange of messages with Logger32. A word of caution - This is not for the faint hearted. While the actual changes are simple, all the GNU/GPL/BLAH/BLAH rules/regulations/guidelines need to be complied with, and the pay is lousy.
 
We really do need someone to help out. Thanks, 73.
--
73 de aki
JA1NLX


Re: A status report ...

ja1nlx
 

Oliver

Ask Jim W5IFP to join L32Test group. L32Test group is dedicated for testing ver4.0.

73

On 2020/07/14 9:51, F4FQH Olivier wrote:
Hi Bob
 
Where could i find the V4 ?
 
Tks
Olivier
F4FQH
 
From: Bob
Sent: Monday, July 13, 2020 9:33 PM
To: hamlogger@groups.io
Subject: [hamlogger] A status report ...
 
Just to update you on the ver 4.0 testing so far ... At the moment we've run out of ver 4.0 bugs. As added incentive to the testers (thanks to all) I have offered free maintenance for a year to any/all who find the next 4.0 bug. And, if it is a really interesting bug, the actual upgrade from 3.5 to 4.0 is offered free.

As a reminder, the primary objectives of 4.0 were to increase the maximum logbook capacity to 1M+ QSOs and to replace the original Microsoft serial port control.
 
Also, just to keep the party exciting, I have finished a little FT4/FT8 add-on ...

It can change JTDX Bands/Modes, and take FT4/FT8 DX Spots and feed them directly into JTDX. Looking at the picture, you can see that JTDX is on 20M/FT4. The developers of JTDX and WSJT have shown little/no interest in opening their external interface to logging programs.  So testing of the Control Panel has been difficult. It works, but not reliably enough to publicly release.
 
So, what we need is for a competent Python savvy programmer to step up and make some simple changes to the JTDX code to allow exchange of messages with Logger32. A word of caution - This is not for the faint hearted. While the actual changes are simple, all the GNU/GPL/BLAH/BLAH rules/regulations/guidelines need to be complied with, and the pay is lousy.
 
We really do need someone to help out. Thanks, 73.
--
73 de aki
JA1NLX


Re: A status report ...

F4FQH Olivier
 

Hi Bob
 
Where could i find the V4 ?
 
Tks
Olivier
F4FQH
 

From: Bob
Sent: Monday, July 13, 2020 9:33 PM
To: hamlogger@groups.io
Subject: [hamlogger] A status report ...
 
Just to update you on the ver 4.0 testing so far ... At the moment we've run out of ver 4.0 bugs. As added incentive to the testers (thanks to all) I have offered free maintenance for a year to any/all who find the next 4.0 bug. And, if it is a really interesting bug, the actual upgrade from 3.5 to 4.0 is offered free.

As a reminder, the primary objectives of 4.0 were to increase the maximum logbook capacity to 1M+ QSOs and to replace the original Microsoft serial port control.
 
Also, just to keep the party exciting, I have finished a little FT4/FT8 add-on ...

It can change JTDX Bands/Modes, and take FT4/FT8 DX Spots and feed them directly into JTDX. Looking at the picture, you can see that JTDX is on 20M/FT4. The developers of JTDX and WSJT have shown little/no interest in opening their external interface to logging programs.  So testing of the Control Panel has been difficult. It works, but not reliably enough to publicly release.
 
So, what we need is for a competent Python savvy programmer to step up and make some simple changes to the JTDX code to allow exchange of messages with Logger32. A word of caution - This is not for the faint hearted. While the actual changes are simple, all the GNU/GPL/BLAH/BLAH rules/regulations/guidelines need to be complied with, and the pay is lousy.
 
We really do need someone to help out. Thanks, 73.


Re: A status report ...

John Munton - G7SSE
 

Not until Scottish independence Bob

;-)

73! John - G7SSE 

------ Original Message ------
From: "Bob" <k4cy@...>
Sent: 13/07/2020 20:40:35
Subject: Re: [hamlogger] A status report ...

Now that BREXIT is finalized, don't you guys get to start from scratch again? 73.
 
On 07/13/2020 3:36 PM Tom Wylie <thomasgwylie@...> wrote:
 
 
Hmmmm only a million? I'd better slow down..... :-)
 
Tom
GM4FDM
 
On 13/07/2020 20:33, Bob wrote:
> Just to update you on the ver 4.0 testing so far ... At the moment we've
> run out of ver 4.0 bugs. As added incentive to the testers (thanks to
> all) I have offered free maintenance for a year to any/all who find the
> next 4.0 bug. And, if it is a really interesting bug, the actual upgrade
> from 3.5 to 4.0 is offered free.
>
> As a reminder, the primary objectives of 4.0 were to increase the
> maximum logbook capacity to 1M+ QSOs and to replace the original
> Microsoft serial port control.
>
> Also, just to keep the party exciting, I have finished a little FT4/FT8
> add-on ...
>
> It can change JTDX Bands/Modes, and take FT4/FT8 DX Spots and feed them
> directly into JTDX. Looking at the picture, you can see that JTDX is on
> 20M/FT4. The developers of JTDX and WSJT have shown little/no interest
> in opening their external interface to logging programs.  So testing of
> the Control Panel has been difficult. It works, but not reliably enough
> to publicly release.
>
> So, what we need is for a competent Python savvy programmer to step up
> and make some simple changes to the JTDX code to allow exchange of
> messages with Logger32. A word of caution - This is not for the faint
> hearted. While the actual changes are simple, all the GNU/GPL/BLAH/BLAH
> rules/regulations/guidelines need to be complied with, and the pay is
> lousy.
>
> We really do need someone to help out. Thanks, 73.
>
 
 
 
 

--
73, John - G7SSE


Re: A status report ...

Bob
 

Now that BREXIT is finalized, don't you guys get to start from scratch again? 73.

On 07/13/2020 3:36 PM Tom Wylie <thomasgwylie@...> wrote:


Hmmmm only a million? I'd better slow down..... :-)

Tom
GM4FDM

On 13/07/2020 20:33, Bob wrote:
Just to update you on the ver 4.0 testing so far ... At the moment we've
run out of ver 4.0 bugs. As added incentive to the testers (thanks to
all) I have offered free maintenance for a year to any/all who find the
next 4.0 bug. And, if it is a really interesting bug, the actual upgrade
from 3.5 to 4.0 is offered free.

As a reminder, the primary objectives of 4.0 were to increase the
maximum logbook capacity to 1M+ QSOs and to replace the original
Microsoft serial port control.

Also, just to keep the party exciting, I have finished a little FT4/FT8
add-on ...

It can change JTDX Bands/Modes, and take FT4/FT8 DX Spots and feed them
directly into JTDX. Looking at the picture, you can see that JTDX is on
20M/FT4. The developers of JTDX and WSJT have shown little/no interest
in opening their external interface to logging programs.  So testing of
the Control Panel has been difficult. It works, but not reliably enough
to publicly release.

So, what we need is for a competent Python savvy programmer to step up
and make some simple changes to the JTDX code to allow exchange of
messages with Logger32. A word of caution - This is not for the faint
hearted. While the actual changes are simple, all the GNU/GPL/BLAH/BLAH
rules/regulations/guidelines need to be complied with, and the pay is
lousy.

We really do need someone to help out. Thanks, 73.


Re: A status report ...

Tom Wylie
 

Hmmmm only a million? I'd better slow down..... :-)

Tom
GM4FDM

On 13/07/2020 20:33, Bob wrote:
Just to update you on the ver 4.0 testing so far ... At the moment we've run out of ver 4.0 bugs. As added incentive to the testers (thanks to all) I have offered free maintenance for a year to any/all who find the next 4.0 bug. And, if it is a really interesting bug, the actual upgrade from 3.5 to 4.0 is offered free.
As a reminder, the primary objectives of 4.0 were to increase the maximum logbook capacity to 1M+ QSOs and to replace the original Microsoft serial port control.
Also, just to keep the party exciting, I have finished a little FT4/FT8 add-on ...
It can change JTDX Bands/Modes, and take FT4/FT8 DX Spots and feed them directly into JTDX. Looking at the picture, you can see that JTDX is on 20M/FT4. The developers of JTDX and WSJT have shown little/no interest in opening their external interface to logging programs.  So testing of the Control Panel has been difficult. It works, but not reliably enough to publicly release.
So, what we need is for a competent Python savvy programmer to step up and make some simple changes to the JTDX code to allow exchange of messages with Logger32. A word of caution - This is not for the faint hearted. While the actual changes are simple, all the GNU/GPL/BLAH/BLAH rules/regulations/guidelines need to be complied with, and the pay is lousy.
We really do need someone to help out. Thanks, 73.


A status report ...

Bob
 

Just to update you on the ver 4.0 testing so far ... At the moment we've run out of ver 4.0 bugs. As added incentive to the testers (thanks to all) I have offered free maintenance for a year to any/all who find the next 4.0 bug. And, if it is a really interesting bug, the actual upgrade from 3.5 to 4.0 is offered free.

As a reminder, the primary objectives of 4.0 were to increase the maximum logbook capacity to 1M+ QSOs and to replace the original Microsoft serial port control.

Also, just to keep the party exciting, I have finished a little FT4/FT8 add-on ...

It can change JTDX Bands/Modes, and take FT4/FT8 DX Spots and feed them directly into JTDX. Looking at the picture, you can see that JTDX is on 20M/FT4. The developers of JTDX and WSJT have shown little/no interest in opening their external interface to logging programs.  So testing of the Control Panel has been difficult. It works, but not reliably enough to publicly release.

So, what we need is for a competent Python savvy programmer to step up and make some simple changes to the JTDX code to allow exchange of messages with Logger32. A word of caution - This is not for the faint hearted. While the actual changes are simple, all the GNU/GPL/BLAH/BLAH rules/regulations/guidelines need to be complied with, and the pay is lousy.

We really do need someone to help out. Thanks, 73.


Re: Generic QSOs page grid - how to change

Bob
 

Martin, likewise, I am disappointed. So sad. Maybe it's just me, I'm old and was born two generations before the age of entitlement. You are of course eligible for the 'full refund if not fully satisfied'. SeventyThree(s).

PS. Let me know when your logging program is released, I'm sure it will be awesome. I'll gladly be the first to genuflect.

On 07/12/2020 8:34 AM Martin G0HDB <marting0hdb@...> wrote:


On Sun, Jul 12, 2020 at 12:13 PM, Bob wrote:
I suspect there is no option for this. SeventyThree(s).
Thanks Bob, that's rather disappointing - displaying the number of the DXCC entity doesn't exactly convey any particularly useful information...  :-)

I'll take a look at the suggestion that John G7SSE has made; maybe using PFX will satisfy my wish to be able to see either the prefix or the name of the entity rather than just its rather meaningless number!

73
--
Martin G0HDB


Re: Generic QSOs page grid - how to change

Martin G0HDB
 

On Sun, Jul 12, 2020 at 12:13 PM, Bob wrote:
I suspect there is no option for this. SeventyThree(s).
Thanks Bob, that's rather disappointing - displaying the number of the DXCC entity doesn't exactly convey any particularly useful information...  :-)

I'll take a look at the suggestion that John G7SSE has made; maybe using PFX will satisfy my wish to be able to see either the prefix or the name of the entity rather than just its rather meaningless number!

73
--
Martin G0HDB


Re: Generic QSOs page grid - how to change

John Munton - G7SSE
 

Martin

There is a prefix (PFX) field that can be displayed, does this achieve what you require?


--
73, John - G7SSE