Version: (using KDE KDE 3.2.0) Installed from: SuSE RPMs OS: Linux When browsing files in a save or open dialog with the up and down keys some files are sometimes randomly skipped. Sometimes it can skip dozens of files at once but usually just one or two. The files it skips seem random. In some cases when I go back with the up button it skips back to where it was, sometimes it doesn't. This bug was present in KDE 3.1.4 that came in SuSE 9.0 as well as the official 3.2 SuSE RPM release which I'm running now.
I smell a "Qt bug" in the air...
Why this bug was previously just closed as invalid (Bug 54727)? Doesn't sound invalid to me. This bug renders "short view" mode in file save/open dialog unusable. I'm seeing this bug with KDE 3.2.2 & QT 3.3.1
This is really funny, I can confirm this.
It was closed as INVALID because it is a Qt bug and not a KDE one
*** Bug 110056 has been marked as a duplicate of this bug. ***
This is still a problem in KDE 3.5.2 with QT 3.3.6 (current Debian unstable)
*** Bug 133116 has been marked as a duplicate of this bug. ***
This is indeed a Qt bug -- QIconView handles keyboard movement by searching vertically from currentItem().rect().center(), which causes the "skipping" effect when the following item is narrower than currentItem().width()/2.
I tried to test the currentItem().width()/2 statement in comment #8, by cycling through the JPG-images in /usr/share/wallpapers. It skips a file even though that filename has more than half the amount of characters as the last. E.g. when "Totally-New-Product-1.jpg" is selected, and I press arrow down, it skips "triplegears.jpg", and lands on "Won-Ton-Soup-3.jpg". Btw., since I was not sure that this had been reported as a QT bug, I submitted a Debian bug report (408092). Its status is now "Forwarded". I included a link to this thread.
Any progress on this bug? Regardless of whether this is a qt bug or kde bug, there should be more ruckus around it. This is a very typical example of the small things that makes kde look really bad when showing it to others. It is of course also a major showstopper when you try to efficiently keyboard-navigate kde and you are forced to reach for the mouse.
can someone indicate whether this is likely to be fixed in qt4 and therefore kde4? this is a pretty outrageous bug
This seems to be indeed fixed with the Qt 4.3. I can still reproduce it with KDE3, but can not under KDE4.