Developer forums (C::B DEVELOPMENT STRICTLY!) > Development
Will patches to compile and link C::B against wxWidgets 2.7.1 be accepted?
Game_Ender:
--- Quote from: afb on November 04, 2006, 04:36:00 pm ---And since the default Mac OS X file manager or the default file dialogs won't help them find the files, many users won't do so.
--- End quote ---
Just a helpful tip: You can get directories like /usr/local by just using Command+Shift+G in finder. A box pops up and you can type in any path you want, if I remember correctly it even has tab completion.
Pecan:
--- Quote from: takeshi miya on November 04, 2006, 03:57:53 pm ---
--- Quote from: Pecan on November 04, 2006, 03:23:15 pm ---I'm really surprised that a Mac programmer/developer is not expected to know how to use terminal and the minimum *nix commands.
--- End quote ---
I don't know how you can ask this, since there are users in this forum that doesn't know even what a project is, or how to debug let alone where the problem was.
This is way off-topic too :P
--- End quote ---
It is not off-topic.
My point is: you are going to a lot of trouble to code and implement changes to CodeBlocks for which a programmer/developer should reasonable be expected to know.
N00bies are different. They're expected to read books and ask questions in order to become a knowledgeable programmer/developer who, on learning how to use an OS, can then find ./codeblocks and become proficient in CB.
Is this an IDE for kindergarten or developers?
thomas:
--- Quote from: Der Meister on November 04, 2006, 06:21:34 pm ---Why are you using wxStandardPathsBase? The "standard" way should be like this:
--- Code: ---wxStandardPaths::Get().GetUserDataDir()
--- End code ---
Anyway, I don't know if this fixes your crash, but I never had any problems with this line of code (not on Windows and not on Linux).
--- End quote ---
I sure was doing what you call the standard way :)
The problem was that I had put all the path names along with initialising code into a static object, so initialisation is done implicitely, and we can avoid calling if(someVariable.IsEmpty()) a hundred times.
Unluckily, wxStandardPaths does not like being called from global constructors... although the documentation speaks of "initialised to reasonable values", the meaning of "reasonable" is apparently NULL.
I've reduced all the checks to testing one boolean now, and initialisation is done the first time any directory function is used... that works, but I am not 100% happy with it.
Der Meister:
Ah, OK, that explains matters...
I guess the problem with your first approach is that you can't say anything about the order in which static and global objects were intialized - maybe your static variable was initialized before the wxStandardPaths structures?
thomas:
Yeah well.... a common problem :(
I had expected, though, that since you instantiate the wxStandardPaths singleton before using it, its data would be valid. But unluckily, that doesn't hold. It still only works after wxApp::OnInit().
The way it is now is probably as good as it can get, oh well... I'll keep it around for a day or two to see if anything works differently from what you would expect, and will commit then.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version