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 27782 - Navigation in form component inspector is slow
Summary: Navigation in form component inspector is slow
Status: RESOLVED FIXED
Alias: None
Product: guibuilder
Classification: Unclassified
Component: Code (show other bugs)
Version: 3.x
Hardware: All All
: P3 blocker (vote)
Assignee: issues@guibuilder
URL: http://performance.netbeans.org/respo...
Keywords: PERFORMANCE
Depends on:
Blocks: 26581
  Show dependency tree
 
Reported: 2002-10-03 15:51 UTC by _ rkubacki
Modified: 2004-04-02 13:20 UTC (History)
3 users (show)

See Also:
Issue Type: TASK
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description _ rkubacki 2002-10-03 15:51:01 UTC
component inspector can't match the speed of
keyboard autorepeat, when arrow key is hold.
Probably caused by instant redrawns of form itself.
Comment 1 Tomas Pavek 2002-10-03 16:02:17 UTC
Radim - enter these issues as tasks please...
Comment 2 _ pkuzel 2002-11-18 13:11:01 UTC
Is it really toppish responsiveness issue? Trung, I'll 
update the document until you object. 
Comment 3 _ ttran 2002-11-18 13:18:02 UTC
for users of the Form Editor it is an issue I think
Comment 4 _ ttran 2003-02-14 21:57:29 UTC
Tomas, can you revisit this issue?  It is listed in the top 10-ish list.  
Comment 5 Tomas Pavek 2003-02-17 13:40:53 UTC
Similar problem as issue 27781 I think. For me it works quite smoothly
so I did not consider it big problem. I'll look at it if time permits...
Comment 6 _ rkubacki 2004-04-02 11:52:56 UTC
I tried it today with build from Apr 01 and JDK1.5.0b45 on Linux and
seems to be OK. Maybe that new property sheet improved the perception
(it is redrawn only once).
Comment 7 Tomas Pavek 2004-04-02 13:20:42 UTC
I did some tuning for 3.6 too in this area, but did not do complete
analysis or measuring. See issue 39035. There were also some problems
with updating PasteAction that also were solved. So I think this issue
can be marked FIXED.

Still this is something that needs to be checked regularly...