On 10/20/2011 08:36 PM, Ken wrote:
If you have "polling" toggled on in the hamlib tab, turn it off and see if that makes a difference.
Ken Kopp - KK0HF
On Oct 20, 2011, at 3:16 PM, David Kjellquist <address@hidden> wrote:
John;
You are correct I just duplicated the same issue with xlog and my
TS-570D. I couldn't see a quick solution beyond turning off hamlib while
the xcvr is on.
Of course, I don't use hamlib/xlog when fldigi is running.... computers
and xcvrs get real confused when 2 people try to talk on the same
interface. I'm not sure if it's an xlog issue or hamlib, however Joop
isn't doing real active develop, last I saw.
On Thu, 2011-10-20 at 18:44 +0000, John wrote:
On 10/20/2011 03:51 PM, Ed wrote:
On 10/20/2011 05:08 AM, John wrote:
Is there a way to view my Xlog log without having the transceiver
turned
on?
--John, K3GHH
Are you saying that Xlog will not start unless the rig is on ?
Ed W3NR
That's right, Ed. I just get a grey screen. And if I mistakenly turn
the rig off before quitting Xlog, when I try to close Xlog the menu is
unresponsive, and soon an error box appears: "Warning: Kwin. Program
xlog not responding... all unsaved data will be lost..."
_______________________________________________
Xlog-discussion mailing list
address@hidden
https://lists.nongnu.org/mailman/listinfo/xlog-discussion
_______________________________________________
Xlog-discussion mailing list
address@hidden
https://lists.nongnu.org/mailman/listinfo/xlog-discussion
Thanks, David, Ken, and
Pierfrancesco. I'm using 2.0.5 also. Eliminating polling solves
the problem; thanks, Ken! But of course I want polling when I'm
using the program, so I'll have to remember to uncheck it before I
shut it down, and recheck it after booting up. Argh... but a
solution, anyway!
--John, K3GHH
|