From a6543e68c04261c31456b503c50295148152edd9 Mon Sep 17 00:00:00 2001 From: Rene Gollent Date: Mon, 27 May 2013 21:59:59 -0400 Subject: [PATCH] When an exception/breakpoint is hit, activate... ...the team window. Resolves #9797. --- .../user_interface/gui/team_window/TeamWindow.cpp | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-) diff --git a/src/apps/debugger/user_interface/gui/team_window/TeamWindow.cpp b/src/apps/debugger/user_interface/gui/team_window/TeamWindow.cpp index 5d0fea6183..1c90ef8119 100644 --- a/src/apps/debugger/user_interface/gui/team_window/TeamWindow.cpp +++ b/src/apps/debugger/user_interface/gui/team_window/TeamWindow.cpp @@ -1290,9 +1290,16 @@ TeamWindow::_HandleThreadStateChanged(thread_id threadID) } // Switch to the threads tab view when the thread has stopped. - if (thread->State() == THREAD_STATE_STOPPED) + if (thread->State() == THREAD_STATE_STOPPED) { fTabView->Select(MAIN_TAB_INDEX_THREADS); + // if we hit a breakpoint or exception, raise the window to the + // foreground, since if this occurs while e.g. debugging a GUI + // app, it might not be immediately obvious that such an event + // occurred as the app may simply appear to hang. + Activate(); + } + _UpdateRunButtons(); }