Version: (using KDE 4.2.0) OS: Linux Installed from: Unspecified Linux 1. Right-click an entry in the places panel 2. click on the main window (the area where the files are listed) Doing the steps above, results Dolphin in leaving the right-clicked entry highlighted, until you move the mouse over another entry thanks
can someone please assign this bug to dolphin? (or the apropriate product)
Confirmed in KDE 4.4.5 and 4.5.0
Created attachment 56207 [details] PyQt TestCase indicating this is a QT issue This seems to be a Qt bug. I attached a PyQt test case, which uses a simple QListWidget. Beware, the selection behaviour is different from the Panel, but the bug is still visible: First, notice there are different colors for (a) selected Item and (b) selected and hovered item, the latter is slightly lighter. Now, right-click on an item in the list to open the context menu, move the mouse out 2of the window and click there to close the context menu again. The color for the item you originally right-clicked stays at "selected and hovered". Only when you bring the mouse back into the widget, the color changes to "selected and NOT hovered". This is exactly the same behaviour as in the places panel. Could someone confirm this, or is there any error in usage of the QListView? I didn't find a corresponding Qt bug report yet. If anyone can confirm this, feel free to search for and possibly create a new Qt bug report with the test case.
Nice test case, looks good to me! (In reply to comment #3) > is there any error in usage of the QListView? I don't think so. > I didn't find a corresponding Qt bug report yet. If anyone can confirm this, > feel free to search for and possibly create a new Qt bug report with the test > case. I think you should report this yourself - the Qt people might have questions concerning your test case which you could answer best. Some remarks: 1. It might be worth investigating if this also happens in other item views (like, e.g., QTreeView/QTreeWidget). This might tell you if the problem is in QListView or in its base class QAbstractItemView. 2. The best way to get a Qt bug fixed quickly is to not only report it, but also provide a merge request with a patch+unit test at Qt's Gitorious site. If you can figure out what goes wrong and how it could be fixed, you could try this. If you have any questions concerning that, just ask me, I've submitted a couple of merge requests already.
Qt bug is http://bugreports.qt.nokia.com/browse/QTBUG-16872 I didn't come around to look for the cause yet.