Community
Participate
Working Groups
Follow up from bug 298648. The fix to bug 298648 changed view activation to be triggered by any IDebugElement rather than just IStackFrames. In multi-language debug scenarios, this can cause thread/target selection to trigger undesired view activations. For example, if a thread has frames from different languages/models, but the thread is considered to be from one model, when resuming from a frame, the thread is selected causing other views to move to the foreground. If a model wants elements other than stack frames to control view activation, IDebugModelProvider can be used/implemented.
Marking as 3.6.1 candidate, pending comments from Pawel.
I did not know about this use case. I'll undo the change and re-test. However, it seems to me that using the stack frame as a test of whether to activate a view is a rather nuanced API feature of the view activation. Seems that we should add something more explicit in the future.
Pawel, Have you been able to test? Did you find any problems?
(In reply to comment #3) > Pawel, > Have you been able to test? Did you find any problems? I'm sorry I haven't yet. I'll make sure to get to it before the end of the week.
Created attachment 173923 [details] Fix.
I reverted the logic back to use IStackFrame instead of IDebugElement. Darin please review.
Verified.