[gnome-clocks] Actually assign the correct alarm to the standalone



commit c89b66a8df6c309738eec2995759f3a690f2c862
Author: Paolo Borelli <pborelli gnome org>
Date:   Fri Aug 31 14:18:51 2012 +0200

    Actually assign the correct alarm to the standalone
    
    Since we save and reload, we need to get the new object from the list

 gnomeclocks/alarm.py |    4 ++--
 1 files changed, 2 insertions(+), 2 deletions(-)
---
diff --git a/gnomeclocks/alarm.py b/gnomeclocks/alarm.py
index 51ea1e3..b7920a3 100644
--- a/gnomeclocks/alarm.py
+++ b/gnomeclocks/alarm.py
@@ -382,6 +382,7 @@ class Alarm(Clock):
         self.liststore.clear()
         self.load_alarms()
         self.notify("can-select")
+        return self.alarms[i]
 
     def delete_alarms(self, alarms):
         for a in alarms:
@@ -495,7 +496,6 @@ class StandaloneAlarm(Gtk.Box):
     def _on_dialog_response(self, dialog, response):
         if response == 1:
             new_alarm = dialog.get_alarm_item()
-            self.view.update_alarm(self.alarm, new_alarm)
-            self.alarm = new_alarm
+            self.alarm =self.view.update_alarm(self.alarm, new_alarm)
             self.update()
         dialog.destroy()



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]