[WriteLog] Re: How to Disable Non-Logging Functions
Sat, 2 Mar 2002 06:36:31 -0600
I think you are OVERTHINKING the situation.
There is no need to do what you want.
You really can't hurt WL.
Let it run the way it was designed.
Doing what you are suggesting ... you might as well just use a word
processor and log that way.
And by next year your crew will have forgotten what you learned this year.
WL is pretty tough...it won't self-destruct.
----- Original Message -----
From: "Pat Conway" <firstname.lastname@example.org>
Sent: Friday, March 01, 2002 9:42 PM
Subject: [WriteLog] Re: How to Disable Non-Logging Functions
> Thank you to FireBrick and Tony for your responses.
> Tony, what I mean is I'd like to disable the entire interface to the
> radios, antennas, etc - including readouts. This year, as novices to
> both networked logging and Writelog, we want to tackle no more than
> networked logging by manually editing the QSO data. Next year we'd hope
> to integrate rig control. So my goal is to do what I can to make sure
> someone won't make the program hang by selecting some menu item that
> we're not set up for.
> Firebrick, I was thinking about making the ini file read-only. The
> problem is 1) determining if that's sufficient; and 2) figuring out what
> that ini file should look like. None of us have used Writelog before
> and I'd rather bank on the experience of you guys than the book-learning
> I can get from the Help menus.
> Thanks to all for trying to help me figure this out!.
> Do You Yahoo!?
> Get your free @yahoo.com address at http://mail.yahoo.com
> WriteLog mailing list