-
Notifications
You must be signed in to change notification settings - Fork 750
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Process from imagedata #188
base: master
Are you sure you want to change the base?
Conversation
Ive added the possibility to pass a byte-pointer directly the downside is that is has to be decleard as unsafe. |
Looks good, I don't have an issue with the unsafe code (we already have some unsafe code in PixData). However in this case using an IntPtr might be a better fit. |
byte* to IntPtr
byte* to IntPtr
What's the actual use case here and is there any reason why you cannot use a Pix directly? I've had a bit of a look here and I'm not sure this is such a good idea as all tesseract does in this case is convert the byte data into a Pix object (see ImageThresholder::SetImage in the tesseract source code). |
Maybe a few things you could consider:
|
OK, I agree. |
For my project it was easier to process the pixeldata directly so i added the missing functions in the wrapper maybe someone else needs that.