CompuServe Thread

#Whap 1.9c HELP!

9 messages in this thread
#957From: Brian YamanakaSep 17, 1990 4:58 AM
To whom it may concern, I seem to be experiencing a *lot* of difficulties while trying to install Whap! 1.9c on my 3000. This is an unvalidated version of Whap and I am awaiting re-validation as my last copy was 1.8. Symptoms are: 1 – Under 2.0 the select message header screen takes a *long* time to appear and some of the buttons on the bottom appear without labels. I think there are supposed to be ghosted. 2 – Refuses to dial in 7-wire mode where as it worked with a prior release of Whap! Could you please indicate which serial lines are monitored so I can check my modem config. 3 – Fails to download under 1.3 and 2.0. With 1.3 the download screen appears, but downloads fail or hang. With 2.0 the program hangs before the download screen appears. 4 – Sometimes during a session, especially when either sending or receiving messages and mail, Whap! will wait at a prompt without responding. The Bull timer will run out, but Whap continues to wait. I hope my questions can be answered soon. Whap! has always saved me time when using CIS and I would like to be able to use this version under 2.0 Thanks, Brian Yamanaka 72250,3544
#984From: Steve AhlstromSep 17, 1990 3:56 PM
Brian, 1.9C has not been tested on a 3000. However, it works on a 2000 running kick version 143. I've been using it in that configuration for a couple of weeks now, have downloaded over 15M of files, and have never used anything other than the 7 wire configuration. If you are not using 143, I suggest to attempt to get it from your dealer. As to View!, there are many problems with it under 143 because of changes CBM made. The most obvious is that CBM has changed the priority of gadget refreshes. This means that anytime you activate any other window or View! brings up a requester, gadgets along the bottom disappear and the informational text across the top disappear. As to the gadgets, they're still there, just not rendered. It is usable, click where the gadgets should be and they will reappear, or use the menu. There is also the problem of text being overwritten on the left edge. In 2.0 CBM added a leftside window border area. This clips the left edge of characters on the left edge. Both of the above problems have been corrected in my version of the program. There are other problems that still need to be addressed. If you use the arrow keys, for some (as yet unknown to me) reason, key repeat stops working. Also, when the View! first comes up and your go into reply mode, you cannot more the bar. If you change the size of the window, or change whether you're running on WB or custom screen, that functionality returns. (This is all under 2.0, 1.3 operation remains unchanged). While View! does currently have problems under 2.0, it is functional. 1.9C was uploaded because many people wanted to run it under 2.0 (including myself). When I work out all of the obvious problems in View! as related to 2.0, I will upload an update. In the meantime, despite the glitches, it is functional. -sja
#990From: Harry CallesisSep 17, 1990 5:58 PM
Steve – I just started using View 1.9C, and am noticing something aesthetically different in the message display. The word wrap seems to not be in sync with what CIS send out, or something. I looked at the .MSG files, and they seem to be formatted the way CIS normally would, so the difference would seem to be in the way View is displaying. The symptoms are single-word lines appearing in the message text, where there would be plenty of room on the previous line for that word. For example, in the message I'm replying to, the first line ends at "2000", the word "running" is on a line by itself, and the word "kick" starts the next line. In the MSG file, "running" terminates tje first line. Just in case you hadn't noticed it yourself … 8^). Harry
#992From: Steve AhlstromSep 17, 1990 6:22 PM
Harry, Nothing was changed there, but, LHARC up your .MSG file and email it to me and I'll take a look. Also, be sure you tell me what font you're using. If it's a font I'm not likely to have, send that to me also. Thanks.
#1119From: Harry CallesisSep 18, 1990 6:35 PM
Steve – Unfortunately, when I used Whap! tonight to get your reply, it overwrote the .msg file … Oh, well. And another strange thing, tonight everything seems to be wrapping just fine. Must be the phase of the moon or something. I'm using an IBM font I think I got from here (does IBM-II sound familiar?), and I'm pretty sure I was using it last night, too. Well, if it happens again, I'll be sure to save the files and send them your way (I hate it this happens 8^) ). Thanks … Harry
#1120From: Steve AhlstromSep 18, 1990 6:50 PM
Harry, When Whap gets messages the longest line length is 76. If the font you use is a wide font, and depending on if your run overscanned or not, a 76 character line may not fit across your screen. In which case, what you're seeing is exactly what it should do.
#1173From: Vic WagnerSep 19, 1990 12:47 PM
Harry, I had it happen to me not 20 minutes ago. So, I bailed out of View!, then manually started View!…..and it looked fine. I'm not sure what the problem is, but I'm gonna nail it somehow. Victor A. Wagner, Jr.
#1196From: Steve AhlstromSep 19, 1990 8:09 PM
Vic, Don't bother. I changed the line …. Text(w_rp, &linebuf[1], min(linebuf[0], max_line_length -2 )); to Text(w_rp, &linebuf[1], min(linebuf[0], max_line_length)); This will alleviate the problem. It'll push the text closer to the prop gadget but will not overwrite the prop gadget and will no longer wrap down in a default config'ed system. Why did I do it the other way before? Dunno — senility strikes again. -sja
#1346From: Brian BartlettSep 21, 1990 9:10 PM
Steve, thanks, those lines were kinda annoying. You have my immense appreciation! Brian J. Bartlett