Community
Participate
Working Groups
At some point in the last few releases, it became possible to auto-focus on a tooltip by moving the mouse over it. This functionality is great, but it is rather clunky without the ability to subsequently scroll the tool tip using the mouse wheel. Here is an example scenario: 1. I'm editing a C++ document. 2. I hover over a function call. 3. A tooltip appears showing the source for that function, only all I can see is the comment header. 4. I move the mouse slightly so thatt the tooltip gains the focus. 5. I want to use the mouse wheel to scroll down to the actual function so I can see the information I'm after. 6. Unfortunately, what happens is that the scroll wheel scrolls the main document, so that my tooltip disappears. Because I automatically use the scroll wheel everywhere else, I perform these sequence of steps all the time without thinking, meaning regularly have to go over the whole sequence twice and then go over to the scroll bar & use it. Joe
Note when the tooltip gains focus (step 4) the caret is still visible in the editor (meaning the editor has the focus). Mouse wheel events are send to the focus control. Alternatevely, you can use F2 to give focus to the tooltip, or click on it. That will actually give focus the tooltip window and the mouse wheel will work then.
It works if you use a mouse driver that allows to scroll the widget under the cursor. We already discussed this. We could try to forward the scroll events but we do not want to give the focus to the hover.
(In reply to comment #2) > We already discussed this. We could try to forward the scroll events but we do > not want to give the focus to the hover. Could you not add the scrollbars in the tooltip window till it actually gets the focus (ie. user presses F2 or clicks on window) ?
>Could you not add the scrollbars in the tooltip window Well they are there already. Not sure what you mean.
See bug 75766. I would mark this as a dup (and maybe add a preference on Windows to fix the broken native behavior).
*** This bug has been marked as a duplicate of bug 75766 ***
