some errors have been logged during
the Code::Blocks startup process.
Please review them in the logs...If I start C::B I get this error message:Codebut no log file is created...some errors have been logged during
the Code::Blocks startup process.
Please review them in the logs...
why C::B needs libSDL?
--without-sdlCode::Blocks is now starting to work again on the Mac,
after applying all of the latest wxFlatNotebook patches.
rev3146 should build cleanly using DarwinPorts/MacPorts,
and a "standalone" nightly build will follow later this week.
wiki: Installing_Code::Blocks_from_source_on_Mac_OS_X (http://wiki.codeblocks.org/index.php?title=Installing_Code::Blocks_from_source_on_Mac_OS_X)
Has been solved the bug of running programs on Intel build?
...save returning to zero length, can you reproduce this ??
Yeah as many times as I wish. It's simple as that:I could swear that you didn't enable the "right" format for non-ansi characters encoding, right? (Settings -> Editor -> General settings -> Default encoding). What do you expect to happen then?!
1. I open my recent project
2. I try to comment a few lines of code in my language (with some non ANSI characters)
3. I save my project
4. I get 0-length file
But you should not tell me that it's not a bug, just expected behaviour.Ok- tell me an algorithm to read your mind what encoding (out of several dozen) you'd like to have for your files and I'll implement it.
That's like stopping to use apache for http-server because in-development svn-version crashed, after you tried to mix some of it's sources with some older ones.Lol, that's a quote I'll have to remember :D
But you should not tell me that it's not a bug, just expected behaviour.Ok- tell me an algorithm to read your mind what encoding (out of several dozen) you'd like to have for your files and I'll implement it.
With regards, Morten.
May it would help if you set the default encoding to UTF-8 or UTF-16/32 ??
If this is would be an error, please explain me why.
Shade37337->greetz()
If this is would be an error, please explain me why.This wouldn't really be an error, but the "default" is still ANSI somehow. I don't know compilers that have Unicode in their language syntax (not in comments). In addition Unicode is not backward compatible. So the question is: Can the compiler read this (not really the case for UTF-8 though...)? Anyway: I'd like to note two things:
Please share the code to implement the algorithm when you get it.*lol* :lol:
thoughts * readMind()
{
return NULL;
}
That's like stopping to use apache for http-server because in-development svn-version crashed, after you tried to mix some of it's sources with some older ones.The greatest thing about this project is that it's based on custom edit control scintilla (best so far). Huh, not much left to implement. However, what I can least expect from such scintilla-based IDE are: good and handy docking system (well, you have one), superb file handling: saving & opening (these are "atom" operations to any text editor & simple to implement) the part that you failed to implement correctly. Any combination of encoding & input shouldn't lead to file-clearing that's why don't respect this project anymore!
MortenMacFly, you need more technical knowledge - any compiler CAN read UTF-8, because it's almost ANSI!!!!!!!!
Can the compiler read this (not really the case for UTF-8 though...)?-no further comment-
MortenMacFly, you need more technical knowledge - any compiler CAN read UTF-8, because it's almost ANSI!!!!!!!!Let He Who Is Without Sin Cast The First Stone.
Any news on a fix for the wxFNB tab problem for Mac?
No tabs on 3146 as far as I can see.
However, what I can least expect from such scintilla-based IDE are: good and handy docking system (well, you have one), superb file handling: saving & opening (these are "atom" operations to any text editor & simple to implement) the part that you failed to implement correctly. Any combination of encoding & input shouldn't lead to file-clearing that's why don't respect this project anymore!
After posting such reply you really look like one...no offence
Thanks for helping us (idiots) out then.
Oh, and thanks for your kind words...
Bye-bye now and go have fun elsewhere.
Guess if I'm going to use this IDE again
you failed to implement correctly.
don't respect this project anymore!
MortenMacFly, you need more technical knowledge
After posting such reply you really look like one [idiot] ...no offence
..., you need more technical knowledge - any compiler CAN read UTF-8, because it's almost ANSI!!!!!!!!
YOU (CB team) neither was helpful nor willing to solve the problem.
Guess if I'm going to use this IDE again
Congratulation for efficiently faking my post (last quote)
After posting such reply you really look like one...no offence
Thanks for helping us (idiots) out then.
Oh, and thanks for your kind words...
Bye-bye now and go have fun elsewhere.
I hope these students (BCCISProf are talking about) are ready to loose their intellectual property...
Congratulation for efficiently faking my post (last quote) that's now almost worth ban...isn't that what you want, ban everyone saying TRUTH loudly. YOU (CB team) neither was helpful nor willing to solve the problem. I hope these students (BCCISProf are talking about) are ready to loose their intellectual property...
And, it might make sense for each OS to have a different default if the user does NOT pick something.
In the meantime, perhaps when the wxWidgets encoding conversion routines return an empty string it could be caught and a warning could be shown to the user, such that the file is not lost.rjmyst3: Thanks for being productive.
Note : after your raging bull (shit) there's already some effort on it within a few hours.
...I think that too, because the compiler will report an error if he don't
I do think we should avoid to have a BOM in there.
0x13 0x65Thought I deleted that post, as I realized the reason he stopped using cb was because of the 0-byte file, not the old CBProfiler :eThat's like stopping to use apache for http-server because in-development svn-version crashed, after you tried to mix some of it's sources with some older ones.Lol, that's a quote I'll have to remember :D
But does really NO compilers supports Unicode?Maybe I missed that post but I believe nobody said this. New compilers do (and they really should do). I think what was meant was to ensure backward compatibility with old (legacy) compilers - and they usually won't.
But does really NO compilers supports Unicode?If Unicode is supposed to mean UTF-8, most of them certainly do. It is even the default encoding that gcc expects if you don't tell it otherwise.
I do not mind but the result is... no nightly for the 26st...
Of course the "use system default" approach utterly fails both for people who are too stupid to set up their system correctly and for people who run a pirated localised version of Windows that has an encoding not compatible with their native language. But seriously, should this be a concern to us? :lol:As I suspect this is aimed at me...well bro you're unforgivably wrong - I own genuine Windows XP professional edition, do you? And I'm not stupid: I was just new to your IDE, and as new user imagined that the system is friendly to new users (the mistake I made).
Yep, I became the cause of your all problems including somebody's laziness.
As I suspect this is aimed at me...well bro you're unforgivably wrong - I own genuine Windows XP professional edition, do you?
Yep, I became the cause of your all problems including somebody's laziness. I must raise thumbs-up to killerbot for at least doing something & other guy for suggesting solution... (that warning message really does the job - warns; & total destruction (no *.bak is made) of your code can be avoided).I have to disappoint you: It was me - your lazy idiot without knowledge that fixed this bug. It took me 5 minutes to track down and fix the issue... I was just waiting to see if you could provide a patch, too as I feel that you are the expert here.