https://bugs.kde.org/show_bug.cgi?id=385012
--- Comment #8 from RJVB ---
Funny, I was thinking of such a solution
- then thought that problem reports can be long so the context popup should be
on top to avoid losing it somewhere offscreen
- then realised some context popups are long too
Can
https://bugs.kde.org/show_bug.cgi?id=385012
Francis Herne changed:
What|Removed |Added
Status|CONFIRMED |RESOLVED
CC|
https://bugs.kde.org/show_bug.cgi?id=385012
--- Comment #6 from Francis Herne ---
There's a patch for this on Phab: https://phabricator.kde.org/D18229
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=385012
--- Comment #5 from RJVB ---
Could you think of a workaround that's quicker to implement? Like a context
menu action, e.g.
- that opens the problem reporter view at the corresponding line
- or opens the popup that's now being preempted (from the
https://bugs.kde.org/show_bug.cgi?id=385012
--- Comment #4 from Sven Brauch ---
My last plan regarding this was to use the inline annotation interface to
display error messages (similar to how QtCreator does it, but less intrusive
probably, just an exclamation mark you can mouseover). Sadly, I
https://bugs.kde.org/show_bug.cgi?id=385012
--- Comment #3 from RJVB ---
Created attachment 118283
--> https://bugs.kde.org/attachment.cgi?id=118283=edit
example screenshot
Any progress on this?
Attached is an example where this is really annoying. Code I just want to get
to compile so the
https://bugs.kde.org/show_bug.cgi?id=385012
Sven Brauch changed:
What|Removed |Added
CC||m...@svenbrauch.de
---
https://bugs.kde.org/show_bug.cgi?id=385012
Milian Wolff changed:
What|Removed |Added
Ever confirmed|0 |1