Slicky wrote:When you use the menu to specify a resources.cfg location it appears to prepend the app path to it.
It pretends you to specify the resources.cfg file. I don't know what else you mean.
If you're suggesting that it should load an "open folder" dialog instead of an "open file" dialog, then I'm afraid Ogre allows using
any name for the CFG, it's just that we all use the default which is "resources.cfg", but the actual name might be "MyOwnResourcesFunnyName.cfg" (it may not even be of *.cfg extension!).
The menu says "Load resources.cfg..." because that way is easier to understand what it does, since most users use that naming convention anyway.
If you have a better name for that menu item which better suggests what it does without being missleading, I'm open to change it.
@Progman
Because I don't release what I think is low level quality stuff. I'm an advocate to open source phylosofy, and I think doing so will misslead those who want to learn from my source code, and only hurts open source.
Besides releasing the source is not about putting all *.cpp & *.h files into a ZIP and putting it in a server to download.
It needs taking care of it: Put the license header in all files (I'm thinking of GPL), put the license in the top level folder. Make double sure it doesn't contain anything propietary (I'm sure it doesn't, but I still need to check every single folder in case I didn't make a mistake) write compiling instructions (otherwise I'll get flooded with "the damn code is broken" posts) and last but not least, register the project on Sourceforge (or similar alternatives) and do all the project admin tasks to put it online.
If you're so pissed by the crash, upload the Ogre.log and let me know if you have the VC2008 SP1 redist. You have loaded absolutely no useful information that can help me to identify the source of the crash (I don't even know your OS!).
Cheers
Dark Sylinc