Replies: 1 comment 3 replies
-
iOS defaults to the C++ defaults, see here. |
Beta Was this translation helpful? Give feedback.
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
The Kotlin/Native wrapper PR discussion reminded me of an open question I had in my mind: What are the best default performance related
ReaderOptions
and should they be equal across all APIs or depend on the context, like mobile vs. desktop/backend?For the general C++ interface, I came to the conclusion that the defaults are best set such that they maximize the detection rate and every deviation from that is basically to make the detection faster. In the Android wrapper the defaults are set to maximize speed. In iOS I don't even know what is happening. It seems there are not defaults at all, so one has to specify all settings explicitly? (The iOS demo does unfortunately not use any options setting).
There is the trivial consistency argument to make them behave the same by default. It also solves the question of how to deal with Kotlin/Native which can't be clearly put in either mobile or desktop. What is your preference? If you answer
NO
, please leave a comment explaining why.4 votes ·
Beta Was this translation helpful? Give feedback.
All reactions