TIP: Click on subject to list as thread! ANSI
echo: bluewave
to: Dan Ceppa
from: Nancy Backus
date: 2005-04-23 23:44:28
subject: Re: Toggle?

-=> Quoting Dan Ceppa to All on 04-23-05  00:37 <=-

 DC> In BW 2.30, when entering an already fully read Echo but with 
 DC> messages still there, the default to enter is "No"  

 DC> Is there a way to make it "yes"?  

In 2.20 (and I'd guess also in 2.30), it's under Message Read
Preference, Inform When All Messages Read.  When set to Yes, the default
to enter is "no".  When set to No, it just goes right into the fully
read Echo, beginning with the first message you'd normally read if it
had been fully unread.

 DC> Not a big deal, as I can globaly make them unread.  But, I'd 
 DC> like the other version!   

Also not a big deal, as when the pop-up tells you they are all read, and
assumes "no", you can always press "Y" and override the
default.  I do
that all the time... :)

Just to check it out, I set it to No...  I notice that it still jumps to
the next un-read echo, if there is more than one echo fully read, but
not all of them...  But it doesn't nag, if I choose any echo that has
been fully read.  I normally have it set to Yes, and then override if I
need to check something again in a fully read echo...  :)

ttyl          neb

... If we are here to help others, what are the others here for?

___ Blue Wave/QWK v2.20

--- ViaMAIL!/WC v1.60d
* Origin: Chowdanet (401-331-0615) telnet://chowdanet.com (1:323/120)
SEEN-BY: 633/267 270 5030/786
@PATH: 323/120 3613/1275 123/500 106/2000 633/267

SOURCE: echomail via fidonet.ozzmosis.com

Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.