In trying out packet and the band map at W6YX for the first time on our
newly interfaced FT-1000MP, we were really pleased with this new
capability (for us). We encountered some unexpected behavior, though.
We found that if we "worked" a station in the bandmap, logging the
contact on the non-interfaced computer didn't alter the
needed-multiplier "smiley face" or add the asterisk for a dupe contact
to the bandmap on either computer. Logging bandmap contacts on the
interfaced computer altered the bandmap on both displays. If an
improperly displayed call was subsequently duped by putting the call
into the call window and entering a space character, then both displays
were updated. I also crashed TR and got a "Divide by Zero" when I just
hit Enter in response to the frequency query on the non-interfaced
computer.
Have we incorrectly set some configuration setting that may have caused
this, or is it supposed to work this way? Sorry, but I don't have the
config file available to email.
A second problem was with bandmap entries with slashes in the callsign,
such as K6XX/6Y5. After using CTRL-END to get into the bandmap,
scrolling over one of these lines caused the slash character to turn
into a space. Hitting Enter over one of these calls causes the call
window to be filled with an invalid callsign such as "K6XX 6Y5" so that
Enter can't be pressed to work the station.
Again, is this expected behavior, a configuration problem, or a bug?
-Mike, N7MH
--
FAQ on WWW: http://www.contesting.com/trlogfaq.html
Submissions: trlog@contesting.com
Administrative requests: trlog-REQUEST@contesting.com
Problems: owner-trlog@contesting.com
Feature Wishlist: http://web.jzap.com/n6tr/trwish.html
|