Concerning the problem of floppy saves happening too often, I think I
might know how this can happen.
The floppy saves are done based upon the number of QSOs that have
scrolled off the top of the editable log window and into the .DAT
file. If you have some blank lines in the editable log window, you
can have this total stay constant for consecutive QSOs. If that total
is right for a floppy save - you will get two (or more) of them in a
row - until the count is incremented by a QSO scrolling off the top
of the editable log window.
Gee - that is two of these "bugs" possibly explained and maybe things
aren't as bad as my earlier post made them out to be.
While debugging this - I noticed that any error messages that should
be displayed if the floppy save fails (i.e., the disk is too full)
are not staying up on the screen long enough to read them. There
is an error sound being made, but no message. I will get this fixed.
Tree
--
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
|