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.
There are several serious usability problems related to Profiling Points, breaking original idea to have something very easy to use: - There is no clear indication from where the PP becomes active/performs action (inclusive vs. exclusive) - Whereas Start/Stop Profiling points have separate option Regions Defined by Profiling Points, other types of PPs (Take Snapshot etc.) are active always without any indication - the user may be confused that he cannot use "normal" profiling without PPs. - Profiling Points don't replace original Code Fragment profiling which was one of intentions when designing this feature. - There is no shortcut for creating PPs, the user has to use context or main menu. When working in the editor a way how to edit PPs without mouse should be available. - There is no visual indication about start/stop points pairing in the editor, moreover both start/stop points have similar icons.
Partially fixed by Profiling Points reimplementation, lowering priority: - exclusive/inclusive: PPs are now defined at start/end of line - profiling without PP: PPs can be turned off from SPT dialog - pairing indication: now indicated by tooltip and PP's popup menu
Keyboard shortcut for PP already implemented. Filed separate RFE for Stopwatches behaving like Code Fragment (Issue 105819), thus closing this issue.