Version: 1.99 (using Devel) OS: Linux Dolphin used to have a cross inside a small box in the left panel to indicate theres subfolders (at least when using Plastique, IaOra themes). Now dolphin simply shows arrows to indicate subfolders even when using these same themes and i dont see anywhere an option to configure this... Its pretty annoying to who is used to use the default cross in a small box to now have a arrow and worst, not giving to the user the ability to choose. Can anyone please fix this before next release? Reproducible: Always Steps to Reproduce: Simply run dolphin from master. Actual Results: Dolphin shows a arrow to indicate folders in left panel not respecting theme configurations. Expected Results: Dolphin should continue using the theme options (Plastique,IaOra) that show a cross inside a small box to indicate folders in left panel. OS: Linux (x86_64) release 3.1.5-1.1-desktop Compiler: gcc
*** This bug has been marked as a duplicate of bug 289090 ***
Why have you set this bug as a duplicate of bug 289090 ? These are different bugs.
Both issues have the same root-cause: If one issue is fixed the other one is automatically fixed too. *** This bug has been marked as a duplicate of bug 289090 ***
Sorry: I just read 289090 again and you want the *option* back there and don't care about the arrows vs. crosses thingy...
Im not understanding what you mean. What happens in this bug report is that dolphin isnt respecting the themes style options and only uses arrows in left panel.
And that to me its a different thing from whats reported in the other bug report in which is about dolphin showing arrows (or crosses) in right panel and not giving the user any option to choose. At least before the user had the ability too choose to have or not expandable folders in right panel, and that doesnt happens now.
Could this be merged with #290276 (or #290276 with this bug)? This is the same bug from users point of view: dolphin 2.0 does not respect oxygen-settings.
I mean bug 290276.
Yes, this should be merged: If 290276 is fixed, this bug is fixed too. Thanks for the hint! *** This bug has been marked as a duplicate of bug 290276 ***