This bug is created in addition for bug 31733.
Steps to reproduce:
1. Open generated servlet for JSP file.
2. Select some variable and press Ctrl+1 to see properties
3. Click twice on method name.
4. Click twice on variable again.
Result: Properties window updated only after ~ 1,5 - 2
seconds. I think it's too slow.
Reproduced with build 030311 under W2k.
I have following configuration: P-IV 1800 Mhz, 512 RAM.
Properties windows should be implemented somewhere in openide/core.
Reassigne to Tim for evaluation.
Some additional delaying was added to property sheet recently as
a performance optimization (so keyboard navigation in explorer -
as in holding down the down arrow) isn't slow and choppy because
the property sheet is rebuilding its component tree hundreds of
With the property sheet rewrite, the infrastructure will be much
more lightweight, offering, ideally, almost no object creation to
update the sheet. Thus it will probably be possible to reduce the
delay without incurring overhead - far less work will be done to
display the properties of a node.
There is also the matter that the nodes in question may do
inordinate work to build their property sets - I don't know.
Scheduling for 4.0. Also ccing Jiri Rechtacek, who made related
changes in prop sheet code. Thx.
Fixed - property sheet rewrite integrated. IMO the
the timing values for this are reasonable, and performance
should be a little better with the new property sheet.
Reopen. The same situation with new property sheet.
Cc'ing Jano from the UI team, changing category to UI.
The delay in changing the property sheet to display the new node
is *by design* - it is intentional. The reason: If the user
is rapidly navigating either a file (the selected node changes
every time the caret enters a new method) or when the user is
rapidly navigating in a tree (again, holding down the up arrow
or something such), performance is degraded if the property sheet
is repainting many times per-second.
The timings can be changed, and it may be that with the new property
sheet, which is lighter-weight, we can probably speed it up a bit.
Please discuss this with the UI folks regarding appropriate
timings. Bear in mind that some compromise is necessary
I've reduced the secondary delay from 350ms to 150ms. Hopefully
that will satisfy :-)
Checking in PropertySheet.java;
a,v <-- P
new revision: 1.123; previous revision: 1.122
Processing log script arguments...
Mailing the commit message to email@example.com (from
verified in [nb_dev](200406291800)