A debian user reported that when deleting a file in detailed view mode, the focus was reseted to the first file in the list, and not (for example) the next one. This makes keyboard navigation harder. This is on 0.9.0 (but this one doesnt exist on bugzilla) Cheers,
*** Bug 4108 has been marked as a duplicate of this bug. ***
Reproducable here. I'm working on a fix right now.
Okay, this was a tricky one. It actually affected all views, not only the detailed list view. I hope I've fixed it permanently and I tried to fix it as clean as possible. * thunar/thunar-standard-view.c: Restore the selection after deleting a file/folder. This is done by connecting to the "row-deleted" signal of the model twice. The first handler saves the tree path to be selected after the removal in the selection_before_delete member. The second handler (which is called after the signal is emitted) selects this path. Selection is not modified if there are two or more files selected. @Yves-Alexis: The commit diff should apply fine to beta 2. Could you check before and after applying it to your package?
(In reply to comment #3) > Okay, this was a tricky one. It actually affected all views, not only the > detailed list view. I hope I've fixed it permanently and I tried to fix it as > clean as possible. > > * thunar/thunar-standard-view.c: Restore the selection after deleting > a file/folder. This is done by connecting to the "row-deleted" > signal of the model twice. The first handler saves the tree path to > be selected after the removal in the selection_before_delete member. > The second handler (which is called after the signal is emitted) > selects this path. Selection is not modified if there are two or > more files selected. This is revision 28902 btw.
(In reply to comment #4) > (In reply to comment #3) > > Okay, this was a tricky one. It actually affected all views, not only the > > detailed list view. I hope I've fixed it permanently and I tried to fix it as > > clean as possible. > > > > * thunar/thunar-standard-view.c: Restore the selection after deleting > > a file/folder. This is done by connecting to the "row-deleted" > > signal of the model twice. The first handler saves the tree path to > > be selected after the removal in the selection_before_delete member. > > The second handler (which is called after the signal is emitted) > > selects this path. Selection is not modified if there are two or > > more files selected. > > This is revision 28902 btw. Is 28903 part of the fix too?
(In reply to comment #3) > @Yves-Alexis: The commit diff should apply fine to beta 2. Could you check > before and after applying it to your package? Ok, it works fine, thanks!
Ok, I'm marking this one as fixed then.