On Fr, 2011-12-09 at 18:43 +0000, Brian wrote:
Patrick Ohly <patrick.ohly@...> writes:
> On Fr, 2011-12-09 at 17:10 +0000, Brian wrote:
> > Patrick Ohly <patrick.ohly@...> writes:
> > but they also leave the notification
> > icon live tempting me to distraction to check it...
> > I'd be happy to hand edit one of the config(ini) files...
> > I only have one sync peer, so I'm not really qualified to answer per
> If the user wants different settings for different peers, the setting
> has to be per peer.
> If the user wants the same setting for all peers, including those not
> configured yet, and wants to turn them on and off for all peers at once,
> then it has to be global.
> I personally expect the second case to be more likely. But what do I
> know... user preferences are notoriously hard to predict
Agreed that user prefs are impossible to predict. If it's not too
much coding, many hierarchical config frameworks allow a global setting
which can be over-ridden by a per-peer setting.
The config files are hierarchical, but the hierarchy is not exposed in
the APIs: for example, a GUI can only set "loglevel", but not "global
It would be a useful extension. I need to think a bit about how to do
> > If it's straightforward, I would think that separating
"info" versus "error"
> > would make a lot of sense.
> There could be a "notify level" similar to the current log level: 0 =
> everything, 1 = only errors, 2 = errors and info messages.
What's the difference between 0 and 2? I would think that 0 = nothing?
Right, 0 was meant as "show nothing".
Would another distinction between "info message about sync without
changes" and "info message about sync with changes" be useful?
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.