Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

Error Notification #153

Closed
jshyeung opened this Issue Nov 16, 2011 · 7 comments

Comments

Projects
None yet
7 participants
Owner

jshyeung commented Nov 16, 2011

Currently freeseer just log the error without providing any feedback to the user on the UI, and user only find out of the problem when they try to play back the video.

I am suggesting an notification system which give proper feedback to user when an error has occurred.

Owner

mtomwing commented Feb 8, 2014

Maybe we should take advantage of things like libnotify on most Linux distributions? Not sure what to do about Windows though.

Example in Python

Owner

zxiiro commented Feb 8, 2014

I think libnotify has to do with systray but let me know if I'm wrong.

I envision a notification system that appears right inside the Freeseer recording Window (maybe below the preview?) I'm not sure where the best place is.

I think it should support 2 types of notifications too. Ones that cannot be cleared such as space warning. And ones that can be cleared such as notifications like when the recording backend fails to start.

Owner

mtomwing commented Feb 8, 2014

IIRC, libnotify will issue the notification to whatever daemon the user has configured.

For example, users on distros with Gnome will see something like:
offline

You can play around with it using the notify-send utility and of course there are Python bindings for it.

notify-send "Testing" "Look at this body" --urgency=critical

screenshot 2014-02-08 12 13 07
Because the urgency is set to critical, the notification won't go away until the user clicks on it.

Owner

dideler commented Feb 8, 2014

You can also set the icon used in the message with notify-send.

Member

MadMub commented Feb 9, 2014

Personally prefer notifications as a part of freeseer UI, just for the sake maintainability/cross-platform support

Contributor

farazs commented Oct 18, 2014

I was thinking something along the lines of dividing the status bar into two, with one side being the current status (like it is now) and the other side being the latest log/warning/error or something of the sort. I was also thinking of adding a sort of icon to the status bar which would be either a green checkmark, yellow exclamation or red X, depending on the contents of the log.

Aside from this there should also be a log window that's accessible from the menu, double clicking the status icon or the log message section of the status bar should also open this log window. The log window can have a "Clear log" button which also clears the status bar error message and resets the status icon to green.

Thoughts?

Owner

dideler commented Oct 19, 2014

I like the log idea.

The problem I see with using the status bar for notifications is that it's too basic. Limited space, not very visible, and doesn't allow for interaction (might be needed for some notifications/errors). On the other hand, it's a start and might be good enough for our needs, instead of building some complex notification system (YAGNI). The visibility could be addressed with proper styling.

Also see #479

@farazs farazs referenced this issue Oct 23, 2014

Merged

Fix #153 - Log / Error Notification System #635

9 of 9 tasks complete

farazs added a commit to farazs/freeseer that referenced this issue Nov 9, 2014

Fix #153 Log and Error Notification System
Added a log window accessible through the help
menu. Added a widget to the Record status bar
that displays the latest high priority message
with a status icon to indicate the type of message.

@dideler dideler closed this in #635 Nov 11, 2014

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment