| Summary: | GDB cmd prompt (integrated debugger) does not restore focus after entering a command | ||
|---|---|---|---|
| Product: | [Applications] kdevelop | Reporter: | Christopher Layne <clayne> |
| Component: | CPP Debugger | Assignee: | kdevelop-bugs-null |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | ||
| Priority: | NOR | ||
| Version: | 3.4.0 | ||
| Target Milestone: | --- | ||
| Platform: | Compiled Sources | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
same here. A solution like proposed above would be great! Somebody, please commit this patch. I would expect it to be safe. The case we had so much trouble with came from updating of the breakpoint editor markers, but I can't see any marker changes happening from entering a gdb command (event though in some cases there should be marker changes) so we shouldn't end up in that mess from this. But why does the focus move away from the input box in the first place? Maybe due to the workaround to the breakpoint-table problem? Anyway, I'll apply and commit the patch. SVN commit 681287 by apaku:
Set focus on gdb edit field after executing a user-supplied gdb command.
Thanks to Christopher Layne for the patch.
BUG:141320
M +1 -0 gdboutputwidget.cpp
--- branches/KDE/3.5/kdevelop/languages/cpp/debugger/gdboutputwidget.cpp #681286:681287
@@ -242,6 +242,7 @@
m_gdbView->scrollToBottom();
m_gdbView->setUpdatesEnabled(true);
m_gdbView->update();
+ m_userGDBCmdEditor->setFocus();
}
/***************************************************************************/
|
Version: (using KDE Devel) Installed from: Compiled sources Compiler: gcc 4.1.1 OS: Linux Enter a simple command like: p /t some_variable You get what you expect and then focus jumps away from the input field. This is counter-intuitive as most people entering manual gdb commands into the input field will be entering additional data into the "GDB cmd" field. $ svn diff src/kdevelop/3.4/languages/cpp/debugger/gdboutputwidget.cpp Index: src/kdevelop/3.4/languages/cpp/debugger/gdboutputwidget.cpp =================================================================== --- src/kdevelop/3.4/languages/cpp/debugger/gdboutputwidget.cpp (revision 631142) +++ src/kdevelop/3.4/languages/cpp/debugger/gdboutputwidget.cpp (working copy) @@ -242,6 +242,7 @@ m_gdbView->scrollToBottom(); m_gdbView->setUpdatesEnabled(true); m_gdbView->update(); + m_userGDBCmdEditor->setFocus(); } /***************************************************************************/ Is what I added to get it to work for me. Debugger hotkeys still function properly while the input remains focused. Intuitively when using a debugger action like "step over" the focus is removed - but not removed if you're manually entering commands to gdb.