-
Enhancement
-
Resolution: Duplicate
-
P4
-
None
-
1.3.1
-
x86
-
linux
Name: gm110360 Date: 07/17/2002
FULL PRODUCT VERSION :
java version "1.3.0"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.0)
Classic VM (build 1.3.0, J2RE 1.3.0 IBM build co130-20020124 (JIT enabled: jitc)
)
FULL OPERATING SYSTEM VERSION :
The Operating System/2 Version is 4.50
A DESCRIPTION OF THE PROBLEM :
In cases where calls to getToolTipText(MouseEvent) are
expensive (in my case, I retrieve data from a database) and
ToolTipManager.getInitialDelay() is high (2-3 seconds) it
makes no sense for ToolTipManager to call getToolTipText()
immediately.
Running the mouse back and forth across my data, I get
hundrends of calls to getToolTipText(), only to have the
tooltip pop up a second later. Those hundrends of calls are
expensive.
My request is to add a new variable (or modify the algorithm
based upon the preexisting variables) such that:
1) The user has the ability to control how long
ToolTipManager waits before calling getToolTipText(), or
2) ToolTipManager is smart enough to not call
getToolTipText() excessively, or
3) ToolTipManager waits until initialDelay expires, THEN
called getToolTipText()
Personally I prefer options 1 or 3. Option 1 gives the
end-user the greatest amount of flexibility depending upon
the complexity of his function.
This bug can be reproduced always.
(Review ID: 145967)
======================================================================
- duplicates
-
JDK-4293264 ToolTipManager causes serious hit in perfomance (getToolTipText)
-
- Resolved
-