On Fr, 2011-12-09 at 17:10 +0000, Brian wrote:
Patrick Ohly <patrick.ohly@...> writes:
> > Is there anyway to end my torment?!?
> Wow, strong words. Good to that you make your frustration known before
> it eats you alive
> The notifications are generated via libnotify. They are not meant to
> interrupt anything, in particular they shouldn't result in a pop-up
> dialog which grabs focus and has to be acknowledged. Are you seeing
> something annoying like that, or why do you find them annoying?
> Sorry, no, currently these notifications cannot be turned off. The need
> for that hadn't been anticipated. But now that I know it would be easy
> to add a configuration option.
> Should that be per peer or global? Do you want to suppress only
> notifications for successful syncs or also for failed ones?
> This would be for advanced users and would default to "notifications
> enabled" (because otherwise normal users will never know that they can
> be enabled). The setting would not be exposed via the sync UI, because
> it doesn't have a concept of "system settings for sync".
Just becoming a serious pet peeve. Especially because I've spent a helluva
lot of time hunting for a solution before I resorted to public wailing. The
popups occasionally catch a mouse click,
Because they pop up under the mouse?
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 peer/global.
If you only have one peer, there's no difference. Suppose you have more
than one. Then the difference is this: if the users wants to suppress
informational messages for all peers, he has to change the setting in
each peer's config.
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 ;-)
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.
Or is there a way to catch it at the libnotify level (for only
don't think so...)
I don't think so either.
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.