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 41934 - UI responsiveness of Step actions should be improved
Summary: UI responsiveness of Step actions should be improved
Status: CLOSED INVALID
Alias: None
Product: debugger
Classification: Unclassified
Component: Code (show other bugs)
Version: 4.x
Hardware: All All
: P2 blocker (vote)
Assignee: issues@debugger
URL:
Keywords: PERFORMANCE
Depends on:
Blocks:
 
Reported: 2004-04-13 17:10 UTC by Antonin Nebuzelsky
Modified: 2010-04-29 09:17 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Antonin Nebuzelsky 2004-04-13 17:10:25 UTC 
Step Over, Step Into and Step Out actions usually
take more than 100ms to complete. The times for
Step Over (when the current line indicator moves
only to the next line in the open source file) I
measured on my machine (old 800MHz PIII) are
around 400ms.

This means that an indication of "action in
progress" should be given to the user. For example
in the form of an hour-glass cursor shape.
Comment 1 Jan Jancura 2004-05-18 10:14:34 UTC 
This is missunderstanding.
You should not measure the time between Step Action press and debugger
stop on the next line. This is not a one action - there are two
indempendent actions in reality.
Step action adds some hidden breakpoint to debugger and calls continue
- thats all and that is very fast!

The second action is stop on breakpoint. Its separate action, and the
time between step & stop is not predicable. Moreover the step can be
never reached.

So, what can we do? We can set hour-glasses every time the debugger is
running. But I think that its not a good solution. As I remember other
IDEs behaves the same.
Comment 2 Antonin Nebuzelsky 2004-05-18 10:29:58 UTC 
Believe me, users don't care if you implement it as two actions. They
only care how responsive the application is when they invoke an action
(hit F8 or F7 in our IDE).

Why do you think setting hour-glass cursor is not a good solution? You
could first set a timer for 100ms and if the action does not finish
till the timer goes off, you would change the cursor to hour-glass.
Otherwise the cursor would not get changed.
Comment 3 Jan Jancura 2004-05-18 16:57:33 UTC 
No No No.
Step action is the same like continue one. It just resumes all threads.
Continue action does not change cursor!

The only difference is that Step Action adds some hidden breakpoint.
Ant this breakpoint can but do not have to be reached. And thats the
root of problem. I can easily add a hour-glass cursor there, but the
problem is when I should remove it. I do not see any good solution for
this.
Rethink it once more, Tonda.
I can not accept some requirement if there is no solution for it...
Comment 4 Antonin Nebuzelsky 2004-05-18 17:28:05 UTC 
I see.
Comment 5 Quality Engineering 2010-04-29 09:17:26 UTC 
Verified ... and Closing all issues resolved into NetBeans 6.7 and earlier.