* Non-maintainer upload. * No longer try to detect (using /proc/cpuinfo when available) how many CPUs are available, fixing the FTBFS (due to -j0) on various platforms (Closes: #477353). The right way to do it is to support parallel=n in DEB_BUILD_OPTIONS (see Debian Policy §4.9.1), and adequate support has been implemented. * Add patch to fix FTBFS due to the build system now refusing to handle whitespaces (Policy CMP0004 say the logs), thanks to Andreas Putzo who provided it (Closes: #482239): - debian/patches/fix-cmp0004-build-failure.dpatch * Remove myself from Uploaders, as requested a while ago, done by Luk in his 2.2.0-2.1 NMU, which was never acknowledged.
"Set the number of frames to retain objects that are have been requested for deletion. ",
39
"When set to zero objects are deleted immediately, by set to 1 there are kept around for an extra frame etc. The ability to retain obejcts for several frames is useful to prevent premature deletion when objects are stil be used the graphics threads that are using double buffering of rendering data structures with non ref_ptr<> pointers to scene graph elements. ");
39
"When set to zero objects are deleted immediately, by set to 1 there are kept around for an extra frame etc. The ability to retain objects for several frames is useful to prevent premature deletion when objects are still be used the graphics threads that are using double buffering of rendering data structures with non ref_ptr<> pointers to scene graph elements. ");
40
40
I_Method0(int, getNumFramesToRetainObjects,
41
41
Properties::NON_VIRTUAL,
42
42
__int__getNumFramesToRetainObjects,
45
45
I_Method1(void, setFrameNumber, IN, int, frameNumber,
46
46
Properties::NON_VIRTUAL,
47
47
__void__setFrameNumber__int,
48
"Set the current frame numberso that subsequent deletes get tagged as associated with this frame. ",
48
"Set the current frame number so that subsequent deletes get tagged as associated with this frame. ",