61
General (but related to Code::Blocks) / Re: Welcome Newcomers - PLEASE READ!!!
« Last post by mgartex on December 27, 2024, 07:46:42 am »New user account! Registered today. I'm real....I love Code::Blocks!
News:
Accounts with zero posts and zero activity during the last months will be deleted periodically to fight SPAM!
Recent Posts
62
Help / Re: How to change title page(?) font colour
« Last post by ubuntourist on December 26, 2024, 08:10:10 pm »If you are talking about the "Start here" page, the colours are set in Environment Settings / Colours / Start here page (three entries). This page is HTML shown using wxHtmlWindow, so theming should not affect the selected colours.
Excellent! Thanks! I missed that. Exactly what I was looking for. It's readable now.
63
Help / Re: How to change title page(?) font colour
« Last post by Miguel Gimenez on December 26, 2024, 07:58:40 pm »If you are talking about the "Start here" page, the colours are set in Environment Settings / Colours / Start here page (three entries). This page is HTML shown using wxHtmlWindow, so theming should not affect the selected colours.
If you are talking about other page, please attach a picture.
If you are talking about other page, please attach a picture.
64
Help / Re: How to change title page(?) font colour
« Last post by ubuntourist on December 26, 2024, 05:33:32 pm »Did this get answered in another topic? I'm having the exact same issue. (I added a bunch of themes with the thought that one might affect the splash / title screen, but alas, no.)
65
Using Code::Blocks / Re: program can't start because libgcc_s_dw2-1.dll is missing from your computer
« Last post by ur_naz on December 26, 2024, 01:06:53 pm »The reason is[...] because it's neither in the search path, nor in the same folder as the exe.Easiest fix is to simply copy libgcc_s_dw2-1.dll (it should be located somewhere similar to C:\MinGW\bin or C:\Program Files\CodeBlocks\MinGW\bin) into the same folder as the .exe.
Alternatively, add the following two switches to your linker options:
-static-libgcc
-static-libstdc++
This doesn't work for my basic sfml project on cb20.03. i mean using flags. so i have to put libs near my executable file.
However it works fine for my basic winapi project. 
66
Using Code::Blocks / Re: Memory dump Window Format
« Last post by mannisp on December 25, 2024, 10:14:30 pm »Yes this is an old topic but as long as Google (or other web search) finds this when trying to find help for showing floating point values in memory dump, it is still valid thread.
So, thanks to previous message I was able to add an array to watches and edit properties to show float values instead of hex values in memory dump. However, this is a strangely behaving feature, far from intuitive:
Firstly, when a pointer is a function argument, you cannot edit its properties in watches by right clicking to show it as array. It has to be added separately to watches during run-time by right-clicking the variable in c file. Only then it allows editing properties when right-clicking in watches window. This doesn't seem like a well-thought feature; there's no reason why pointer in function arguments should not directly allow showing it as array.
Then in properties it is not obvious that you have to leave the format as "undefined" in order to show the floating point value. I tried all other options until I gave up and set it undefined and to my surprise it then showed floating point value.
So, thanks to previous message I was able to add an array to watches and edit properties to show float values instead of hex values in memory dump. However, this is a strangely behaving feature, far from intuitive:
Firstly, when a pointer is a function argument, you cannot edit its properties in watches by right clicking to show it as array. It has to be added separately to watches during run-time by right-clicking the variable in c file. Only then it allows editing properties when right-clicking in watches window. This doesn't seem like a well-thought feature; there's no reason why pointer in function arguments should not directly allow showing it as array.
Then in properties it is not obvious that you have to leave the format as "undefined" in order to show the floating point value. I tried all other options until I gave up and set it undefined and to my surprise it then showed floating point value.
67
General (but related to Code::Blocks) / Re: CodeBlocks with Win 98se, DJGPP & Vesa VBE
« Last post by ollydbg on December 21, 2024, 07:06:05 am »Nice work, Tim.
If I remember correctly, there is another guy which build a C::B working on very old Windows 95 system. I just forget the github link.
If I remember correctly, there is another guy which build a C::B working on very old Windows 95 system. I just forget the github link.
68
Nightly builds / Re: The 08 December 2024 build (13596) is out.
« Last post by Khram on December 19, 2024, 12:17:12 pm »Problem again. And the editing result can no longer be saved.
69
General (but related to Code::Blocks) / Re: CodeBlocks with Win 98se, DJGPP & Vesa VBE
« Last post by MichaelAgarkov on December 17, 2024, 08:02:11 pm »Awesome project! wxWidgets 3.0.5 is the last version that supports Win95, so in theory it should be possible to port newer versions of C::B. Unicode support can be added via Unicows. If you got the time, I wish you good luck!
70
General (but related to Code::Blocks) / CodeBlocks with Win 98se, DJGPP & Vesa VBE
« Last post by Tim on December 17, 2024, 06:31:40 pm »A while back I wanted to use DJGPP with Codeblocks and windows 98se, after building DJ Delories impressive vesa (VBE) plasma demo.
When I tried using the ansi build of CB 8.02 it kept crashing when I tried to access the menu with the mouse on "real" hardware, so I used CB1 RC2 instead. After a while I found a problem in CB1 RC2 which limited the number of user compilers to 1 only, and so tried rebuilding RC2 with Widgets version 2.6.4 and the problem went away. Later I tried the same thing with an ansi version of CB 8.02 with WxWidgets version 2.8.12 and the crashing problem went away. I had always intended to create a post with some links to these later builds, but as usual, I just moved on to my next project, and forgot about them. Then months later, when I thought about it again I could no longer remember what the state of play was with the rebuilds so I just posted them up to Github. (https://github.com/Krakenw/codeblocks-win98-98SE)
Now we come to the point of this post, I recently bought an old Dell D810 laptop which came with a hires 1680x1050 screen, and I immediately loaded it with 98se which worked a treat. Next I actually loaded the standard version of CB 8.02 and then before running it copied over it with the 2.8.12 build from Github. I then set it up to use DJGPP and started playing with it and so far it's all worked fine. So even though I don't remember what the 2.8.12 build details were, because I'm using it now without a problem, it seems worth mentioning it to other CB users. Something else that might be worth mentioning is that although you can use DJGPP with XP, you can't make use of 32 bit mode VBE calls or examine usb 3.0 chips etc; for this sort of "playing about" you need to be using win98. (I can't comment on Linux, as I don't use it)
When I tried using the ansi build of CB 8.02 it kept crashing when I tried to access the menu with the mouse on "real" hardware, so I used CB1 RC2 instead. After a while I found a problem in CB1 RC2 which limited the number of user compilers to 1 only, and so tried rebuilding RC2 with Widgets version 2.6.4 and the problem went away. Later I tried the same thing with an ansi version of CB 8.02 with WxWidgets version 2.8.12 and the crashing problem went away. I had always intended to create a post with some links to these later builds, but as usual, I just moved on to my next project, and forgot about them. Then months later, when I thought about it again I could no longer remember what the state of play was with the rebuilds so I just posted them up to Github. (https://github.com/Krakenw/codeblocks-win98-98SE)
Now we come to the point of this post, I recently bought an old Dell D810 laptop which came with a hires 1680x1050 screen, and I immediately loaded it with 98se which worked a treat. Next I actually loaded the standard version of CB 8.02 and then before running it copied over it with the 2.8.12 build from Github. I then set it up to use DJGPP and started playing with it and so far it's all worked fine. So even though I don't remember what the 2.8.12 build details were, because I'm using it now without a problem, it seems worth mentioning it to other CB users. Something else that might be worth mentioning is that although you can use DJGPP with XP, you can't make use of 32 bit mode VBE calls or examine usb 3.0 chips etc; for this sort of "playing about" you need to be using win98. (I can't comment on Linux, as I don't use it)