I think it would be a good idea to default that option to 'on' instead

Sweet, thank youCool - I'll make that little tweak
That would be great! Please go ahead. Do you need anything to do for that from my side?If it all goes well, do you mind if I push this back to your fork?
Nopekuxv wrote:Please go ahead. Do you need anything to do for that from my side?
Code: Select all
3> OgreTerrainPagedWorldSection.cpp
3> Generating Code...
3>c:\users\angus\documents\projects\ogre\gsoc_2011_tpi\components\terrain\src\ogreterrain.cpp(1399): fatal error C1001: An internal error has occurred in the compiler.
3> (compiler file 'f:\dd\vctools\compiler\utc\src\p2\main.c[0x6C6618C0:0x00000004]', line 183)
3> To work around this problem, try simplifying or changing the program near the locations listed above.
3> Please choose the Technical Support command on the Visual C++
Code: Select all
1>------ Build started: Project: OgreTerrain, Configuration: Debug Win32 ------
1> OgreTerrain.cpp
1>C:\Users\Angus\Documents\Projects\Ogre\GSOC_2011_TPI\Components\Terrain\src\OgreTerrain.cpp(5038): error C2665: 'operator new' : none of the 5 overloads could convert all the argument types
1> C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\include\crtdbg.h(1080): could be 'void *operator new(size_t,int,const char *,int)'
1> C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\include\xdebug(33): or 'void *operator new(size_t,const std::_DebugHeapTag_t &,char *,int) throw(...)'
1> while trying to match the argument list '(unsigned int, const char [92], int, const char [64])'
========== Build: 0 succeeded, 1 failed, 2 up-to-date, 0 skipped ==========
Sorry if that's a bit off-topic, but I'd really like to see documentation about Ogre components (new terrain, RTSS, etc.) included into the Manual...jacmoe wrote:We can't have too much documentation on the terrain component.
The problem is: Someone has to volunteer to write that documentation first in a way that can be included in the manual.Mikachu wrote:Sorry if that's a bit off-topic, but I'd really like to see documentation about Ogre components (new terrain, RTSS, etc.) included into the Manual...jacmoe wrote:We can't have too much documentation on the terrain component.
Since these components ship together with Ogre, the wiki might not be enough, IMHO.
Oops, I didn't realize that the sources for Ogre manual are actually in the repository...spacegaier wrote:The problem is: Someone has to volunteer to write that documentation first in a way that can be included in the manual.Mikachu wrote:Sorry if that's a bit off-topic, but I'd really like to see documentation about Ogre components (new terrain, RTSS, etc.) included into the Manual...jacmoe wrote:We can't have too much documentation on the terrain component.
Since these components ship together with Ogre, the wiki might not be enough, IMHO.