search

nekohayo / specto

Automatically exported from code.google.com/p/specto
0 stars 0 forks source link

cannot sort columns' ascending or descending order #30

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
Although the sorting order is remembered in gconf, we currently don't sort
the watches prior to populating the notifier window's listview.

Original issue reported on code.google.com by nekoh...@gmail.com on 16 Dec 2006 at 5:09

GoogleCodeExporter commented 9 years ago 
Changed in revision 38; the lines such as
        self.model.set_sort_column_id(4, not self.get_gconf_sort_order())
became
        self.model.set_sort_column_id(4, self.get_gconf_sort_order())

However, this broke the ascending/descending sorting (but fixed sorting 
persistence
on startup and also fixed a gmail bug).

Original comment by nekoh...@gmail.com on 16 Dec 2006 at 9:37

GoogleCodeExporter commented 9 years ago

Original comment by woutclym...@gmail.com on 23 Jan 2007 at 5:27

GoogleCodeExporter commented 9 years ago 
minor glitch left: the sorting order is not set in the menu (for example, if I 
set to
sort by name, the notifier will indeed sort the names on startup, but the 
'sorting'
submenu will not be set to 'name')

Original comment by nekoh...@gmail.com on 24 Jan 2007 at 10:37

GoogleCodeExporter commented 9 years ago

Original comment by woutclym...@gmail.com on 27 Jan 2007 at 2:55

GoogleCodeExporter commented 9 years ago 
It works! thanks

Original comment by nekoh...@gmail.com on 27 Jan 2007 at 3:38

GoogleCodeExporter commented 9 years ago

Original comment by nekoh...@gmail.com on 18 Mar 2008 at 2:00