Bug 186395 - wrong selection when file names are big
Summary: wrong selection when file names are big
Status: RESOLVED DUPLICATE of bug 162030
Alias: None
Product: dolphin
Classification: Applications
Component: general (show other bugs)
Version: 16.12.2
Platform: Debian testing Unspecified
: NOR normal
Target Milestone: ---
Assignee: Peter Penz
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-03-06 21:38 UTC by Daniel Nicoletti
Modified: 2009-06-06 01:02 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Daniel Nicoletti 2009-03-06 21:38:07 UTC 
Version:            (using KDE 4.2.0)
Installed from:    Debian testing/unstable Packages

the screen shot explains this much better, when you have
large file names they get selected..
i simply pressed SHIFT + (the down arrow) over the selected item was 5
but both "4 ola meu..." were wrongly selected...
if you need more explanation please ask

http://img16.imageshack.us/my.php?image=dolphinbug.png
Comment 1 Peter Penz 2009-03-07 00:05:53 UTC 
Thanks for the report. Is the issue really related to long filenames? The selection mechanism does not differ between short and long filenames, so I'm wondering...

I currently cannot reproduce this issue, do you know which Qt version you are using? I know there was a related Qt bug some time ago, but this should have been fixed already.
Comment 2 Daniel Nicoletti 2009-03-07 01:06:58 UTC 
i'm using Qt 4.4.3,
from my point of view seems that any file that has a second line get's selected, it is like it was calculating the selection using a ruler, this does not happen with short names.
kde 4.2.0 and i tested it on my laptop with very similar packages (same issue..)
Comment 3 Frank Reininghaus 2009-05-31 14:27:18 UTC 
I can reproduce this in 4.2.3 (Qt 4.5.0) and current trunk (Qt 4.5.1). I think it's probably a duplicate of bug 162030.
Comment 4 Frank Reininghaus 2009-06-06 01:02:44 UTC 

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