Community
Participate
Working Groups
Created attachment 109393 [details] popup shown instead of javadoc Build ID: I20080617-2000 Steps To Reproduce: Write a line of code in the editor: Collection tmp = new ArrayList(); When you hover over either Collection or ArrayList to see the javadoc, the 'multiple markers' popup interferes and does not display an option to see the javadoc. You only get: ArrayList is a raw type. References to generic type ArrayList<E> should be parameterized 3 quick fixed are available: - Add type parameters to arraylist - Infer generic type arguments.. - Add @suprress warning More information: Usability issue - would be better to either show javadoc in a popup next to the popup of suggestions, or give an option to show the javadoc when I press F2.
Problems have higher weight than Javadoc. This is by design and won't be changed. If you always want to see Javadoc, you can choose this in the preferences or assign a modifier to the Javadoc hover (modifer+hovering will then always show the Javadoc for you).
How do I set to always see javadoc?
(In reply to comment #1) > Problems have higher weight than Javadoc. This is by design and won't be > changed. > > If you always want to see Javadoc, you can choose this in the preferences or > assign a modifier to the Javadoc hover (modifer+hovering will then always show > the Javadoc for you). > These are warnings, not errors. Thus although they have a higher weight I can choose to ignore them. I still think there should be an option when I press F2 to also redirect me to the javadoc. Either by pressing F2 again or via link/icon. This is very annoying when debugging code or even in development. So I hope you would reconsider. For now, how do I set the two options you mentioned?
Java > Editor > Hovers.
We could add a link or button to the problem hover.
Can't we simply cycle through various hovers, something similar to the content assist popup ?
(In reply to comment #6) > Can't we simply cycle through various hovers, something similar to the content > assist popup ? How often do you have that issue besides the problem mentioned here?
I can think of one more case at this point - while debugging you see the debug hover for fields, but you may also be interested in Javadoc hover.
Maybe the best match hover could just add a button to the rich hover toolbar to replace the current hover with the next best hover.
Yeah, we could just add 'Next' and 'Previous' buttons. Luxury solution would also offer a hover on those buttons.
Another luxury would be a key binding to go to the next hover. We can use F2 for this.
