fix #277269 Dolphin(Part) Detail/Tree view, highlighted selection paint glitch
Review Request #101924 - Created July 11, 2011 and submitted
What was strange that background highlighting and actual item selection were drawn independently from each other and the bogus highlighting to the left of the item was not cleared... Now this one was a __REAL__ bitch to get dealt with, took me hours and hours bashing my head against the shell ^^ ok now again the viewOptions is not only not the place to turn off background highlighting, but there it was even tried to ENABLE it :O turned out this so called QStyle::SH_ItemView_ShowDecorationSelected documented as "When an item in an item view is selected, also highlight the branch or other decoration." is hard-coded on by DEFAULT in QCommonStyle and all inheriting from there so it requires a QProxyStyle to override the setting. While we have the opportunity, also set SH_ItemView_ArrowKeysNavigateIntoChildren for added joice of keyboard navigation (although strange effect comes up when being on a leaf and pressing Cursor::Right again - but with or without this setting, something with the selection handler...) ...now someone owes me CAKE for this one :D
Thanks again for your investigations. Like for the previous patch: It would only make sense to push it to the 4.7 branch. In this case I'm a little bit concerned to backport such a non-trivial change, but I trust you here. Please do a careful testing especially with the Oxygen-style as this style is used by most people. After fixing the leak I'm fine if this patch gets pushed to the 4.7 branch.
Review request changed
This should have the proxy style destroyed with the treeview instead of leaking it. > would only make sense to push it to the 4.7 branch. What exactly do you mean by 'only'? Isn't 4.7 the branch just about to be released and which will be in all distros until sometime next year? Or am i the only one who has this? couldn't find a bug report about it. Anyways. Also have got my git setup now in case you can't be bothered typing a commit message :)
Revision 2 (+24 -1)
Thanks for the update! >> would only make sense to push it to the 4.7 branch. > What exactly do you mean by 'only'? Isn't 4.7 the branch just > about to be released and which will be in all distros until sometime next year? I meant that this change should only be pushed to the KDE/4.7 and not to master as this class will be removed from master around the beginning of August (Dolphin 2.0...)