Recent Posts

Pages: [1] 2 3 4 5 6 ... 10
1
Help / Re: wxScintilla and wx2.8
« Last post by oBFusCATed on Today at 09:37:53 pm »
You can use the patch attached here: http://trac.wxwidgets.org/ticket/18115 (after modifying it to match the source locations in cb's repo).
But generally you want to have wxdisplay working. It will make you're user experience a lot better.
2
Help / Re: wxScintilla and wx2.8
« Last post by Commaster on Today at 09:01:43 pm »
I've added that flag, but the setup.h still says
Code: [Select]
#define wxUSE_DISPLAY 0
I'll have to dig into the wx src to figure out why this is happening.

Thanks for the suggestion!  :)
3
Help / Re: gdb_types.script is not loaded
« Last post by oBFusCATed on Today at 08:05:15 pm »
What is gdb_types? Are you talking about the one used for our watches?
This one no longer works in newer releases. The code is fully removed. For watches you need a python enabled gdb and the appropriate printer scripts.
4
Using Code::Blocks / Re: How to keep breakpoints and bookmarks
« Last post by BlueHazzard on Today at 06:53:15 pm »
Note: You have to hit "save all" before closing, or nothing will get saved
5
Using Code::Blocks / Re: How to keep breakpoints and bookmarks
« Last post by Pecan on Today at 06:50:38 pm »
Enable Bookmarks under Settings/Editor/Browsetracker.
Bookmarks are automatically saved when the project is closed, and restored when the project is opened.

Note: Debugger breakpoints are *not* saved.


6
Help / Re: gdb_types.script is not loaded
« Last post by BlueHazzard on Today at 06:05:00 pm »
and you probably have to add it as source in the startup parameter, depending if you are on windows or linux
7
You start debugging with the red right-pointing triangle.  Hover over that for a second.  In the tool-tip that pops up you will see its description as "Debug / Continue".  Start your program using that and when you hit a break-point do what you want to do and then press it again to continue.  First click starts the program with your attached debugger and at a break point(s) subsequent clicks continue execution of your program.
8
Link to an High DPI post that might be related to your issue. http://forums.codeblocks.org/index.php/topic,22349.msg152182.html#msg152182
9
The annoying problem is when I do debug and run my cpp file a cmd will open but I can not debug again because I have to close the cmd.
How I can debug multiple times without closing the cmd every time?
10
Too bad you failed to mention what your operating system information; I guess you just wish to complain instead of getting help.

Tim S.
Pages: [1] 2 3 4 5 6 ... 10