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

Author	SHA1	Message	Date
Vladimír Vondruš	506740f9c8	Trade: typeless access to MeshData indices. Like with attributes, it returns a 2D strided view with the second dimension having the same size as the index type.	6 years ago
Vladimír Vondruš	d0542267ac	Trade: direct access to MeshAttributeData array in MeshData. Again useful for MeshTools algos.	6 years ago
Vladimír Vondruš	476497952f	Trade: make it possible to construct a "padding" MeshAttributeData. Will be used in MeshTools algorithms. Also harden the MeshData constructor to reject such instances.	6 years ago
Vladimír Vondruš	5f35b06d8f	Trade: expose getters in MeshAttributeData.	6 years ago
Vladimír Vondruš	aecec186be	Trade: expose getters in MeshIndexData. It made testing and everything harder than strictly necessary. OTOH still keeping MeshData as a friend and accessing members directly since those are heavily interconnected anyway.	6 years ago
Vladimír Vondruš	e3ee1e561e	Trade: typeless access to MeshData attributes. Similarly to ImageData::pixels() which return a strided array view of one dimension more.	6 years ago
Vladimír Vondruš	c74b4c6b90	Trade: make MeshAttributeData constexpr. This makes it possible to have fully allocation-less MeshData, with statically defined indices and attributes. Only the final MeshData construction needs to be done at runtime because Array is not constexpr, but that isn't anything heavy anyway.	6 years ago
Vladimír Vondruš	8cd75087ed	Trade: make MeshIndexData constexpr. First step towards an ability to expose data compiled into an executable through MeshData without having to allocate anything.	6 years ago
Vladimír Vondruš	8ea86b05f9	Trade: implement mutable data access in MeshData. Turns out the design wasn't so simple after all. AnimationData and ImageData classes will follow with similar changes.	6 years ago
Vladimír Vondruš	ecbe5718b4	Trade: a reworked MeshData class. With API analogous to the (relatively) new AnimationData -- with one buffer containing all index data and one buffer containing all vertex data, both meant to be uploaded as-is to the GPU. This will eventually replace MeshData2D and MeshData3D, backwards compatibility and wiring up to other APIs will be done in follow-up commits.	6 years ago