Code::Blocks Forums
User forums => Nightly builds => Topic started by: killerbot on February 26, 2006, 07:02:42 pm
-
Get quick announcements through the RSS feed http://www.codeblocks.org/nightly/CodeBlock_RSS.xml
A link to the unicode windows wxWidget dll for Code::Blocks : http://download.berlios.de/codeblocks/wxmsw26u_gcc_cb.7z
For those who might need this one (when no MingW installed on your system) : the mingw10m.dll : http://download.berlios.de/codeblocks/mingwm10.7z
For support of ansi builds, a link to the ansi windows wxWidget dll for Code::Blocks : http://download.berlios.de/codeblocks/wxmsw26_gcc_cb.7z
The 26 February 2006 build is out.
- Windows : http://download.berlios.de/codeblocks/CB_20060226_rev2084_win32.7z
- Windows (ANSI): http://download.berlios.de/codeblocks/CB_20060226_rev2084_win32_ansi_.7z
- Linux : not supported yet
Resolved Fixed:
- Added debian folder for .deb creation
- Fix for compiler options dialog in 120 dpi
- Fixed some View menu items not working in linux (Manager, Open files
and Fullscreen) - Fixed default EOL mode to be defined correctly under each
platform - Improved filenames handling
Regressions/Confirmed/Annoying/Common bugs:
- DDE bug : clicking in windows explorer on a CB registered file throws an error message box
- toolbar-images-not-changing-state (is a wx problem)
- there are several issues with Code Completion (is being redesigned : work in progress)
-
Hi, when I write something in unicode in the source code and save the file it becomes 0 bytes. I don't know it's CodeBlocks or Scintilla bug, here is the string which contains unicde letters, when I delete these 3 letters everything goes well, when I write even one such letter and try to save the *.cpp file it becomes 0 bytes length... Thank you.
_tprintf(_T("%s"), _T("Այո"));
-
check your File encoding settings
-
check your File encoding settings
Ah, thank you.
Anyway, I think it would be "logically more right" if it could automatically detect non ASCII characters and ask what to do.
P.S.
Do you know if it is ISO standard compatible UTF-8 or UNICODE source files with BOM? In other words, do all popular compilers support such files? Thank you once more.
-
now that's out of my league, I just knew it is often a cause of problems.
Yiannis, Thomas to the rescue please (they know all about this) ... :mrgreen:
-
You know how the wx-not-changing-state problem was for some of the buttons.... Uhh, well, the ANSI build for Windows 9x does not have this problem..... :shock: It may be a unicode wx problem! The ANSI build on Windows 98 did not have the problem, the stop debugging icon was greyed out like it was supposed to...
-
You know how the wx-not-changing-state problem was for some of the buttons.... Uhh, well, the ANSI build for Windows 9x does not have this problem..... :shock: It may be a unicode wx problem! The ANSI build on Windows 98 did not have the problem, the stop debugging icon was greyed out like it was supposed to...
Unless something pertinent was changed between 2083 and 2084, it's still present in the ANSI build running under WinXP.
-
Hi, I found new bug in this build (I didn't noticed it in previews). When I click Settings->Editor following message shows up:
10:06:52: No handler found for XML node 'object', class 'sizeritem'!
10:06:52: No handler found for XML node 'object', class 'sizeritem'!
I'm using Windows UNICODE version in WindowsXP.
-
Hello,
Yes, I can confirm these bugs. I have compiled C::B rev2084 myself with GCC4.1.0 and wxWidgets 2.6.3-RC1.
Best wishes,
Michael
-
Yes ,I have it too.
-
:shock: O.o, I'm hoping no-one used wxSmith for adding wxStdDialogButtonSizers in XRC mode. I've implemented the c++ output, but not the xrc output, because I didn't know wxSmith internals enough (and as byo said the recode was coming. BTW I told him that xrc output was not implemented).
Look at the todo's in src\plugins\contrib\wxSmith\defwidgetswxsstddialogbuttonsizer.h.
-
Yiannis has fixed it in the mean time.
-
Yiannis has fixed it in the mean time.
Veni, vidi, vici. :D
Best wishes,
Michael