assimp/test/models/PLY
Matthias Möller db72c6ee38 When "getNextBlock" was called after "getNextLine", the pointer could still on the newline.
The pointer to a newline could not advance enough, when the line ended with \r\n. The resulting buffer was correct, as the buffer range went from <start> until \r, but that the pointer increased by just 1 could lead to the problem that the next pointer points at \n, which is still part of the newline and therefore, "getNextBlock" got 1 byte too much.

Refs Issue #4871
2023-02-04 15:16:22 +01:00
..
Wuson.ply Cleaned up Assimp-test repository of sample 3d models. 2008-12-30 12:32:45 +00:00
cube.ply header paths adjusted for unit tests and samples 2018-01-05 23:12:40 -08:00
cube_binary.ply Add PLY loader unit test for binary files 2018-03-04 16:04:12 +01:00
cube_binary_header_with_RN_newline.ply When "getNextBlock" was called after "getNextLine", the pointer could still on the newline. 2023-02-04 15:16:22 +01:00
cube_uv.ply Add unit-test for PLY with UV coordinates 2018-03-04 16:02:36 +01:00
float-color.ply Fix #1415 : float-color.ply is broken 2018-03-04 15:59:27 +01:00
issue623.ply Fix issue #4866 by continuing to resetting read loop after hitting a comment 2023-01-23 14:18:50 -05:00
points.ply Add test file. 2019-02-18 21:44:07 +01:00
pond.0.ply header paths adjusted for unit tests and samples 2018-01-05 23:12:40 -08:00