[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kdevelop-bugs
Subject:    [Bug 141320] New: GDB cmd prompt (integrated debugger) does not
From:       Christopher Layne <clayne () anodized ! com>
Date:       2007-02-07 8:32:32
Message-ID: 20070207093231.141320.clayne () anodized ! com
[Download RAW message or body]

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
         
http://bugs.kde.org/show_bug.cgi?id=141320         
           Summary: GDB cmd prompt (integrated debugger) does not restore
                    focus after entering a command
           Product: kdevelop
           Version: unspecified
          Platform: Compiled Sources
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: general
        AssignedTo: kdevelop-bugs kdevelop org
        ReportedBy: clayne anodized com


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.


[prev in list] [next in list] [prev in thread] [next in thread]