User forums > Announcements
Release 12.11 has arrived
Pecan:
--- Quote from: Freem on December 20, 2012, 02:12:54 am ---Great job for this event. Did not come here since some times, but I just started this new version... Did not remember the upgrade, but when I saw the new...erm, logo, it jumped in my eyes ^^
At least it is quite uncommon :D
--- End quote ---
I so agree. That logo is such a pleasure.
Taiki:
Hello, I'm a C developer and a proud user of Code::Block since 2 years, I work on Windows 7.
I loved the 10.05 version: it was stable except few hangs when gdb was freezing but nothing impossible to fix with the task manager.
When I saw the 12.11 nightly some times ago, I gave it a try and I was disappointed: lot of UI elements changed in (IMO) the wrong way. I thought that it was a dev build and I said to myself that it'll improve with time. I tried several nighty, then RC1 then the final build and elements I disliked became more and more visible.
I've no problem with changes, but I want them to go in the right direction, here is a short list of what I think isn't (but I won't go against what has been decided by core developers.
1- Watches window: no more a list of variable of the current function: well, I deal with some quite big functions with over 50 variables. To deal with so much, I've functions that modify a lot of them in the same time but as I don't want to read the whole function, with the old system, I'd to watch on what become red after the function, now, I'll have to add _every variable_ to the window, manually... Please, tell me there is a way to get them all easily, the new system seems to have a lot of things to show but without this, I can't do anything :(
2- build options: they are locked when the dbg is running but I don't understand why and there is way to access to it anyway (via project prefs)?
3- can't run anymore a normal instance + one in the debugger, it was damn useful to study soft comportment when he wasn't alone to access to some resources.
4- sometime, when I press 'enter' while moving in the project tree, the tree collapse. (bug?)
5- Syntax color: well, there was A LOT of improvements in this section (:D) but also several weird bugs: the _WIN32 flag, defined at compile time is ignored in the #ifdef in the editor. It's also the case with some defines in #include file. Also, variable call "size" are colored in green. It's probably something in C++ but the project is in C so... it's disturbing. Minor bugs but they make read some long code harder :(
6- After a sigsev, the stack once hasn't been displayed. Maybe gdb failed at provide it but in this case, a message (ex: Stack unavailable) would be great.
7- UX: when the cursor is on a tile name at the bottom of the screen (dbg, search and compilation results,...) and I slide, tiles change very quickly when I highly probably simply want to slide some code. Maybe a pref for that?
I know it's a little bit late but if it could be fixed in a future release, it'd be awesome.
Even if I seem to be an evil user who want to say shit on your hard work, please understand that I wrote this long post simply because I really want Code::Block to be even better and some of all those cool new features that this update bring are hidden under some bugs and UI/UX ditch. I'll report those bugs but the compiler defines syntax color is already filled since 2 years (http://developer.berlios.de/bugs/?func=detailbug&bug_id=17921&group_id=5358) so I was scared that those issues fall into deepest part of the bug tracker without any notice :/
Thanks in advance for read this long post and tell me if you want details on anything (English isn't my native language so some parts are probably hard to understand).
PS: ICC support seems broken under both 10.05 and 12.11, on 12.11, the error message is that it doesn't find VS in the path.
Regards
Taiki
MortenMacFly:
For devs under Windows we mad it easier to get a quick start by providing the pre-compiled wxWidgets distro we have used for the release (and will use for upcoming nightlies) here:
http://www.codeblocks.org/downloads/source
Jenna:
--- Quote from: Taiki on December 26, 2012, 12:43:10 am ---I tried several nighty, then RC1 then the final build and elements I disliked became more and more visible.
I've no problem with changes, but I want them to go in the right direction, here is a short list of what I think isn't (but I won't go against what has been decided by core developers.
--- End quote ---
Why didn't you post it before the release ?
--- Quote from: Taiki on December 26, 2012, 12:43:10 am ---7- UX: when the cursor is on a tile name at the bottom of the screen (dbg, search and compilation results,...) and I slide, tiles change very quickly when I highly probably simply want to slide some code. Maybe a pref for that?
--- End quote ---
I don't understand what you mean, can you please try to explain in other words, probably with a step-by-step explanation how to get the issue ?
Alpha:
--- Quote from: Taiki on December 26, 2012, 12:43:10 am ---5- Syntax color: well, there was A LOT of improvements in this section (:D) but also several weird bugs: the _WIN32 flag, defined at compile time is ignored in the #ifdef in the editor.
--- End quote ---
This should actually work... what are your settings in Settings->Editor...->C/C++ Editor settings?
(Correctly) parsing defines from #included files is significantly more difficult than it may first sound, and is currently not supported.
--- Quote from: Taiki on December 26, 2012, 12:43:10 am ---PS: ICC support seems broken under both 10.05 and 12.11, on 12.11, the error message is that it doesn't find VS in the path.
--- End quote ---
I can work on this, however, I do not own ICC; is there a trial/free version of it?
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version