Community
Participate
Working Groups
Build Identifier: I20110613-1736 When I use the quickfix hover menu once it works perfectly fine (for example adding throws clause to method). When i want to use it again the menu shows up. But as soon i hover it with the mouse it disappears again. However when i switch workspaces in the window manager once it works again. Reproducible: Sometimes Steps to Reproduce: 1. use the quickfix hover menu 2. try to use it a second time somewhere else 3. the hover menu disappears as soon the mouse enters the boundaries of the menu
Sorry forgot to mention: I use Linux with the i3 windowmanager
I assume you hover over the warning in the editor? Anything in .log? What is value of the 'When mouse moved into hover' preference on General > Editor > Text Editor?
> I assume you hover over the warning in the editor? Yes I hover the warning in the editor. > Anything in .log? Sorry did not know there is a log file existing. I did tail -f /path/to/.log but no messages appeared while this error ocurred. I will upload the logfile anyway. > What is value of the 'When mouse moved into hover' preference on General > Editor > Text Editor? Setting is "Enrich after delay".
Created attachment 217154 [details] logfile as mentioned in comment 3
(In reply to comment #3) Can you try with our latest build: http://download.eclipse.org/eclipse/downloads/drops/S-3.8RC4-201206081200/
Same issue with that build
ok i noticed some things: -> if i have a different window that eclipse selected the current tab turns gray -> saving is not possible when i select one of this quickfixes a second popup box pops up that allows me to select the exception type (if i fix a throw-clause error). In the same turn the current tab turns gray -> this exception select box has focus. now even if i click into the editor somewhere again the tab still stays grey. however if i switch workspaces or windows once the tab text gets black again and the hovering of the autocompletation works again. Hope it helped.
(In reply to comment #7) > ok i noticed some things: > > -> if i have a different window that eclipse selected the current tab turns > gray > -> saving is not possible > when i select one of this quickfixes a second popup box pops up that allows me > to select the exception type (if i fix a throw-clause error). In the same turn > the current tab turns gray -> this exception select box has focus. now even if > i click into the editor somewhere again the tab still stays grey. however if i > switch workspaces or windows once the tab text gets black again and the > hovering of the autocompletation works again. > > Hope it helped. Do you have some special mouse settings, e.g. focus follows mouse pointer? Deepak, please try on your Linux box.
(In reply to comment #8) > Deepak, please try on your Linux box. I cannot reproduce the problem, probably because I do not have i3 windowmanager?
Erik, can you try with a different window manager?
> Do you have some special mouse settings, e.g. focus follows mouse pointer? Yes on i3 the focus follows mouse. It works fine in Unity
(In reply to comment #11) > > Do you have some special mouse settings, e.g. focus follows mouse pointer? > Yes on i3 the focus follows mouse. > > It works fine in Unity That explains it. Same problem as reported in bug 161986. *** This bug has been marked as a duplicate of bug 161986 ***
Hm. For me it looks different. The window does not disapear if i leave its boundaries but if i ENTER the boundaries. Which makes the window completly unusable.
I believe I'm getting the same issue, but with gnome-flashback-session and Ubuntu 14.04. There's 2 ways I noticed which prevent the hovering menu from disappearing: - Using the F2 key, which changes the menu into a slightly different looking one that stays and behaves properly. - Moving the mouse cursor quickly enough into the hover window's content area helps often, same results as with F2 when successful. I initially thought it was a sporadic issue, but it seems to be dependend on where the mouse position is being sampled while moving it, possibly getting lost in the gap between cursor and quick fix window?
(In reply to Marco Klemm from comment #14) > I initially thought it was a sporadic issue, but it seems to be dependend on > where the mouse position is being sampled while moving it, possibly getting > lost in the gap between cursor and quick fix window? You're probably running into bug 490933, which I just fixed a moment ago. It's hard to tell what's going on when it hits you, because that bug depends on the exact path *and* speed of the mouse movements, and only happens with certain widget positions.
> You're probably running into bug 490933, which I just fixed a moment ago. > It's hard to tell what's going on when it hits you, because that bug depends > on the exact path *and* speed of the mouse movements, and only happens with > certain widget positions. I have still the same issue with Oxygen.2 Release (4.7.2) Build id: 20171218-0600 But for me it is ,,always reproducable''. Reproducible: Always Steps to Reproduce: 0. Use any windows manager (KDE,xmonad,gnome ...) with ,,focus follow mouse''. 1. use the quickfix hover menu 2. the hover menu disappears as soon the mouse enters the boundaries of the menu Workaround with F2 works. Within KDE/Plasma you can choose ,,Activation below Mouse'' instead the ,,Activation exactly below mouse'' (X11 standard).
(In reply to Dani Megert from comment #12) > (In reply to comment #11) > > > Do you have some special mouse settings, e.g. focus follows mouse pointer? > > Yes on i3 the focus follows mouse. > > > > It works fine in Unity > > That explains it. Same problem as reported in bug 161986. > > *** This bug has been marked as a duplicate of bug 161986 *** Bug 161986 ==> windows closes when you *leave* the menu,this is the expected behaviour, no bug. In this bug report the windows disappears when you *enter* the menu. So it is not a duplicated bug.
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. If you have further information on the current state of the bug, please add it. 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.
