From 512ff3b3dd27539dcea174cdbf3b594a82187076 Mon Sep 17 00:00:00 2001 From: Julio Biason Date: Sun, 18 Apr 2010 10:27:45 -0300 Subject: [PATCH] fixed the way we work with volatile messages when updating status --- mitterlib/ui/ui_pygtk.py | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/mitterlib/ui/ui_pygtk.py b/mitterlib/ui/ui_pygtk.py index b103ea4..da1e5b1 100644 --- a/mitterlib/ui/ui_pygtk.py +++ b/mitterlib/ui/ui_pygtk.py @@ -802,7 +802,7 @@ class Interface(object): """Function called if the retrival of current messages returns an exception.""" _log.debug(str(exception)) - + # if we get a NetworksNoNetworkSetupError, we need to show the # settings window if isinstance(exception, NetworksNoNetworkSetupError): @@ -897,7 +897,7 @@ class Interface(object): ### Results for the update status call def _post_update_status(self, widget, data): """Called when the status is updated correctly.""" - self._update_statusbar(_('Your status was updated.')) + self._statusbar.volatile(_('Your status was updated.'), pair='update') self._action_group.get_action('Update').set_sensitive(True) self._clear_text(None) @@ -926,6 +926,7 @@ class Interface(object): # re-enable the update, or the user won't be able to repost their # message. self._action_group.get_action('Update').set_sensitive(True) + self._actionbar.volatile(_('Update failed.'), pair='update') return ### Results for the delete message call