Opened 13 years ago
Closed 12 years ago
#2256 closed patch (Fixed)
Indexes aren't updated properly when removing columns
| Reported by: | Ratanak | Owned by: | |
|---|---|---|---|
| Priority: | minor | Milestone: | 1.3.10 |
| Component: | GTK UI | Version: | 1.3.5 |
| Keywords: | Cc: | Ratanak |
Description
I've been experimenting with columns in the torrent view and found that the indexes keeping track of which ListStore columns are used by a plugin's view column are not updated properly when another plugin's column is removed. This can lead to the column rendering the wrong data in the view. Default columns are not affected since they have fixed indexes, but this can be an issue for plugin developers.
Attachments (2)
Change History (5)
comment:1 by , 13 years ago
by , 13 years ago
| Attachment: | listview.py.2.diff added |
|---|
Patch that updates TreeViewColumn indexes (includes first patch)
comment:3 by , 12 years ago
I've implemented your fix here: https://github.com/bendikro/deluge/tree/1.3.9-column-fix
comment:4 by , 12 years ago
| Milestone: | 1.3.x → 1.3.10 |
|---|---|
| Resolution: | → Fixed |
| Status: | new → closed |
Note:
See TracTickets
for help on using tickets.



Fixing the
ListStoreindexes revealed a deeper issue that better explains why plugin columns were rendering other plugins' column data. It turns out that theTreeViewColumnalso needs updating.When a
TreeViewColumnis created, itsCellRendereris given a fixedListStorecolumn number. Later, when that column number changes (when a column is removed), theCellRenderercontinues to use the old column index. For example:I have added another patch that should resolve the
TreeViewColumnindex not being updated.