User forums > Nightly builds

The 27 November 2010 build (6863) DEBUGGER BRANCH version is out.

<< < (3/6) > >>

killerbot:
or we can start with an entry in the Debug menu, and right click context menu, right ?

oBFusCATed:

--- Quote from: killerbot on November 30, 2010, 01:04:35 pm ---or we can start with an entry in the Debug menu, and right click context menu, right ?

--- End quote ---
Yes for Debug menu
No for the context menu, it is too crowded already

killerbot:
what about grouping all the debug related ones in a submenu Debug in the right click context menu (toggle breakpoint , run to cursor,  set next statement) ?

Pecan:
Could we hide the remote console on MSW with something like the following:


--- Code: ---Index: src/plugins/debuggergdb/debuggergdb.cpp
===================================================================
--- src/plugins/debuggergdb/debuggergdb.cpp (revision 6710)
+++ src/plugins/debuggergdb/debuggergdb.cpp (working copy)
@@ -831,6 +831,13 @@
         SetConsoleTitleA("Codeblocks debug console - DO NOT CLOSE!");
         SetConsoleCtrlHandler(HandlerRoutine, TRUE);
         m_bIsConsole = true;
+        //(pecan 2010/10/20) start
+        HWND console_window_handle = GetConsoleWindow();
+        if (console_window_handle)
+        {
+            ShowWindow( console_window_handle, SW_HIDE );
+        }
+        //(pecan 2010/10/20) end
     }
     #endif
     // start the gdb process
--- End code ---

Pecan:
MSW: "Run to cursor" is enabled, runs the debugger and breaks the program at the cursor.

"Step Into" is enabled, runs the debugger but does not break the program.

Why is "Step Into" enabled before running the debugger?

Navigation

[0] Message Index

[#] Next page

[*] Previous page