ic/magnum - magnum - Gitea: Git with a cup of tea

Author	SHA1	Message	Date
Vladimír Vondruš	eabba4f155	Trade,SceneTools: use lowercase in custom field / attribute name tests. Custom material attributes are enforced to start with a lowercase letter, so I think it makes sense to be consistent and use the same for custom scene fields and mesh attributes as well. It's not enforced in any way but the tests should reflect that choice so new code that gets written based on these inherits that practice.	3 years ago
Vladimír Vondruš	bb6b84a76e	sceneconverter: implement --bounds for mesh weights and joint IDs.	3 years ago
Vladimír Vondruš	07a8edb03d	sceneconverter: test mesh bounds printing better. The main property of this feature is that it prints the bounds in a canonical type, not of the actual type that's used. Yet however that wasn't ever tested. Now it is, and it's also testing behavior for custom attributes, which don't get their bounds printed (because the canonical type isn't known for those).	3 years ago
Vladimír Vondruš	7067ed91c8	{scene,image}converter: split implementation and executable tests. They're each a totally different beast and putting them into the same test file doesn't really make sense: - We want to link certain plugins statically on static builds to test certain code paths in the implementation. However this is counter-productive for the executable tests because there we are checking for plugin presence from the test with the assumption that the executable and the test have the exact same set of plugins available (or linked statically). - The executable tests are implemented on Unix only at the moment, thus it's wasteful to try to build it on any other platforms. Having it in a separate file makes it much easier to deal with.	4 years ago
Vladimír Vondruš	cc29cbcc73	{image,scene}converter: extract and test --info printing code. It was quite a pile, and all of it was written just once, relying only on hopefully-available model files that would hopefully touch most code paths. Which means, extremely annoying to make changes in. I extracted the code to a header that can be tested with a mocked-up importer and without having to execute the utility itself, deduplicated the image info printing code, fixed various inconsistencies (such as data/field flags sometimes denoted with superfluous "flags:" and sometimes not) and TODOs (such as 2D/3D skins, where there was no format whatsoever that would have 2D skin support, so the code couldn't get written). Now it's finally possible to easily add the remaining missing features, such as printing camera info.	4 years ago