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 50809 - Double clicking on the current stackframe has no effect
Summary: Double clicking on the current stackframe has no effect
Status: CLOSED FIXED
Alias: None
Product: debugger
Classification: Unclassified
Component: Code (show other bugs)
Version: 4.x
Hardware: PC All
: P4 blocker (vote)
Assignee: issues@debugger
URL:
Keywords: RANDOM
Depends on:
Blocks:
 
Reported: 2004-10-25 14:30 UTC by _ lcincura
Modified: 2010-04-29 09:19 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 _ lcincura 2004-10-25 14:30:17 UTC
If I double click on a -different- stack frame,
then on the current stack frame, things work. But
it would be nice if the code which is determining
that "I'm already in th right context" would also
set the editor location regardless.
Comment 1 Maros Sandor 2004-10-25 15:11:54 UTC
Fixed by this commit:

/cvs/debuggerjpda/ui/src/org/netbeans/modules/debugger/jpda/ui/models/
CallStackActionsProvider.java,v
1.8 => 1.9
Comment 2 Jan Jancura 2004-10-25 15:23:12 UTC
fixed in the main trunk;
Comment 3 _ lcincura 2005-02-08 12:49:30 UTC
Verified on build 200502061900
Comment 4 _ lcincura 2005-04-21 13:52:52 UTC
Again does not work in 4.2 build 200504181800
Comment 5 Martin Entlicher 2005-05-31 15:43:19 UTC
This works only randomly. Sometimes it looks like one click is consumed by the
focus transfer...
Comment 6 Martin Entlicher 2005-05-31 15:51:09 UTC
This might be partially related to a similar bug in openide/core (likely
WinSys), which occasionally occurs also in Explorer - double click on a file
does not open it.

However, in Call Stack this seems to occur much more often.
Comment 7 Martin Entlicher 2007-04-10 16:46:04 UTC
It seems to be O.K. after the fix of issue #92319.
Please verify.
Comment 8 Quality Engineering 2010-04-29 09:19:46 UTC
Verified ... and Closing all issues resolved into NetBeans 6.7 and earlier.