As I have reported before, I think there is a problem in the input buffer
handling of the packet and RTTY windows. The problem occurs when I have
the window set so that just one line of input shows. Then I maximize the
window and perhaps send a command, such as DIR/N. Later I minimize the
window again to its former dimensions. Then anything I type is ignored and
"rings" an error bell, except for the Enter key - so the PacketCluster
returns K2CIB de nnnn.
If I maximize again and position the cursor to the bottom, below anything
I've sent before, then minimize it again, I can usually regain my input.
Closing DX4WIN and restarting it works OK for me.
John, K2CIB
[EMAIL PROTECTED]
man.qth.net To:
dx4win@mailman.qth.net
Sent by: cc:
[EMAIL PROTECTED] Subject: Dx4win digest, Vol 1
#63 - 10 msgs
n.qth.net
02/26/2002 12:01 PM
Please respond to
dx4win
Original Message:
Message: 4
To: dx4win@mailman.qth.net
Date: Tue, 26 Feb 2002 02:29:08 +0000
From: Fred W Hoffert <[EMAIL PROTECTED]>
Subject: [Dx4win] Packet Window Weirdness
For some reason my packet window started acting up earlier this evening.
For as long as I can remember I could enter a packet line, like a talk
line, hit enter, and the line I just typed would disappear (move up) and
the entry line would be blank, ready for the next line. Now, I type a
line, hit enter and the cursor moves to the next line and eventually out
of sight. Any suggestions on how I get the correct functioning back.
73 and thanks,
Fred/NA2U
CWMAN...I'D RATHER WORK CW!!!
"Je mange donc je suis."
"Good wine is a necessity of life for me."--Thomas Jefferson
_____________________________________________________________
