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 5631 - Explorer tabs are flashing and no tooltip is displayed under JDK1.3 (Occasionally).
Summary: Explorer tabs are flashing and no tooltip is displayed under JDK1.3 (Occasion...
Status: CLOSED WONTFIX
Alias: None
Product: platform
Classification: Unclassified
Component: -- Other -- (show other bugs)
Version: 3.x
Hardware: All All
: P4 normal (vote)
Assignee: David Simonek
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2000-02-03 19:38 UTC by Jan Chalupa
Modified: 2008-12-23 11:49 UTC (History)
0 users

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 Jan Chalupa 2000-02-03 19:38:18 UTC
Occasionally, the Explorer tabs start flashing instead of displaying a tooltip.

Steps to reproduce the problem:

1. In the Explorer Window, select the third or fourth tab (Javadoc or Runtime, by default).
2. Move the mouse pointer to the first or second tab without clicking on it.
3. Wait a moment. The tabs should start flashing.

It seems that (mouse) events are buffered during flashing. The longer you keep the mouse pointer on a tab, the longer it takes to the UI to recover.


The problem could not be reproduced under JDK 1.2.2, so it may be a JDK 1.3 issue only. Classic VM vs. Hotspot makes no difference.

Thread dump attached.
Comment 1 Jiri Kovalsky 2000-07-04 15:09:59 UTC
Explorer is not the only one. The same problem concerns Component Inspector as
well. Failing tab is in this case the last one: "Code Generation". But I found
out that it doesn't matter, what tab is selected.
(Seen on Windows NT)
Comment 2 David Simonek 2000-07-12 14:31:59 UTC
This is clearly JDK problem and I see no possible workaround for it except for
not using tool tips.

*** This bug has been marked as a duplicate of 5610 ***
Comment 3 David Simonek 2000-07-12 14:34:59 UTC
This is clearly JDK problem and I see no possible workaround for it except for
not using tool tips.
Comment 4 David Simonek 2000-07-12 14:36:59 UTC
*** This bug has been marked as a duplicate of 5319 ***
Comment 5 Quality Engineering 2003-07-01 15:53:52 UTC
Resolved for 3.4.x or earlier, no new info since then -> verified.

Comment 6 Quality Engineering 2003-07-01 16:18:31 UTC
Resolved for 3.4.x or earlier, no new info since then -> closing.