Bug 14549

Summary:	Dolphin panels tied to window
Product:	Mageia	Reporter:	Dennis Nigbur <d.nigbur>
Component:	RPM Packages	Assignee:	Mageia Bug Squad <bugsquad>
Status:	RESOLVED WONTFIX	QA Contact:
Severity:	normal
Priority:	Normal	CC:	doktor5000, lmenut
Version:	4
Target Milestone:	---
Hardware:	All
OS:	Linux
URL:	https://projects.kde.org/projects/kde/applications/kde-baseapps/repository/revisions/5583fc635b1bfc96c096bce6c4fa2c28df4d279f
Whiteboard:
Source RPM:		CVE:
Status comment:

Description Dennis Nigbur 2014-11-14 11:08:55 CET

I used to like having Dolphin's Folders panel outside the main Dolphin window for easy file management - like a floating toolbar. I cannot post a screen shot because this no longer works. According to KDE Docs, it should work: "By unlocking the panels and clicking and dragging a panel title, the panel can be moved to a different position, even outside the window" (https://docs.kde.org/stable/en/applications/dolphin/panels.html).

When I now unlock the panels and try to drag the Folder panel outside the window, it snaps right back into the window. Another Mageia forum user has reproduced the issue: https://forums.mageia.org/en/viewtopic.php?f=7&t=8685

I have already tried deleting dolphinrc, with no success. I am running Mageia 4 with all the latest updates, on a Packard Bell EasyNote TE laptop.

Comment 1 Florian Hubold 2014-11-14 15:33:26 CET

Confirmed and reproduced by at least two people. The same happens with the places panel. It can be separated from dolphin, and moved outside the window - if you let go of the mousebutton, it will snap back to dolphin, not matter if panels are unlocked or not.

CC: (none) => doktor5000, lmenut

Comment 2 Luc Menut 2014-11-16 23:11:08 CET

This feature caused many bugs, and so it was removed upstream.
https://projects.kde.org/projects/kde/applications/kde-baseapps/repository/revisions/5583fc635b1bfc96c096bce6c4fa2c28df4d279f
"Do not allow that panels are dragged out of the main window
This feature might have been useful in some cases, but it's most likely
not useful enough to justify that we accept the bugs that it causes.
Even though some of these bugs are not Dolphin's fault at all, they
cause serious problems for users in some cases."
https://git.reviewboard.kde.org/r/111692/

https://bugs.kde.org/show_bug.cgi?id=288629
https://bugs.kde.org/show_bug.cgi?id=322299
https://bugs.kde.org/show_bug.cgi?id=322812

URL: (none) => https://projects.kde.org/projects/kde/applications/kde-baseapps/repository/revisions/5583fc635b1bfc96c096bce6c4fa2c28df4d279f
Hardware: x86_64 => All

Comment 3 Florian Hubold 2014-11-16 23:50:50 CET

(In reply to Luc Menut from comment #2)
> This feature caused many bugs, and so it was removed upstream.

Shouldn't we close it as WONTFIX then ?

Comment 4 Luc Menut 2014-11-19 00:13:04 CET

(In reply to Florian Hubold from comment #3)
> (In reply to Luc Menut from comment #2)
> > This feature caused many bugs, and so it was removed upstream.
> 
> Shouldn't we close it as WONTFIX then ?

probably, as this can't be fixed downstream by Mageia.

This should be reported upstream at https://bugs.kde.org, if this feature's removal is really problematic for some users.

Status: NEW => RESOLVED
Resolution: (none) => WONTFIX

Comment 5 Dennis Nigbur 2014-11-19 09:22:25 CET

(In reply to Luc Menut from comment #4)

> This should be reported upstream at https://bugs.kde.org, if this feature's
> removal is really problematic for some users.

I understand the reasoning, and it's obviously not a problem to be fixed by Mageia. It also probably doesn't affect many users, and is not a huge problem. 

But if a feature used to work, the documentation says it should work (see my original post), and then it stops working - that's what causes issues. Maybe the documentation should be updated.

Comment 6 Florian Hubold 2014-11-19 18:05:48 CET

(In reply to Dennis Nigbur from comment #5)
> (In reply to Luc Menut from comment #4)
> 
> > This should be reported upstream at https://bugs.kde.org, if this feature's
> > removal is really problematic for some users.
 
> But if a feature used to work, the documentation says it should work (see my
> original post), and then it stops working - that's what causes issues. Maybe
> the documentation should be updated.

Since we don't own that documentation, please see Luc's comment about reporting it upstream.