The documentation about the iink SDK undo stack mentions that it is partially purged from time to time. Is it possible to have more details about when / under what conditions that happens?
If it makes a difference, we are using the iink SDK version 1.4 on Android.
Thank you!
Best Answer
O
Olivier @MyScript
said
about 4 years ago
Dear Nicolas,
thank you for your question.
Currently, the documentation by itself is explicit, i.e. checking the memory consumption, the iink decides if the the undo/redo stack shall be purged.
The solution is to check the details.possibleUndoCount to know how many stemps can be undone.
Best regards,
Olivier
1 Comment
O
Olivier @MyScript
said
about 4 years ago
Answer
Dear Nicolas,
thank you for your question.
Currently, the documentation by itself is explicit, i.e. checking the memory consumption, the iink decides if the the undo/redo stack shall be purged.
The solution is to check the details.possibleUndoCount to know how many stemps can be undone.
Nicolas Morin
The documentation about the iink SDK undo stack mentions that it is partially purged from time to time. Is it possible to have more details about when / under what conditions that happens?
If it makes a difference, we are using the iink SDK version 1.4 on Android.
Thank you!
Dear Nicolas,
thank you for your question.
Currently, the documentation by itself is explicit, i.e. checking the memory consumption, the iink decides if the the undo/redo stack shall be purged.
The solution is to check the
details.possibleUndoCountto know how many stemps can be undone.Best regards,
Olivier
Olivier @MyScript
Dear Nicolas,
thank you for your question.
Currently, the documentation by itself is explicit, i.e. checking the memory consumption, the iink decides if the the undo/redo stack shall be purged.
The solution is to check the
details.possibleUndoCountto know how many stemps can be undone.Best regards,
Olivier