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

..

headercheck

Removed uneeded expression in else() and endif() constructs.

2020-02-23 07:09:35 -05:00

models

When "getNextBlock" was called after "getNextLine", the pointer could still on the newline.

2023-02-04 15:16:22 +01:00

models-nonbsd

Reuploaded (fixed) mmd model

2022-04-13 02:50:31 +02:00

other

Add first WIP version of a TrueSpace loader. Currently only ASCII COB/SCNs are supported.

2010-04-02 04:17:05 +00:00

regression

Merge branch 'master' into x3d_pugi_migration

2021-09-07 15:04:08 +02:00

unit

When "getNextBlock" was called after "getNextLine", the pointer could still on the newline.

2023-02-04 15:16:22 +01:00

.editorconfig

Implemented: Add editor config for test code

2015-06-28 16:08:06 -06:00

.gitignore

Add Exporter Unit Test output to gitignore

2019-07-25 11:12:06 +01:00

CMakeLists.txt

Add check for wall switch from cmake

2022-09-17 18:16:42 +02:00

test.3mf

Fixes

2021-11-10 20:37:27 +01:00