Re: [evolution-patches] big setting patch



yeah that is bad, I wasn't paying enough attention to the other keys, it
is simple enough to filter on the ones that should, but we may want to
change the schema before we get stuck with it?  Ettore thoughts?

--Larry

On Tue, 2003-05-20 at 12:39, Jeffrey Stedfast wrote: 
> This patch seems "mostly okay" except for listening to changes for all
> /apps/evolution/mail/display/* setting changes. This bothers me only
> because there are settings under that hierarchy that should not cause a
> redisplay of the message - these settings would include:
> 
> /apps/evolution/mail/display/mark_seen
> /apps/evolution/mail/display/mark_seen_timeout
> /apps/evolution/mail/display/show_deleted
> /apps/evolution/mail/display/show_preview
> /apps/evolution/mail/display/paned_size
> /apps/evolution/mail/display/thread_list
> /apps/evolution/mail/display/thread_subject
> 
> I think the best approach for now would just be to listen to the
> individual keys that *should* cause a redisplay.
> 
> However, I think the ideal solution might be to rearrange the gconf keys
> in such a way as to separate out the keys listed above to not be under
> display/ and to instead be grouped somewhere else. For example, we might
> want to move a number of those keys into, say:
> 
> /apps/evolution/mail/message_list/
> 
> mark_seen, mark_seen_timeout, show_deleted, thread_list and
> thread_subject would all be good candidates for this.
> 
> Not sure where the best place for paned_size or show_preview might be,
> maybe the toplevel? (/apps/evolution/mail/)
> 
> Jeff
> 
> On Tue, 2003-05-20 at 12:22, Larry Ewing wrote:
> > This hooks up the settings that were not hooked up and add the
> > appropriate schema entries.
> > 
> > --Larry




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