I have a background service for identifying after receiving the data. There is no problem in normal use, but when I hold my screen, this error appears, indicating that there is a problem with the so library.
can you please provide us a full log. This can be done setting the following configuration (ensure you replace PATH_LOG_FILE by the path where you store your log file): conf.setString(“debug.log-file”, "PATH_LOG_FILE");
can you please provide us a full log. This can be done setting the following configuration (ensure you replace PATH_LOG_FILE by the path where you store your log file): conf.setString(“debug.log-file”, "PATH_LOG_FILE");
This may help understand what is occurring.
Best regards,
Olivier
C
Chad li
said
over 4 years ago
We have tried to catch the exception, but no exception was thrown.
If no exception is raised, in order to be able to investigate further, we would need your project. Indeed, with the below information, it it difficult to understand what is likely to cause the issue.
Best regards,
Olivier
C
Chad li
said
over 4 years ago
The PointerDown method was used first, and the specific code block is as follows:
currently, I do not see a "PointerDown" event? Indeed, after clearing the editor and when starting adding new stroke, you shall ensure each stroke starts with a "pointerDown".
Each following point shall be added with the pointerMove, and the last pen shall be added with a pointerUp.
Normally, you should have an exception occuring. Can you please try to catch it, which would prevent from crashing and return more information?
Best regards,
Olivier
C
Chad li
said
over 4 years ago
Hello, our operation process is roughly as follows:
We have a background service here to pass the handwriting data to myscript for identification, and then when we switch pages, we will call the Editor.clear () method, reset the package and contentPart parameters, and then continue to handwriting data to myscript Identify.Then there is a chance that this bug will appear
O
Olivier @MyScript
said
over 4 years ago
Dear Chad,
thank you for contacting us.
Currently, the crash by itself doesn't help much. Is it possible to have the exact scenario, so that we can reproduce?
When you say you have a background service, what do you mean? What is the latter doing? You send the strokes via this background service and add strokes from the screen at the same time?
Please explain, so that we can reproduce and better understand what is happening.
Chad li
I have a background service for identifying after receiving the data. There is no problem in normal use, but when I hold my screen, this error appears, indicating that there is a problem with the so library.
Dear Chad Li,
can you please provide us a full log. This can be done setting the following configuration (ensure you replace PATH_LOG_FILE by the path where you store your log file): conf.setString(“debug.log-file”, "PATH_LOG_FILE");
This may help understand what is occurring.
Best regards,
Olivier
- Oldest First
- Popular
- Newest First
Sorted by Newest FirstOlivier @MyScript
Dear Chad Li,
can you please provide us a full log. This can be done setting the following configuration (ensure you replace PATH_LOG_FILE by the path where you store your log file): conf.setString(“debug.log-file”, "PATH_LOG_FILE");
This may help understand what is occurring.
Best regards,
Olivier
Chad li
We have tried to catch the exception, but no exception was thrown.
What should we do now?
Olivier @MyScript
Dear Chad Li,
Did you try to catch the exceptions that may be raised on the pointerMove function: https://developer.myscript.com/refguides/interactive-ink/android/1.3/com/myscript/iink/Editor.html#pointerMove-float-float-long-float-com.myscript.iink.PointerType-int- This may help investigate.
If no exception is raised, in order to be able to investigate further, we would need your project. Indeed, with the below information, it it difficult to understand what is likely to cause the issue.
Best regards,
Olivier
Chad li
The PointerDown method was used first, and the specific code block is as follows:
Olivier @MyScript
Dear Chad Li,
currently, I do not see a "PointerDown" event? Indeed, after clearing the editor and when starting adding new stroke, you shall ensure each stroke starts with a "pointerDown".
Each following point shall be added with the pointerMove, and the last pen shall be added with a pointerUp.
Normally, you should have an exception occuring. Can you please try to catch it, which would prevent from crashing and return more information?
Best regards,
Olivier
Chad li
Hello, our operation process is roughly as follows:
We have a background service here to pass the handwriting data to myscript for identification, and then when we switch pages, we will call the Editor.clear () method, reset the package and contentPart parameters, and then continue to handwriting data to myscript Identify.Then there is a chance that this bug will appear
Olivier @MyScript
Dear Chad,
thank you for contacting us.
Currently, the crash by itself doesn't help much. Is it possible to have the exact scenario, so that we can reproduce?
When you say you have a background service, what do you mean? What is the latter doing? You send the strokes via this background service and add strokes from the screen at the same time?
Please explain, so that we can reproduce and better understand what is happening.
Best regards,
Olivier