[LOGic] Dennis RE: RTTY and Hamscope

[J. Wolf, K6JW]

   Some of you may recall that I recently posted a question regarding a 
problem I was having running HamScope with LOGic, namely, crashing when I 
tried to enter a callsign into HamScope. No one on the reflector had either 
experienced it or been able to solve it, so I wrote to Dennis. Here are his 
analysis, work-around, and his plans for the future. This is posted with his 
permission.
--Jeff, K6JW

>From Dennis:

I don't log in HamScope.  I log in LOGic, and let the data come into LOGic's
HamScope windows.  But I tried it, and did see some problems, although it
did not lock up.

It appears to try to do a callbook lookup on each letter of the call that 
you
type in HamScope. LOGic generates some errors from it's callbook module
that it does not do when looking up nonexistant calls such as K from
LOGic's callbook form.

So, I turned auto callbook lookup off in LOGic, and everything worked.  I
turn auto lookup on, and everythnig works flawlessly.  So, if you start
LOGic, start HamScope, log one QSO with auto callbook lookup off, then
turn on auto callbook lookup on, all is well.

I can try to eliminate the errors LOGic generates when HamScope tries to
log partial calls (don't know why he would be doing that), and I plan to
integrate MMTTY into LOGic.

Tnx for using LOGic.

73,

Dennis WN4AZY