Jon Nelson wrote: >There is a serious bug in GTK involving the CList. > >Near line 2804 of the current GTK gtkclist.c file, there is some >(partially broken, commented out) code. > >I have "fixed" the code: > > if (clist->focus_row >=0 && > (row <= clist->focus_row || clist->focus_row >= clist->rows)) > clist->focus_row--; > if (clist->focus_row < 0) clist->focus_row = 0; > >Why? > >Take a CList, set the mode to EXTENDED. >attach a signal handler for control-d that deletes the currently >selected rows (after sorting and reversing, so we delete down->up). >Populate the clist with some data. >select the last row. >hit control-d. >Here is the bug: the focus_row is 1 greater than the number of rows. >Still using the keyboard, hold down shift and tap up-arrow. >release shift. >*bang*, sigseg. > >it also works if you select multiple rows, just so long as the last >row highlighted is the last row. > >There are also reported problems with going the other direction (ie, >selecting "up", but I've been unable to reproduce that problem.) > >This is reproduceable 100% of the time. > > Please report GTK+ bugs at http://bugzilla.gnome.org/ under the "gtk+" product (like its README says to). You can also report pygtk bugs there under the gnome-python product.
James. -- Email: [EMAIL PROTECTED] | Linux.conf.au http://linux.conf.au/ WWW: http://www.daa.com.au/~james/ | Jan 22-25 Perth, Western Australia. _______________________________________________ pygtk mailing list [EMAIL PROTECTED] http://www.daa.com.au/mailman/listinfo/pygtk Read the PyGTK FAQ: http://www.async.com.br/faq/pygtk/
