Path: utzoo!attcan!uunet!aplcen!uakari.primate.wisc.edu!sdd.hp.com!usc!cs.utexas.edu!rutgers!faatcrl!jprad
From: jprad@faatcrl.UUCP (Jack Radigan)
Newsgroups: comp.sys.amiga
Subject: Re: JRCOMM 1.0 BS
Keywords: red
Message-ID: <18@faatcrl.UUCP>
Date: 30 Jul 90 18:37:34 GMT
References: <dd96052268df26a4eae0@canremote.uucp> <1657@nyx.UUCP> <7@faatcrl.UUCP> <1696@nyx.UUCP>
Organization: FAA Technical Center, Atlantic City NJ
Lines: 60

bscott@nyx.UUCP (Ben Scott) writes:

>Well, I found out to my embarrasment that I had not installed the fonts as
>such, but once I did the GURU stopped.  (it DID GURU, BTW...not just a lockup)
>Since I always used topaz in the earlier versions, due to when I used to 
>use Snipit and it didn't like your font, I just sorta neglected to put the
>new ones in my Fonts: dir.  

Hmm, hadn't seen the guru, guess it's possible though, a fairly nasty brain
cramp produced that code segment...  BTW, Snap works fine with the fonts in
JR-Comm, don't know about snipit though.

>Anyway, I tried it a few times and it seemed to
>be fairly solid, but I'm back to Handshake now for VT100 for a few reasons, 
>not all of which are your fault.  (I wish, though, that lines too long for
>the screen would wrap around - I know a VT100 terminal doesn't do this, but
>Handshake has an option (HINT HINT) for it and it does help - 

Uh, there is an option for wrapping lines...

>also, when a
>too-long line leaves a character at the end, the optimized scroll routine
>"forgets" about it and leaves it on the screen until a screen clear... not
>exactly a bug, but...)

Yep, got that one fixed now.

>(also, I seem to have very few choices as to what
>color to set the title bar to in VT100 mode, else it will flash mercilessly.
>I liked the old multicolor scheme better, but that's another story) 

Well, the way I set it up was so that you could have hi/lo intensity instead
of bold rendered text and I also wanted to eliminate the flashing menu items
that Handshake exhibits.  Unfortunately, it does leave you with little in the
way of flexibility unless you change the colors in the palette itself.  Also,
you'll notice that the colors are "tied" to one another to keep things
consistent.

>One question:  WHY did you change some of the old keyboard shortcuts, most
>notably the one for the phone book and for the screen title, when you added
>the new functions?  Why not just use new shortcuts for the new functions?

Again, I wanted things a bit more consistent, there wasn't too many changes,
just two or three that I can think of.

>Anyway, I've put 1.0 away until A: I can afford to register to get rid of
>that delay screen, which I can't now due to some sudden dental work, and B:
>your "bug fix" version (1.1?) comes out, even if the bugs don't affect me,
>you might change some more things (hope hope).

Yes, 1.01 should be out shortly.  It has corrected some of the more abusive
problems and now works fine with 2.0 (again).  I was also able to get ahold 
of a rather nice (and brutal) VT-100 test program.  'Tis amazing how things
differ in reality over how it is described in a manual for these things. ;-)

>Remember, the more you make user-selectable the more people you'll please!

Hehe, I want to consider it somewhat "finished" in *this* century!

  -jack-