Version: KDE4 - Revision 806921 (using Devel) Installed from: Compiled sources OS: Linux I've found a strange combination of files which cause a weird selection. If I select a particular file and I press SHIFT+DOWN for selecting all files from the selected one to the file below, there are two other files which are selected. I'll attach an image as example. This happen on dolphin and in konqueror with the dolphin part.
Created attachment 24745 [details] Screenshot
I can confirm this behavior. I've added Rafael to CC; when turning on the categorization, everything works very well (-> Rafaels KCategorizedView does it right). When turning off the categorization (-> Qt's QListView is used directly), this strange behavior occurs. @Rafael: does http://trolltech.com/developer/task-tracker/index_html?id=199822&method=entry fix this issue too? I'm not sure whether they are related...
No, I'm afraid this bug is not related to http://trolltech.com/developer/task-tracker/index_html?id=199822&method=entry. This task tracker entry was talking about Mouse + Keyboard selection (when it talks about a rectangle on the report, it wants to say a mouse rectangle). This is a different problem, and should be reported separately to TT.
BTW, I can't reproduce with Qt 4.4.0 here.
> BTW, I can't reproduce with Qt 4.4.0 here. Hmm, strange: I tested with Qt 4.4.0 and could reproduce it (only if the categorization is turned off). I'll try to provide a Qt-only example, but this issue has not a high priority currently for KDE 4.1 -> please give me some time... :-)
I can reproduce the bug on dolphin using Qt4.4. @Rafael: what did you do for trying to reproduce the bug?
I can't still reproduce. Please can you retry it ?
I can still reproduce using today's trunk. Even with different files... the selection is messed up.
Maybe it helps: I cannot select items on more than one line, if there are many files in dolhpin. That means you cannot select (with SHIFT or CTRL) more than that one line on which your cursor is... is this the same bug or should I open a new one?
@Chris: please open a new bug, and write a complete explanation which allow us to reproduce it. Thanks!
Created attachment 34152 [details] Qt-only test case To see buggy behaviour in my test case, either 1. Go to an element labeled with "Text" in the first row, press Shift+Down. 2. Go to the bottom right element, press Shift+Up (this is bug 186395). 3. Go to the bottom right element, Shift-Click the element above it (this is bug 194751). In all cases, all elements with wrapped labels are selected in the top row. All these issues might have the same root cause. I think I'll try to find the root cause in Qt and either submit a patch (if I can come up with one in the next few days) or at least my test case to Qt Software.
Sorry, but I copied&pasted an incorrect bug number in my last comment. The right one is (In reply to comment #11) > 3. Go to the bottom right element, Shift-Click the element above it (this is > bug 193447).
Created attachment 34311 [details] Patch for Qt 4.5.1 The attached patch (which I've just submitted with my bug report to Qt Software's task tracker) fixes all three issues (and the analogous problems you get when settings the "Arrangement" of the Icons View to "Columns"). I'll mark the other two reports as duplicates.
*** Bug 186395 has been marked as a duplicate of this bug. ***
*** Bug 193447 has been marked as a duplicate of this bug. ***
Many thanks Frank! I hope that trolls will apply your patch soon :-) !
Created attachment 34329 [details] Another Qt-only test case for analogous issues in QListView::TopToBottom mode ("Columns" alignment in Dolphin's Icons View) I'll upload another test case here so that I can provide a link to the Qt people in my merge request at qt.gitorius.org.
The patch (which I had updated with a new unit test in the meantime) has been accepted for Qt 4.6.0: http://qt.gitorious.org/qt/qt/commit/5539b4ab311501821eb0e971432d769a25000032 I don't know if it's going to be backported to the Qt 4.5 branch. But anyway, I think we can close this report now :-)
*** Bug 203966 has been marked as a duplicate of this bug. ***
*** Bug 205137 has been marked as a duplicate of this bug. ***