Developer forums (C::B DEVELOPMENT STRICTLY!) > Development
Will patches to compile and link C::B against wxWidgets 2.7.1 be accepted?
Pecan:
--- Quote from: takeshi miya on November 04, 2006, 03:03:50 am ---
--- Quote from: Game_Ender on November 04, 2006, 02:54:00 am ---While your point about the config location is correct I can't let you be this wrong. I develop on the mac platform and terminal is perfectly capable of accessing "hidden" files. Terminal.app is just a terminal emulator and it runs bash, tcsh, etc shells. These access standard UNIX tools which have no problems manipulating "." files.
--- End quote ---
I know that, that's what I was referring with "some programs": you need bash/sh, you need to know which commands to issue like ls -a (which I didn't recall atm), and overall you're correct, those are standard UNIX tools, which I don't think a Mac user needs to know how to use, Finder should be enough in this case;
it was not the point anyways, and will now be fixed by the above patch.
--- End quote ---
I'm really surprised that a Mac programmer/developer is not expected to know how to use terminal and the minimum *nix commands.
I don't think I'd care to hire one of those.
takeshimiya:
--- 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
afb:
--- 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 ---
Not that surprising really, many Win programmers don't know this either (using Console and the minimum DOS commands).
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.
I would be surprised if the average UNIX/Linux developer didn't know it, but for Mac/Win I don't find it all that surprising ?
thomas:
I've taken the opportunity to rewrite the directory stuff, using wxStandardPathsBase where possible and putting everything into a class that is kept as static instance in ConfigManager. That way, file paths are determined once per application, not once for every namespace (as it is now), and all the checks whether special paths exists are also only done once, instead of once for every namespace.
The only problem so far is that wxStandardPathsBase::GetUserDateDir() crashes on my machine... it seems to hit a null pointer inside AppendAppName(), humm....
Der Meister:
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).
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version