Re: [evolution-patches] Possible fix for #322016



On Mon, 2005-12-05 at 13:24 +0000, karllinuxtest relton ntlworld com
wrote:
> Here is a possible fix for bug #322016, to provoke discussion.
> 
> Note I haven't compiled this or tried it - because it is
> not clear that this is the correct way to fix the problem.
> 
> The basic problem is that up->new is true if mails are
> added to the folder, regardless of their unread status. The up->unread will give a count of unread mails, so adding
> this to the conditional expressions will help.
> 
> However, the behaviour would still be wrong if a user moved
> a mail from one folder to another, where the other folder
> had unread messages - it would trigger the notifications.
> 
> Fundamentally the only way I can see to truely fix these
> is for the notifications to be sent after a 'fetch mail'
> operation, i.e. when brand new mail truely arrives into
> Evolution.

The problem is that new mail can arrive more than just after a 'fetch
mail' op. For example, new mail can arrive at any time for IMAP and
possibly other remote mail providers.

> 
> Karl
> 
> 
> -----------------------------------------
> Email sent from www.ntlworld.com
> Virus-checked using McAfee(R) Software 
> Visit www.ntlworld.com/security for more information
> _______________________________________________
> Evolution-patches mailing list
> Evolution-patches gnome org
> http://mail.gnome.org/mailman/listinfo/evolution-patches
-- 
Jeffrey Stedfast
Evolution Hacker - Novell, Inc.
fejj ximian com  - www.novell.com




[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]