On 23 Apr 05  19:44:29, Nancy Backus got back to Dan Ceppa 
-> Re: Toggle?

 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"?  

 NB> In 2.20 (and I'd guess also in 2.30), it's under Message Read
 NB> Preference, Inform When All Messages Read.  When set to Yes, the
 NB> default to enter is "no".  

That was easy enough!  For some reason, I thought it did something 
different...  

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

I just hate the nag!   

 NB> Just to check it out, I set it to No...  I notice that it still jumps
 NB> to the next un-read echo, if there is more than one echo fully read,
 NB> but not all of them...  

I think that may be a function of the "Read New Messages First".  
As it was, this Echo was set to be entered first and it was 
highlighted though all messages had been read.  

 NB> But it doesn't nag, if I choose any echo that
 NB> has been fully read.  I normally have it set to Yes, and then override
 NB> if I need to check something again in a fully read echo...  :)

For me, I tend to scan an Echo base and delete what I don't feel 
like reading or replying.  I then go back and read more in depth.  


--- OMX/Blue Wave/DOS v2.30