Chris Robinson a3511c62cf Don't store textkeys in user object bindings ... It's a bit unwieldy to have them stored in the 'skeleton master' instead of the skeleton instance. And although the text keys are extracted for each created instance now, this shouldn't be much worse than the multimap copying going on before. Plus, proper serialization can help for future optimizations.		2013-04-22 00:01:30 -07:00
..
tests	Mostly removal of unnecessary #include's and a little clean up	2012-07-17 09:27:12 +02:00
material.cpp	Fix normal maps with spaces in filename not getting loaded	2013-04-12 04:36:28 +02:00
material.hpp	Move NIFMaterialLoader to a separate file	2013-04-10 20:24:44 -07:00
mesh.cpp	Move a method to the Node class	2013-04-10 23:19:47 -07:00
mesh.hpp	Move the mesh loader to its own source file	2013-04-10 22:38:46 -07:00
ogrenifloader.cpp	Don't store textkeys in user object bindings	2013-04-22 00:01:30 -07:00
ogrenifloader.hpp	Avoid storing text keys for each animation	2013-04-21 22:56:40 -07:00
skeleton.cpp	Don't store textkeys in user object bindings	2013-04-22 00:01:30 -07:00
skeleton.hpp	Don't store textkeys in user object bindings	2013-04-22 00:01:30 -07:00