Greetings,
I guess I'm dense... I entered my eQSL login information, completed a
few QSOs and logged them, then went to my eQSL page and see no sign of
those QSOs were logged. What am I missing? How can I know whether or
not they were uploaded?
Thanks.
-Joe-
Pierfrancesco Caci wrote:
"w1hkj" == w1hkj<[email protected]> writes:
w1hkj> On 11/13/2011 08:35 AM, Graham Saville wrote:
>> This Email was sent on 13/11/11 at 14:32
>> In Reply to: Re: fldigi-3.22.0BA posted for testing
>>
>> Hi Dave,
>> The EQSL tag works well a nice addition to a great program. Can you
>> tell me what if any error feed back is give from this tag? I.E if it
>> is rejected by eqsl for any reason.
w1hkj> In this version a popup message will appear if there is a
transmission
w1hkj> or log entry failure.
w1hkj> I am changing the implementation to include a thread handler so
that
w1hkj> there is no hesitation in the decoder loop while waiting for
eQSL.cc
w1hkj> to respond. The notifications will then shift to the event log
and it
w1hkj> will include a connect failure, a log entry failure, and a
successful
w1hkj> upload entry.
Finally got around testing BA, both HamQTH and eQSL additions work fine
for me (with the very scientific test set of ONE QSO :-).
I saw a mention in other messages about eqsl using an old adif spec and
rejecting some modes. Maybe a "translation" set like tqsl does could be of
help?
Pf
--
+---------------------------------------------------------------+
| Joseph A. Counsil [email protected] Phone:(573) 341-5186 |
| 1310 Woodlawn Drive, Rolla, MO 65401 Amateur Radio: - KØOG - |
+---------------------------------------------------------------+
_______________________________________________
fldigi-alpha mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/fldigi-alpha
