So to my surprise I discovered TD62 still has this ridiculous limitation.
See test application has two testcases:
- Create a string buffer which exceeds 64k, copy it to farmem and copy back to a new buffer
- Load a bitmap file which exceeds 64k, copy it to farmem and copy back and display in a picture object
Clearly the cstruct way will result in a cutoff buffer, limit of 64K.
(the string buffer reports a wrong text length, the testcase using the bitmap will show a truncated image).
The test application also shows the possible workaround, using memcpy/RtlMoveMemory WinApi functions.
(uncheck the cstruct checkboxes to use the workaround).
Both ANSI and UNICODE versions are available.
Please lift this old limitation to support "unlimited" buffer sizes using cstruct.
