Taskbar Notifier

0.9 Finally Here (Thanks for waiting)

Missed call taskbar notifications added, support for 1.1.3 and if run on an iPod Touch will not check SMS or Missed Calls. It'll be on installer ASAP.

There are 2 versions. One for 1.1.3 and one for anything pre 1.1.3. Please make sure you get the correct one. The new one runs as mobile and there are other fairly major changes.

This iPhone application adds a small envelope icon in the taskbar when you have an unread email message, a small speech bubble when you have an unread SMS message and a small telephone icon if you have a missed call. It is useful for reminding you from anywhere within the iPhone user interface that you have an unread message. This includes the lock screen and on your multiple home screens.

Yes! You can finally check your email from the lock screen (assuming you have your email set to auto check)

After the initial blue popup when an SMS message is received, the only place in the UI in which you are reminded of the unread message is the home screen, which as we all know is not where you spend the majority of your time!

This application is possibly even more useful for email because you're never actually notified of these anywhere other than the home screen.

Changes in 0.9

• Once again the code has been significantly cleaned up.
• It now checks missed calls
• It fully supports 1.1.3
• It now uses an NSTimer to time the checks (if you experience problems with alarms not sounding in the clock application then please let me know. I have found that deleting an alarm and recreating it seems to fix the problem and I am looking into what is causing it)
• It now checks whether you are using an iPod Touch or an iPhone and acts accordingly (does not check missed calls and SMS messages on iPod Touch)

Know Issues

• If you have unread messages in a disabled account (in preferences) the account will be checked and you will be notified of this message.
• There is a chance that it may interfere with the alarm clock application (very occasionally). I have yet to find the exact cause of the problem (it is something to do with my use of NSTimer).