Community
Participate
Working Groups
3.8 M5. With the fix for bug 229536 we keep the selection stable - good! Now, there is one problem with this: when another thread gets suspended it's not easy to see which one it was. We should add some visual indication here.
One solution would be to have a view to log debug events. Then user could see clearly what events occurred and in what order. When user selected an event in the log view, the corresponding context would then get selected in Debug view. The last part would be the new and tricky part.
(In reply to comment #1) > One solution would be to have a view to log debug events. Then user could see > clearly what events occurred and in what order. When user selected an event > in the log view, the corresponding context would then get selected in Debug > view. The last part would be the new and tricky part. This is a separate feature/bug. I'm asking for a visual indicator in the Debug view ;-).
(In reply to comment #2) > This is a separate feature/bug. I'm asking for a visual indicator in the Debug > view ;-). You could look at it that way. My problem with this feature request is that I believe the Debug view already is trying to do too much. I'm suggesting to use an event log to solve your workflow problem as well as off-load some of the functionality that makes the Debug view not user friendly.
(In reply to comment #3) > (In reply to comment #2) > > This is a separate feature/bug. I'm asking for a visual indicator in the Debug > > view ;-). > > You could look at it that way. My problem with this feature request is that I > believe the Debug view already is trying to do too much. I'm suggesting to use > an event log to solve your workflow problem as well as off-load some of the > functionality that makes the Debug view not user friendly. I disagree. Adding yet another view to the Debug perspective isn't helpful - at least not to me. I mainly work with the Debug view + editor + Variables view.
(In reply to comment #4) > I disagree. Adding yet another view to the Debug perspective isn't helpful - at > least not to me. I mainly work with the Debug view + editor + Variables view. Nobody really wants another view. Is there another creative way to display notifications (e.g. email notification style popus)?
(In reply to comment #5) > (In reply to comment #4) > > I disagree. Adding yet another view to the Debug perspective isn't helpful - at > > least not to me. I mainly work with the Debug view + editor + Variables view. > > Nobody really wants another view. Is there another creative way to display > notifications (e.g. email notification style popus)? For me a simple decorator that denotes the last suspended thread is enough. That's all I'm asking in this bug.
+1 for a solution in the Debug view. You could also change the label to "... (Suspended at <date> <time>)". Then the sequence would be visible and Navigate > Next/Previous (Ctrl+./,) could jump through suspended threads in the order of suspension time. Deselect all, Ctrl+. would select the last suspended thread.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. If the bug is still relevant, please remove the stalebug whiteboard tag.
