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.
[ BUILD # : 201109110600 ] [ JDK VERSION : 1.7 ] Value tooltips are not displayed hovering variables in the editor.
I can reproduce as well on Ubuntu 11.04 with 2011/09/13 dev build. I think this should be P1 since this is rather annoying regression.
Works for me correctly on Ubuntu with both JDK 6u27 and JDK 7 using my local today's build. Is it random or can you reproduce the bug all the time?
I'm now using build 201109120600 and the tooltips are showing, but since Miroslav has been able to reproduce the bug with a newer build I'd say it's random. Is there any flag I can set to get more information in messages.log?
Works correctly for me in today's dev build as well so feel free to either close the issue or downgrade it and mark as random. Since I develop mostly on dev builds in case it would reapper I will possibly show Martin E. the problem and we can do some more debugging.
Thanks for the feedback. Closing for now.
It'still happening in build 201109180600
Yes I've seen it in today's build too so I should be able to reproduce it. I'll talk to Martin E. and we'll attempt to resolve the problem.
I've just installed netbeans-trunk-nightly-201109180600-javase.zip created Java project and tooltips works fine for me when I debug that project. Any concrete steps to reproduce? Do you see other tooltips when you finish the debugger session? E.g. create some syntax bug and check if a tooltip is displayed upon the red underline...
I don't see any tooltip in the editor during regular java editing either - I hadn't noticed that. For syntax errors, the tooltips are only shown hovering over the error icons on the left, but not over the red underline. I havent' noticed any regularity in this behaviour: sometimes the editor tooltips are displayed but most of the times they're not.
Right, other tooltips seem also to not appear so I've filed issue #202395. *** This bug has been marked as a duplicate of bug 202395 ***