Don't use std::unique_ptr for SVEvent

[rmast]

#3869

[stweil]

This reverts parts of the commits 58e8538 and 37b3374, but misses some destructor calls which were previously used.

[stweil]

4.0.0 already used std::unique_ptr for this functionality (see code).

[rmast]

I didn’t test against 4.0.0. 4.1.3: ~/tesseract4.1.3$ grep unique_ptr src/viewer/scrollview.cpp ~/tesseract4.1.3$

[rmast]

Conclusion: Also /src/cutil/callcpp.cpp contains a unique_ptr-construction, but that’s probably not getting ‘delete’d. The big log is not falling over it. I think a clear choice has to be made between using those std::-constructs and make the Java-application use them as well, or just remove them.

[stweil]

For 4.x that code was in callcpp.cpp (see link in my previous comment).

[rmast]

For 4.x that code was in callcpp.cpp (see link in my previous comment).

Yes. I saw that on second look. My commit primarily reverses your second commit, but hardly the first one. I wonder whether those other variables are also transferred to and from Java, and whether the std:: -wrapping gives trouble with the Java-application.

[amitdo]

Replaced by #3872.