Bug 256439 - Media sources view resizes (sometimes) when folder path is too large.
Summary: Media sources view resizes (sometimes) when folder path is too large.
Status: RESOLVED DUPLICATE of bug 246029
Alias: None
Product: amarok
Classification: Applications
Component: general (show other bugs)
Version: 2.3.2
Platform: Ubuntu Linux
: NOR normal
Target Milestone: 2.4.0
Assignee: Amarok Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-11-09 13:45 UTC by vatoslocos
Modified: 2010-11-09 14:06 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description vatoslocos 2010-11-09 13:45:20 UTC
Version:           2.3.2 (using KDE 4.5.3) 
OS:                Linux

When i browse through local files, Media Sources resizes automatically when directory path expands beyond Media Source's width. 
The main problem is that sometimes you cannot make it smaller again.
This bug is extremely annoying if you work on small screen. 
You have to restart amarok, in order to resize Media Sources to its inital size.

Reproducible: Sometimes

Steps to Reproduce:
1. Change the width of media sources (make it small enough).
2. Browse through local files and select a folder with large name.
3. If Media Sources is resized automatically, try to make it smaller again.

It reproduces after bug 256436 (https://bugs.kde.org/show_bug.cgi?id=256436) has been reproduced.

Actual Results:  
Sometimes Media Sources resize to show the folder path.
When it has resized, sometimes you cannot resize it to it's initial width.

Expected Results:  
In my opinion, it shouldn't resize it in first place.
Even if it did, you should be able to make it smaller again.

I have all 3 views (Media Sources, Playlist, Context) enabled.
It doesn't matter if i have enabled "lock layout".

As i mentioned before, it reproduces after bug 256436 (https://bugs.kde.org/show_bug.cgi?id=256436) has been reproduced.
I don't know if it occurs in any other case.
Comment 1 Myriam Schweingruber 2010-11-09 14:06:31 UTC

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