kms@ecsvax.UUCP (Ken Steele) (06/08/89)
[Tony: I tried to mail this to you but it keeps being bounced back]
I have found another (minor) 2.8A problem. Try to assign a shortcut
key to xmodemCRC. It gets assigned to xmodem. It appears as if
something like the following is happening:
switch (read_init_file()){
case ASC: assign_key_stuff();
break;
case KE: assign_key_stuff();
break;
case XMC: assign_key_stuff();
case XM: assign_key_stuff();
break;
default: complain();
break;
}
The effect is like a missing break statement such that the letter to
be assigned to XMC falls through and is assigned to XM.
Also, would you consider changing the xmodem info window so that the
title reflected whether the CRC or checksum protocol was being used.
For one set of work I need to be switching back and forth between
the two, and it would help to know that I was at least beginning
with the correct protocol.
Thanks again.
--ken
--
Ken Steele Dept. of Psychology kms@ecsvax.[bitnet || UUCP]
Mars Hill College kms@ecsvax.uncecs.edu
Mars Hill, NC 28754 acs@pccuts.pcc.amdahl.com (Tony Sumrall) (07/06/89)
Sorry, I've been on vacation for a LONG while and just saw this. In article <7126@ecsvax.UUCP> kms@ecsvax.UUCP (Ken Steele) writes: } }[Tony: I tried to mail this to you but it keeps being bounced back] } }I have found another (minor) 2.8A problem. Try to assign a shortcut }key to xmodemCRC. It gets assigned to xmodem. Correct! It was a coding error which has been fixed in 2.9. No, 2.9 is NOT out yet. }Also, would you consider changing the xmodem info window so that the }title reflected whether the CRC or checksum protocol was being used. }For one set of work I need to be switching back and forth between }the two, and it would help to know that I was at least beginning }with the correct protocol. Good idea. I'll try to remember to incorporate this change when I get back to my machine. }Ken Steele Dept. of Psychology kms@ecsvax.[bitnet || UUCP] } Mars Hill College kms@ecsvax.uncecs.edu } Mars Hill, NC 28754 -- Tony Sumrall acs@pccuts.pcc.amdahl.com <=> amdahl!pccuts!acs [ Opinions expressed herein are the author's and should not be construed to reflect the views of Amdahl Corp. ]