Version: (using KDE 4.2.2) OS: Linux Installed from: Debian testing/unstable Packages Some lines in "First Matching Line" in KFinds are truncated altough there exists more space to show them. Best seen in the screenshot attached.
Created attachment 33061 [details] Screenshot with an example.
- Could you retest this on KDE SC 4.3 / 4.4 ? I did some changes to the treeview and I can't reproduce the bug with KDE SC 4.5trunk Regards
(In reply to comment #2) > - Could you retest this on KDE SC 4.3 / 4.4 ? I did some changes to the > treeview and I can't reproduce the bug with KDE SC 4.5trunk > Regards Hi, I cannot reproduce the exact conditions, but the bug seems mostly gone. There is still a small difference between the cut-off limits. Please take a look at the new screenshot and decide if this a bug. Notice that some lines are cut earlier than others.
Created attachment 40911 [details] New screenshot
- If, in the treeview header, you double-click the line at the left of the "First Matching Line" column (to autoexpand it), does the problem "dissapear" ? I just double checked the code, and the matching line is not getting chopped... so it may be a widget-style issue Regards
- Also, could you try this using different widget styles ? (launch KFind from Konsole as "kfind -style plastique" or "kfind -style oxygen")
Hi, i forgot to mention that I run 4.3.4 from Debian, and not something newer. So I did: 1. Click on the header at the left of "First matching line". This doesn't autoexpand any column, I guess it is a newer Qt feature than my 4.5.3. The truncation is still there. 2. Try other styles, and the situation is just the same. I'll try to remember to come back when I have a newer KDE or Qt.
> So I did: > 1. Click on the header at the left of "First matching line". This doesn't > autoexpand any column, I guess it is a newer Qt feature than my 4.5.3. The > truncation is still there. You need to *double-click* the "vertical line" (separator) between the two column headers ("First matching line" and the one to the right of it) (sorry, I said "left" instead of "right" in the previous message)
(In reply to comment #8) > > So I did: > > 1. Click on the header at the left of "First matching line". This doesn't > > autoexpand any column, I guess it is a newer Qt feature than my 4.5.3. The > > truncation is still there. > > You need to *double-click* the "vertical line" (separator) between the two > column headers ("First matching line" and the one to the right of it) (sorry, I > said "left" instead of "right" in the previous message) I see, I got it, I needed to double click on the _line_ not on the _header_. Yes, this expands that column. Anyway, I'm satisfied with the current behaviour and I'm just signalling the potential issue, loosing 2-3 characters is not that important.
I was wondering if we could remove the start/end whitespaces from the line, so situations like you showed in the second image should not happen that much oftenly. Regards
In recent 4.5 and trunk compiled from sources I don't have this bug anymore: branch: kfind --version Qt: 4.6.3 KDE: 4.4.93 (KDE 4.4.93 (KDE 4.5 >= 20100713)) KFind: 2.0 trunk: kfind --version xxQt: 4.6.2 KDE Development Platform: 4.5.60 (KDE 4.5.60 (KDE 4.6 >= 20100627)) xxKFindxx: 2.0 xx
Dear Bug Submitter, This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond. Thank you for helping us make KDE software even better for everyone!
Dear Bug Submitter, This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? This bug will be moved back to REPORTED Status for manual review later, which may take a while. If you are able to, please lend us a hand. Thank you for helping us make KDE software even better for everyone!
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version? If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!