Bug 205605

Summary:	"Disconnect-Device"-Button doesn't move on scrolling playlist
Product:	[Applications] amarok	Reporter:	Moritz Isselstein <moeis>
Component:	Collections/Media Devices	Assignee:	Amarok Developers <amarok-bugs-dist>
Status:	RESOLVED DUPLICATE
Severity:	normal	CC:	aikawarazuni, kuba.serafinowski
Priority:	NOR
Version:	2.3-GIT
Target Milestone:	---
Platform:	unspecified
OS:	Linux
Latest Commit:		Version Fixed In:
Attachments:	scrolling error overlapping disconect-buttons

Description Moritz Isselstein 2009-08-29 20:10:20 UTC

Version:           2.2-GIT (using 4.3.00 (KDE 4.3.0) "release 158", KDE:KDE4:Factory:Desktop / openSUSE_11.1)
Compiler:          gcc
OS:                Linux (x86_64) release 2.6.27.29-0.1-default

The "Disconnect-Device"-Button from removable devices in the collections tab doesn't scroll when moving the playlist - it remains on the tab. 

The expected behaviour would be it stuck on the device-panel and disappear together with the device when scrolling down. insted it seems to be attached to the tab itself and doesn't move at all.

When you remove one of two ore more attached devices and you remove the "most upper" one in the collection, the devices move up but the buttons stay where they are. which is tricky when you have 2 or more devices attached. sometimes the buttons even overlap as in one of the screenshots attached.

Attached screenshots for clarification
Umgebung2.png - working state:
http://imagebin.ca/view/LbeAJNpD.html

Umgebung3.png - error on moving:
http://imagebin.ca/view/eSRHWP0m.html

Umgebung4.png - overlapping:
http://imagebin.ca/view/5qt5uC.html

Comment 1 Moritz Isselstein 2009-08-29 20:13:34 UTC

Created attachment 36562 [details]
scrolling error

shoes scrolling error of disconnect-device buttons

Comment 2 Moritz Isselstein 2009-08-29 20:14:42 UTC

Created attachment 36563 [details]
overlapping disconect-buttons

shows overlapping diconnect-device buttons

Comment 3 Kuba Serafinowski 2009-08-29 20:21:18 UTC

confirmed

Comment 4 Seb Ruiz 2009-08-30 02:26:00 UTC


*** This bug has been marked as a duplicate of bug 204566 ***