What steps will reproduce the problem?
1. Run Witty
2. Wait w/out Clearing Error Dialogues. I get lots of 404s and 502s.
When you leave witty running on an unattended computer for a while, all of
the MessageBox.Show()s accumulate. This is probably also creating a lot
of unnecessary overhead as the current execution thread is blocked.
Instead of displaying a MessageBox, it could update the StatusTextBlock
instead. Since it is an error, it might be nice to fade the
StatusTextBlock to red on errors, and then, when the error clears (lets
say twitter comes back up), it fades back to the usual color. (This way
temporary error notifications are completely erased, since the user likely
won't care about them anyways since the system now working.)
Original issue reported on code.google.com by david.so...@gmail.com on 12 Feb 2008 at 7:57
Original issue reported on code.google.com by
david.so...@gmail.com
on 12 Feb 2008 at 7:57