Re: [evolution-patches] 45063, more etree api workarounds



On Wed, 2003-06-18 at 17:04, Ettore Perazzoli wrote:
> On Wed, 2003-06-18 at 17:13, Not Zed wrote:
> > this can't be done in the message-list since it doesn't know which
> > message the folder-browser has displayed.
> 
> +       * folder-browser.c (do_message_selected): dont re-load if the same
> +       message gets selected again as one we've already shown.  Etree
> +       sends out selection changed events even when when it hasn't.
> 
> Could this be fixed in ETree instead?

Is this over one of those intervals where the tree is torn down and
rebuilt?  Not sure how we'd suppress the signal in that scenario.  

If it's a double emission of the same selection on a stable tree (which
wouldn't surprise me that much), I can take a look, but with the way
that signals wind in and out through etree/etable, it's hard to say
whether I can fix it without rearchitecting. :/

Mike






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