[kdevelop] [Bug 385012] counterproductivity: semantic analysis issues preempt code context popups

[RJVB]

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 this be merged (easily) into the 5.3, (pretty) please?

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdevelop] [Bug 385012] counterproductivity: semantic analysis issues preempt code context popups

[Francis Herne]

https://bugs.kde.org/show_bug.cgi?id=385012

Francis Herne  changed:

   What|Removed |Added

 Status|CONFIRMED   |RESOLVED
 CC||m...@flherne.uk
 Resolution|--- |FIXED

--- Comment #7 from Francis Herne  ---
In fact, that was merged:

This should be fixed after
https://commits.kde.org/kdevelop/2071db63b3fb4172f112356b6d531aae75de5da8

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdevelop] [Bug 385012] counterproductivity: semantic analysis issues preempt code context popups

[Francis Herne]

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.

[kdevelop] [Bug 385012] counterproductivity: semantic analysis issues preempt code context popups

[RJVB]

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 context browser I
think?)
- or toggles a switch which controls which of the two is seen (which could be
both when you have a big screen)

In fact, I've often wondered why the problem popup is triggered everywhere on
the line, while the other popup is more context sensitive. IMHO the most
logical thing to do would be to let the context browser popup preempt the
problem popup. Even if that means that the problem reporter has to check if no
one else could try to show a popup; a priori that'd be a bit of code that can
be marked as a temporary workaround.

I know workarounds aren't always appreciated around here and don't disagree in
principle ... but there are times where you have accept compromises for the
sake of productivity (and this'd be one, IMHO).

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdevelop] [Bug 385012] counterproductivity: semantic analysis issues preempt code context popups

[Sven Brauch]

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 currently have
about no time to work on anything related. :(

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdevelop] [Bug 385012] counterproductivity: semantic analysis issues preempt code context popups

[RJVB]

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 lack of a shortcut into the class definition that doesn't
provide the expected message is really handicapping here.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdevelop] [Bug 385012] counterproductivity: semantic analysis issues preempt code context popups

[Sven Brauch]

https://bugs.kde.org/show_bug.cgi?id=385012

Sven Brauch  changed:

   What|Removed |Added

 CC||m...@svenbrauch.de

--- Comment #2 from Sven Brauch  ---
I think we should just show both popups, like we do in the debugger (one below
the other). The code for that already has to be somewhere ...

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdevelop] [Bug 385012] counterproductivity: semantic analysis issues preempt code context popups

[Milian Wolff]

https://bugs.kde.org/show_bug.cgi?id=385012

Milian Wolff  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|UNCONFIRMED |CONFIRMED

--- Comment #1 from Milian Wolff  ---
I've seen this myself, Kevin, Sven - any idea's on how to handle this?

-- 
You are receiving this mail because:
You are watching all bug changes.