This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 116165

Summary:	Can't scroll Navigator javadoc popups, nor select text
Product:	java	Reporter:	kirillkh <kirillkh>
Component:	Navigation	Assignee:	Tomas Zezula <tzezula>
Status:	NEW ---
Severity:	blocker	CC:	phrebejk
Priority:	P3
Version:	6.x
Hardware:	PC
OS:	All
Issue Type:	ENHANCEMENT	Exception Reporter:

Description kirillkh 2007-09-20 14:31:58 UTC

When moving the mouse over a class member in Navigator, if its javadoc is long enough, the javadoc window presents a
scrollbar. But I can't find a way to actually scroll it, since as soon as I move the mouse pointer out of the Navigator
window, the pop-up disappears. This also prevents me from selecting text in the javadoc pop-up.

I suggest fixing it by setting a timer (default at 300-500 ms) on mouse exit from the Navigator window. When fired, the
timer would close the pop-up. If mouse pointer enters Navigator or pop-up window again during the delay, the timer
should be canceled. If the mouse is dragged out of the window, only start the timer on mouse_release (this is to handle
the case, when the user unintentionally moves the mouse out of the pop-up, while selecting text inside it).

This kind of pop-ups will also be usable in other places, such as the CVS History (issue #106936), which implies it
should be made generic.

Comment 1 Petr Hrebejk 2007-09-20 15:38:12 UTC

Press Ctrl+F1 to show the javadoc in the javadoc window. It is mentioned on bottom of the javadoc tooltip.

Comment 2 kirillkh 2007-09-20 15:55:00 UTC

I have tried Ctrl-F1 before posting this issue and I don't like opening an additional window each time I need to scroll
the javadoc. Would the proposed fix have a negative impact on anything? If not, then it should be a pure usability
improvement. Since the functionality is accessible through Ctrl-F1, I would understand changing the issue type to
enhancement, but WONTFIX seems inappropriate, unless there is some kind of trade-off involved.

Comment 3 Petr Hrebejk 2007-09-21 10:03:55 UTC

It is not additional window each time it is. Just one window. 

But as you wish, my lord, making it an enhancement. You seem to be pretty confident in what and how to do it. Feel free
to send a patch, I'll be happy to integrate it :-)

Comment 4 Petr Hrebejk 2007-09-21 10:06:10 UTC

Reassigning to you. Feel free to reassign back to me if you don't plan to work on it.

Comment 5 kirillkh 2007-09-21 12:36:48 UTC

I don't quite get the reason for the irony, since no offense was intended. I argued against closing it with WONTFIX only
because I thought it could make an important usability improvement in several GUI components.

Now, regarding your kind offer to send a patch, I will gladly do it, if it is easy enough for me, considering how little
experience I have with the code. So I will take a look, maybe play with it a little and then decide, if I can advance
without external help (or with the kind of help that nbdev can offer). If I can't, I will still do it, if someone with
enough experience and time on hands could be available to answer many little questions over an instant messenger.

To give some background, to the date I already have an unsuccessful experience with fixing a NB module, where I got
stuck due to the complexity of the code (related to MDR), another where no one answered any of the questions on nbdev
(filed as issue #106128) and one more with creating my own module, where the required API wasn't public and the request
to make it public was denied.

Comment 6 Petr Hrebejk 2007-09-21 17:39:36 UTC

Ok, Ok, don't take it personally. I sometimes test how the open source works.

And I agree with you that sometimes it is not easy at all to learn NetBeans APIs and to get help. In this case you are
of course welcome to send the questions to me. I'll try to answer or find someone who knows. 

I did some research and I think it could be doable. Although maybe not easy. It is not much about NetBeans but more
about swing. The right class to look at is org.netbeans.modules.java.navigation.ToolTipManagerEx in the java/navigation
module. If you suceed with getting the ToolTip focused then adding the actual scroll pane with javadoc should not be hard.

Comment 7 kirillkh 2007-09-23 11:12:27 UTC

Now this should be a pretty amusing test, considering you're on a Sun payroll and I am not.