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.
The visualisation of various activity states while in debugging and the appearance of breakpoints needs to be improved as current design may cause usability problems. In particular: * green execution point colides with green selection * breakpoint is too small (and is not consistent with border highlighting of activity states)
Rather than just make a larger square, I'd like to propose that we use the same breakpoint icon as used in the source editor breakpoint annotation. If we do not use this icon and instead just use a larger red square, the square will need to look nicer than just a plain square. For example, it needs a border like the breakpoint annotation icon. Ideally, the icon should be overlaid where the incoming line crosses the top edge of the activity instead of at the top center of the activity.
I would also suggest to have an arrow as a pointer of the current execution position along with the selection. Simple selection of the currently executing element may be confusing for large containers - consider a main sequence activity which spans over 2 or more screens.
Jirka Copsa wrote: "i was just wondering if you are at work and can comment on your comment in #81610 - if you could be more specific - how and where exactly do you suggest to show the arrow ?" I think of an arrow that lie on the activity's incoming connection and points to that activity. Although, I'm not sure if can always determine on which connection to put an arrow in the case of an activity with multiple incomming connection.
The first issue described in initial description is not valid now. The second one is fixed. All other suggestions are enhancements. Resolve is as fixed
Thanks Sergey for closing this. I've filled the RFE: http://www.netbeans.org/issues/show_bug.cgi?id=85793
There is no green selection, so the first issue is not valid anymore. Verified that the second issue has been relogged into 85793