Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 317939 - [hovering] Expanded vertical ruler icons hover out of reach for the mouse (only when expanding Eclipse window over two monitors!)
Summary: [hovering] Expanded vertical ruler icons hover out of reach for the mouse (on...
Status: RESOLVED FIXED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.7   Edit
Hardware: PC Windows 7
: P3 minor (vote)
Target Milestone: 3.7 M1   Edit
Assignee: Markus Keller CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-06-25 05:49 EDT by Wolfgang Schell CLA
Modified: 2010-06-28 18:50 EDT (History)
2 users (show)

See Also:


Attachments
screenshot showing the problem (19.54 KB, image/png)
2010-06-25 05:49 EDT, Wolfgang Schell CLA
no flags Details
screenshot showing the correct way (19.98 KB, image/png)
2010-06-25 05:49 EDT, Wolfgang Schell CLA
no flags Details
Preferences (36.28 KB, image/png)
2010-06-25 05:50 EDT, Wolfgang Schell CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Wolfgang Schell CLA 2010-06-25 05:49:00 EDT
Build Identifier: 20100617-1415 (final Helios Release)

This is a strange one:
I have streched my Eclipse window over two Monitors (Win7 extended desktop), so that the right monitor has the editors and the console, and Package Explorer and all the small windows are cluttered on the left monitor.

I have checked the option "Expand vertical ruler icons upon hovering" in the Java/Editor/Hovers Preferences, so that multiple markers on the vertical ruler on the left of the Java editor are expanded. 

The expanded hover is placed just above the mouse cursor instead of under it and when I try to move the mouse into it, e.g. to navigate to a overridden method or toggle a breakpoint, the hover closes (see attached screenshot in Editor.png, the mouse cursor is on the breakpoint on the ruler next to line 18). The correct behavior is shown in attached screenshot Editor2.png.

This happens ONLY (as it was in my case), if the left-most pixel of the editor is on the (edge of) left monitor, and the ruler is on the right.

Reproducible: Always

Steps to Reproduce:
1. Create a Java class from the following snippet:
public class MultiHoverTest {
	public static void main(String[] args) {
		Runnable r = new Runnable() {
			public void run() {
				System.out.println("Hello world!");
			}
		};
		r.run();
	}
}

2. Place a breakpoint on declaration of run() method, so that there are two icons on the ruler: breakpoint and Implementation of interface marker.

3. check the option "Expand vertical ruler icons upon hovering" in the Java/Editor/Hovers Preferences (see attached prefs.png)

4. Move the Eclipse window so that it is placed over two monitors (does not need to streched over the whole screen), so that the left editor border is on the left monitor and the ruler on the right (might need to play a little bit with placement, a single pixel may count!)

5. Move mouse to ruler, so that the hover is expanded to show both breakpoint and implementation marker.


Workaround: simply move the editor part one or two pixels to either side.
Comment 1 Wolfgang Schell CLA 2010-06-25 05:49:38 EDT
Created attachment 172730 [details]
screenshot showing the problem
Comment 2 Wolfgang Schell CLA 2010-06-25 05:49:55 EDT
Created attachment 172731 [details]
screenshot showing the correct way
Comment 3 Wolfgang Schell CLA 2010-06-25 05:50:13 EDT
Created attachment 172732 [details]
Preferences
Comment 4 Markus Keller CLA 2010-06-28 09:03:12 EDT
Fixed in HEAD of AnnotationBarHoverManager#computeInformationControlLocation(..).

The hover manager code tries to ensure that the complete hover is visible, is only on 1 monitor and does not overlap the subject area. That's why it jumped to the top. For the expansion hover, this doesn't make sense.
Comment 5 Wolfgang Schell CLA 2010-06-28 18:50:07 EDT
That was fast! Especially for such a minor bug with a (simple) workaround.

I'll test it, when 3.7M1 is released.

Thanks!