ever). And it
stops properly *api->SetImage*, on demand. But this is not the case for
*api->ProcessPages*. Is there a missing feature here ?
On Wednesday, June 22, 2022 at 2:57:12 PM UTC+3 flavi...@gmail.com wrote:
> I also tried this (inside the thread method):
>
>
return true;
}
Stopping *api->ProcessPages* it is a mission impossible ?
On Tuesday, June 21, 2022 at 6:03:04 PM UTC+3 flavi...@gmail.com wrote:
> Win10, VS2017, MFC C++ application, Tesseract 4.1.1
>
> I started *TessBaseAPI::ProcessPage* call, and I realized I couldn't s
Win10, VS2017, MFC C++ application, Tesseract 4.1.1
I started *TessBaseAPI::ProcessPage* call, and I realized I couldn't stop
it. I noticed the prototype of *TessBaseAPI::ProcessPages*, if the int
timeout_millisec parameter is greater than 0, the library uses internally a
*ETEXT_DESC* monitor:
I hope to come back with a little sample project. Soon as possible.
On Thursday, March 24, 2022 at 9:59:12 AM UTC+2 flavi...@gmail.com wrote:
> Forgot to tell you, the initlization was successful and the image that I
> have tried to read is attached to this email.
>
> On Wednesd
Forgot to tell you, the initlization was successful and the image that I
have tried to read is attached to this email.
On Wednesday, March 23, 2022 at 4:39:40 PM UTC+2 flavi...@gmail.com wrote:
> I have implemented OCR with Tesseract 4.1
> (tesseract41.lib/tesseract41.dll), used on a Win
I have implemented OCR with Tesseract 4.1
(tesseract41.lib/tesseract41.dll), used on a Win10, 64 bit. Tesseract
library also compiled on 64 bit, of course.
I created a VC++ VS2017 test project, with the following code:
do
{
std::shared_ptr api =
std::make_shared
6 matches
Mail list logo
