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 188519 - Watches should be resolved against correct context
Summary: Watches should be resolved against correct context
Status: RESOLVED WONTFIX
Alias: None
Product: javafx
Classification: Unclassified
Component: Debugger (show other bugs)
Version: 6.x
Hardware: PC Windows XP
: P2 normal (vote)
Assignee: Michal Skvor
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-07-09 08:12 UTC by Martin Ryzl
Modified: 2011-05-16 13:52 UTC (History)
0 users

See Also:
Issue Type: ENHANCEMENT
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 Martin Ryzl 2010-07-09 08:12:45 UTC 
Bounce sample, the loop at line 111. When stepping through, I'd like to create a new watch for bricks. It is also visible through +Script node but this may contain too many fields or get collapsed, whatever.
However, if I add the new watch and type in bricks, it says "bricks is not a know variable in the current context".
The IDE should try to resolve it against script level if the field cannot be resolved in current context.
Comment 1 Michal Skvor 2010-08-03 13:25:16 UTC 
The Script node is visible only when "this" variable is visible to the debugger. This feature is about to evaluate/implement in next version.
Comment 2 David Strupl 2011-05-16 13:52:59 UTC 
Closing all bugs filed against JavaFX 1.x as wontfix. We will support JavaFX 2.0 - please keep opened only bugs against the new release. Thanks.