Hello, I've sucessfully compiled and run a quick-and-dirty OpenCV application (let's call it app A) in C++ using Tesseract. Later, I refactored my code into app B and used a tesseract::TessBaseAPI tess; member into one of my classes there. When running this B app, first thing the program does, Scrollview tries to initialize --unsuccessfully, leading to the eternal Waiting for server... display. However, in app A, where tess is just a local variable, there's no such behavior. Neither in CLI usage of Tesseract, for that matter. I think I don't want Scrollview. I read in the forums that recompiling Tesseract is the suggested workaround. Shouldn't this be an opt-in for the sake of precompiled dev packages? Can't this be avoided? How should I instantiate TessBaseAPI objects so that I don't unwishfully call Scrollview? Thank you in advance!
-- You received this message because you are subscribed to the Google Groups "tesseract-ocr" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/tesseract-ocr. To view this discussion on the web visit https://groups.google.com/d/msgid/tesseract-ocr/5b8cbd5c-e3d5-4086-8c09-a811a8dc6af5%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
