Bug 136419 - Tooltip not shown when track name partly obscured by queue number
Summary: Tooltip not shown when track name partly obscured by queue number
Status: RESOLVED INTENTIONAL
Alias: None
Product: amarok
Classification: Applications
Component: general (show other bugs)
Version: 1.4.5
Platform: Debian testing Linux
: LO normal
Target Milestone: ---
Assignee: Amarok Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-10-28 16:00 UTC by Reuben Thomas
Modified: 2008-06-16 16:55 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Reuben Thomas 2006-10-28 16:00:00 UTC
Version:           1.4.1 (using KDE KDE 3.5.5)
Installed from:    Debian testing/unstable Packages
OS:                Linux

The tooltip for track name in the playlist is only shown if the track name is wider than the column. Unfortunately, this misses the case when the track name fits in the column, but is partly obscured by a queue number because the track is queued for playing.
Comment 1 Kevin Funk 2007-02-08 18:54:19 UTC
I can confirm this but i wouldn't say this is a bug. Close this?
Comment 2 Reuben Thomas 2007-02-09 01:27:39 UTC
I don't understand why this is not a bug. Under other circumstances you can
read the track name (either because it's not obscured, or because the 
tooltip is shown. In this one special case, it's not possible to read the   
full track title. You could be missing arbitrarily many characters depending
on how many tracks are queued.
Comment 3 Edward Hades 2008-06-15 17:49:12 UTC
Amarok 1.4.x is in bugfix-only mode as development is focused on Amarok 2. Unfortunately your bug will very likely not get fixed, as the risk of regressions is too high and the Amarok developers do not have the resources for it. Thank you for your report though. Please don't hesitate to report new bugs should you have any problems with Amarok 2 once it is released.
Comment 4 Edward Hades 2008-06-16 16:55:05 UTC
Alas, this bug won't get fixed in 1.4 branch. Thanks for your report.