my eqsl and lotw seems to now be broken.
I no longer have lotw showing confirmed on the qsl screen
eqsl seems to have messed up too. before I revert back to 2.4. was there anybody else seeing this issue
was there a change in the way log4om handles qsl.
was there a change in the way log4om handles qsl.
Dave ve3wej / ve3ie
Re: was there a change in the way log4om handles qsl.
Take a look starting on Page 77 of the new users guide that you can download with any version of Log4OM V2.ve3wej wrote: 21 Apr 2020, 21:22 my eqsl and lotw seems to now be broken.
I no longer have lotw showing confirmed on the qsl screen
eqsl seems to have messed up too. before I revert back to 2.4. was there anybody else seeing this issue
But, yes handling of uploads, etc. have been modified. Take a view of the UG before you make wrong assumptions.
73 - Nolan Kienitz - KI5IO
Plano, TX
Plano, TX
Re: was there a change in the way log4om handles qsl.
the qsl manager image at the bottom of pg 77, is what I see as well, but the sent and received columns no longer say yes or no to the contacts in the list
can I send a screen captuire to show you
can I send a screen captuire to show you
Dave ve3wej / ve3ie
Re: was there a change in the way log4om handles qsl.
Dave,ve3wej wrote: 22 Apr 2020, 19:15 the qsl manager image at the bottom of pg 77, is what I see as well, but the sent and received columns no longer say yes or no to the contacts in the list
can I send a screen captuire to show you
Post your screen clips as part of this thread so other OMs can view, add value and/or learn as well.
Have you made any changes in Configuration / Confirmations about what value is defaulted in the Sent and Rcvd fields?
Have you made any 'bulk' field changes?
Or have the changes happened after you did an upload?
Will need more details with respect to what steps you took to get to where you have noted a change.
As an aside have you yet installed V 2.5.0.0 ? This won't impact those fields, but just curious.
73 - Nolan Kienitz - KI5IO
Plano, TX
Plano, TX
Re: was there a change in the way log4om handles qsl.
the issue has corrected itself. not sure why. I must have been doing things wrong.
learning curve
thanks for listening
learning curve
thanks for listening
Dave ve3wej / ve3ie