pieterdd / aptnotifier Goto Github PK

AptNotifier exits silently without warning. We're not sure when it happens, but we're running tests for hours at a time to gather relevant logging data to investigate the issue.

Trigger a notification for a calendar when an appointment is in progress.

Let the user choose whether they want to receive ongoing and/or reminder notifications per calendar.

Google Calendar appointments that are marked on a certain date (as opposed to a certain time) are currently ignored by the calendar parser.

Relevant discussion: http://productforums.google.com/forum/#!msg/calendar/92J00lDwn4k/7HWiFCr3A0YJ

The format should all current features as well as the features mentioned in issues #6 and #7.

Currently the name of a calendar is fixed to the name that is reported by the ICS file. Users should be allowed to change it.

As a result of this, Appointment, with a name will incorrectly be displayed as Appointment, with a name without unescaping special characters.

This problem can currently be reproduced by loading calendar http://aquilis.be/uurrooster/hkt33vss4soc3kck2dj2tne451/calendar.ics, which at the time of writing started with "\nWarning: file(".

We will probably use a generic appointment image and colorize it accordingly. Details aren't set in stone yet.

Aquilis calendars are parsed incorrectly. Further investigation is needed to fix the issue.

My research has indicated that it might be a stack corruption bug. I haven't dealt with serious stack corruption bugs before, so I'm struggling to track down the root of the issue. This information might prove helpful.

I'm on Windows myself, but I might have to resort to the Unix-only memcheck (part of the valgrind suite) to obtain further information.

Bug

• Ensure that AptNotifier reacts to an offline connection in an appropriate manner

Aesthetics/Usability

• Replace the default tray icon with a greyscale version for as long as no updates can be downloaded

Check for calendar updates every so often. Users can trigger a calendar update as well. Make use of file checksums to prevent unnecessary cache rebuilding operations.

Reminders aren't triggered when needed. Requires further investigation to track down the cause.

See also http://stackoverflow.com/questions/9617890/detecting-changes-in-ical-files.