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 119247 - [60cat] editor tooltips for undefinded variables
Summary: [60cat] editor tooltips for undefinded variables
Status: RESOLVED WONTFIX
Alias: None
Product: editor
Classification: Unclassified
Component: Actions/Menu/Toolbar (show other bugs)
Version: 6.x
Hardware: PC Linux
: P3 blocker (vote)
Assignee: issues@editor
URL:
Keywords:
: 120318 (view as bug list)
Depends on:
Blocks:
 
Reported: 2007-10-17 16:46 UTC by Unknown
Modified: 2009-11-02 10:59 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Unknown 2007-10-17 16:46:27 UTC
[ BUILD # : 200710150000 ]
[ JDK VERSION : 1.6.0_02 ]

Product Version: NetBeans IDE Dev (Build 200710150000)
Java: 1.6.0_03; Java HotSpot(TM) Client VM 1.6.0_03-b05
System: Linux version 2.6.22.9-slh-smp-1 running on i386; UTF-8;
en_US (nb)
Userdir: /home/sasbeb/.netbeans/dev

tooltips showing undefined variable names (ie foo is undefined, blah
blah, blah) not going away even after hitting esc.

Typically, the code is cut and pasted into the editor and tips show
up before I can fix the typo.
Iterestingly enough, the tooltip accepts keyboard focus (shows the
caret).  I tried typing and of course it through an exception.
Comment 1 Jiri Prox 2007-10-18 07:40:40 UTC
Can you attach screenshot of the problem and stacktrace?
Thanks

Comment 2 Vitezslav Stejskal 2007-10-18 12:44:37 UTC
Tooltips work fine for me.
Comment 3 Unknown 2007-10-18 18:20:28 UTC
Then it works for everyone ;)
If I can reproduce it, I will and give the snapshot and stack trace.
"Truth is stranger than fiction"
I can't be making this stuff up;)
Comment 4 Vitezslav Stejskal 2007-10-19 09:32:59 UTC
Thanks sasbeb, I didn't say you made it up. ;-) Sometimes strange defects are reported that can only be reproduced under
certain conditions. Hunting them down can be frustrating experience for both the reporter and the developer. The first
one can clearly see the defect while the other can't and has no clue what the hell could be wrong. Well, as you said,
sometimes 'Truth is stranger than fiction'. Cheers,
-vita
Comment 5 Jan Lahoda 2008-03-13 17:01:09 UTC
*** Issue 120318 has been marked as a duplicate of this issue. ***
Comment 6 Jiri Prox 2008-04-11 00:43:04 UTC
moving opened issues from TM <= 6.1 to TM=Dev
Comment 7 Max Sauer 2008-11-18 09:00:06 UTC
We will have a look at this LATER.
Comment 8 Unknown 2008-11-18 12:05:58 UTC
How is this resolved?
Comment 9 Max Sauer 2008-11-18 12:14:49 UTC
http://wiki.netbeans.org/IssueLifeCycle#section-IssueLifeCycle-EvaluatingIssues says:

> Use LATER resolution for issues that we don't plan to fix in this neither next release.

That's what we're planning to do, sorry -- it does not mean the issue does not exist, however until this issue is somehow clarified or reproduced, there's 
not much to do.
Comment 10 Quality Engineering 2009-11-02 10:59:31 UTC
NetBeans.org Migration: changing resolution from LATER to WONTFIX