Bug 313206

Summary:	add copy + select feature to use report
Product:	[Developer tools] kdevplatform	Reporter:	Andreas Pakulat <apaku>
Component:	contextbrowser	Assignee:	kdevelop-bugs-null
Status:	CONFIRMED ---
Severity:	wishlist	CC:	kfunk
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Other
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Andreas Pakulat 2013-01-13 20:56:11 UTC

This is a regression I believe introduced during the refactoring to make the output of the uses widget a bit nicer. Its not possible (anymore) to click anywhere in a line to jump to the found location. One can only click on the "Line xy" part to jump.

Please downgrade the priority if I was wrong about the regression part.

Reproducible: Always

Steps to Reproduce:
1. Let the contextbrowser search for uses
2. Try to click a found use in the middle or end of the line
3.
Actual Results:  
Nothing happens.

Expected Results:  
Jump to the line of use found.

Comment 1 Kevin Funk 2013-01-31 20:52:03 UTC

Actually, I think this is not a bad thing.

The much worse part about the current show uses widget is that you cant select/copy the contents.

What do you think?

Comment 2 Milian Wolff 2013-01-31 21:40:16 UTC

I think both should be done. But please create a second bug report for copy abilities in the "show uses" dialog.

Also note that this bug I'd like to fix by using a proper tree model. Those are known to be tricky when it comes to select all/copy actions. But its doable, just a bit more code...

Comment 3 Milian Wolff 2016-09-07 20:41:15 UTC

still valid, would be nice to see this improved. the styling should ideally stay the same, just with the capability to click on the whole line. I'll try and see if I can fix that with a bit of CSS.

Comment 4 Milian Wolff 2016-09-07 21:11:09 UTC

Git commit 54113eb4ed975e682cf98fbcee5dffd5f43e250e by Milian Wolff.
Committed on 07/09/2016 at 21:11.
Pushed by mwolff into branch '5.0'.

Navigate to use when clicking anywhere in a use report line

The code for the use report is incredibly ugly and really needs
to be cleaned up. We could probably get away with generating a
single HTML report and use that for all matches, instead of
generating one widget (with two labels) per use, each with its
own HTML inside...

Doing it all in one document would also allow us to easily implement
a select + copy action.

M  +16   -8    language/duchain/navigation/useswidget.cpp
M  +2    -3    language/duchain/navigation/useswidget.h

http://commits.kde.org/kdevplatform/54113eb4ed975e682cf98fbcee5dffd5f43e250e