KR> the reason that i like ppoint so much is that there is zero
 KR> hassle, i've probably spent no more than 5% of the time on it
 KR> that any of the pkt2qwk or squish users have, and it has never
 KR> sent messages to the wrong area. i got a shoal of dupes with a
 KR> shonkey system that i set up at 3am one morning but that was my
 KR> fault. when a new version comes out, i can usually have it up
 KR> and running in less than 30 min.

  The only problem I have with PQWK is trhat Paul brings out a new
version every week, but I have had so much experience now that I can
change the system while it's sending the mail! My record for changing
(from v181 to v182... it's now up to v221) is 17.2 seconds. 30 minutes
sounds like a lot to me. :-)

 KR> thats my sort of software, no fucking about, it just works.
 KR> corse, the user interface is fucked, but thats another story
 KR> (-8

  What you need is something with a fucked program to go with your 
fucked interface. TinyPoint could be for you! (It actually works like
a charm).

 KR> sounds a great hobby, and a good way to learn vb. i always
 KR> reckonned the way to learn a language was to find a project
 KR> that you really want to do, and write the program to do it.

  Yair... and when I get it working in VB, I do it again in C, to see
if I can learn any other tricks.

 KR> i am doing the same thing with c++ and owl to write a windows
 KR> prog, the learning curve is so steep that i think that i need a
 KR> rope and pitons. )-8

  In my mind, the "steep learning curve" phrase is backwards. I know
what you mean, but to me, a steep learning curve is something I learn
easily; a whole lot of stuff quickly. I find VB has a steep learning
curve, and C a slow one. It's a real battle to learn anything new in
C, but shit easy in VB (which is why I use it).

  I guess I plot knowledge versus time... what you do use on the
horizontal axis of your "steep" curve?

Regards,
Bob
     
___ Blue Wave/QWK v2.12
@EOT:

---