Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 333432 - [hovering][projection] ProjectionAnnotationHover uses wrong line count to compute the hover information
Summary: [hovering][projection] ProjectionAnnotationHover uses wrong line count to com...
Status: CLOSED WONTFIX
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Text (show other bugs)
Version: 3.2   Edit
Hardware: All All
: P3 minor with 1 vote (vote)
Target Milestone: ---   Edit
Assignee: Platform-Text-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
: 306145 (view as bug list)
Depends on:
Blocks:
 
Reported: 2011-01-03 11:43 EST by Sebastian Zarnekow CLA
Modified: 2020-03-06 17:17 EST (History)
3 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Sebastian Zarnekow CLA 2011-01-03 11:43:01 EST
Consider the following Java class:

/**
 * 
 * 
 * 
 * 
 * 
 * 
 * 
 *
 */
public class FooBar {

}

If you collapse the leading multi line comment and hover of over the small (+) icon to see the collapsed text, you'll only get the first 4 lines of the comment instead of the full region. Please note also that adding a number of empty lines inside the class body or to the end of the file will increase the number of visible lines in the hover.

I assume the bug is caused by 
org.eclipse.jface.text.source.AnnotationBarHoverManager.computeInformation()
which uses #adaptLineRange to reduce the visible lines in the hover to the number of lines that are currently visible in the source viewer - which may be smaller than the number of folded lines.
Comment 1 Dani Megert CLA 2011-01-03 12:04:13 EST
Broken since 3.2.
Comment 2 Sebastian Zarnekow CLA 2011-01-10 10:09:58 EST
*** Bug 306145 has been marked as a duplicate of this bug. ***
Comment 3 Dani Megert CLA 2011-11-15 05:37:53 EST
Deepak, please investigate.
Comment 4 Eclipse Genie CLA 2020-03-06 17:17:48 EST
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. As such, we're closing this bug.

If you have further information on the current state of the bug, please add it and reopen this bug. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.