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 173177 - Project debuggin does not open Watches window
Summary: Project debuggin does not open Watches window
Status: VERIFIED WORKSFORME
Alias: None
Product: javafx
Classification: Unclassified
Component: Debugger (show other bugs)
Version: 6.x
Hardware: All All
: P2 blocker (vote)
Assignee: Michal Skvor
URL:
Keywords:
Depends on:
Blocks: 173187
  Show dependency tree
 
Reported: 2009-09-28 09:30 UTC by Alexandr Scherbatiy
Modified: 2010-06-24 09:06 UTC (History)
0 users

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 Alexandr Scherbatiy 2009-09-28 09:30:16 UTC 
netbeans-trunk-nightly-200909221401-javafx-full.zip 

  Product Version         = NetBeans IDE Dev (Build 200909221401) (#038a2843d59a)
  Operating System        = Windows XP version 5.1 running on x86
  Java; VM; Vendor        = 1.6.0_15; Java HotSpot(TM) Client VM 14.1-b02; Sun Microsystems Inc.

Steps to reproduce:

- Remove the NB userdir
- Start the IDE
- Debug a JavaFX project
 Only Variables and Breakpoints windows open.
 
 Other debugger windows like Watches do not open.
Comment 1 Michal Skvor 2009-10-23 15:46:04 UTC 
Watches are not implemented in 6.8 so it makes no sense to show them.
Comment 2 Lukas Hasik 2009-11-12 07:56:36 UTC 
as this bug is either caused by the fx compiler or it too complicated to fix it in 6.8 - > approved
Comment 3 Petr Suchomel 2010-03-26 13:47:48 UTC 
Watch could not work until we have mapping between JavaFX and generated variables in class files. There is no way to guess them
Comment 4 Alexandr Scherbatiy 2010-03-29 12:26:32 UTC 
Could the appropriate issue be created in JIRA?
Comment 5 Michal Skvor 2010-06-22 14:19:30 UTC 
Watches and local variables window is joined. If somebody wants to open the window he could do that from menu->Window->Debugging.
Comment 6 Alexandr Scherbatiy 2010-06-24 09:06:43 UTC 
verified