Loading ...
Sorry, an error occurred while loading the content.

Re: [linuxham] 3.20.20 remote logging bug?

Expand Messages
  • David Kjellquist
    Yes Ed, this is what I m seeing. At the bottom and not sent to xlog. The only difference is that with repeated saves, w3nr (highlighted in fldigi log view)
    Message 1 of 7 , Jul 20, 2010
    • 0 Attachment
      Yes Ed, this is what I'm seeing. At the bottom and not sent to xlog. The
      only difference is that with repeated saves, w3nr (highlighted in fldigi
      log view) will be sent to xlog.

      On Tue, 2010-07-20 at 10:28 -0400, Ed wrote:
      >
      > On 07/20/2010 08:37 AM, David wrote:
      > > I use Xlog for logging via a remote call from fldigi. I upgraded to
      > 3.20.20 and now the log data isn't being passed correctly to Xlog.
      > >
      > > Instead of the data being "Saved" by fldigi being sent to Xlog, it
      > is the highlighted entry in the fldigi log. Always the same QSO.
      > However, if I open the fldigi log, highlight another entry and close
      > the log. It will be that highlighted entry sent to Xlog!
      > >
      > >
      > > Dave, WB5NHL
      >
      > I'm not quite sure if I'm seeing the same here or not.
      >
      > I have the fldigi log set so that the newest entry is always at the
      > top.
      > This has changed and it is now at the bottom of the log below my
      > oldest
      > entry.
      >
      > I notice that xlog is one fldigi logged qso behind. If I save w3nr in
      > the fldigi log, not only is it now at the bottom of the list, it is
      > not
      > being sent to xlog. If I save aa5vu in the fldigi log it is now below
      > w3nr at the bottom of the list, not at the top as I have it set. But
      > now
      > the w3nr appears in xlog, but the a5vu entry is not there.
      >
      > Ed W3NR
      >
      >
      >
      >
    Your message has been successfully submitted and would be delivered to recipients shortly.