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 118263 - Open Threads View option usage is not clear
Summary: Open Threads View option usage is not clear
Status: RESOLVED FIXED
Alias: None
Product: profiler
Classification: Unclassified
Component: Base (show other bugs)
Version: 6.x
Hardware: All All
: P4 blocker (vote)
Assignee: Jiri Sedlacek
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-10-09 16:12 UTC by Maksim Khramov
Modified: 2012-10-15 10:48 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 Maksim Khramov 2007-10-09 16:12:29 UTC
Product Version: NetBeans IDE Dev (Build 200710090000)
Java: 1.6.0_02; Java HotSpot(TM) Client VM 1.6.0_02-b05
System: Windows XP version 5.1 running on x86; Cp1251; ru_RU (nb)

Actual usage for this option is not clear. When I set this option to Always I expect that Threads View ALWAYS opens
automatically when I start profiling, but now it opens only when 'Enable threads monitoring' option is checked in SPT
dialog. 
Moreover for CPU and Memory profiling modes 'Enable threads monitoring' available only in custom configurations in
advanced settings.
Comment 1 Jiri Sedlacek 2007-10-12 17:46:35 UTC
I believe that it does make sense to not open Threads view when threads are not monitored - but I agree that the wording
is a bit misleading and should be improved. Lowering priority as this is really a minor issue.
Comment 2 Tomas Hurka 2007-11-07 10:36:41 UTC
Changing target milestone to dev, since NetBeans 6.0 is in high resistance mode.
Comment 3 Tomas Hurka 2009-04-08 10:10:36 UTC
Target milestone cleanup.
Comment 4 Tomas Hurka 2009-04-08 12:53:44 UTC
Milestone cleanup: future->next
Comment 5 Jiri Sedlacek 2012-10-15 10:48:25 UTC
Already fixed, added a hint "if threads monitoring is enabled" to profiler options.