We would like to ask a few questions about limits in iink Text Documents.
1- Is there a maximum number of Text blocks that can be created in a document?
2- As explained in an earlier question, we have other layers on top of the iink layer where the user can input data. Those layers are tied to the iink layer, in part so that the iink line markers and strokes scroll along with the other layers. To be able to scroll lower than the last iink input from the user, we are using a trick where we first add a dummy text block at the start of the document, then add another one at a far away y offset (for example, at the equivalent of a 16000 lines offset with font size set to 8 and line size set to 1.4) and finally delete the first dummy block. That way, it is possible to scroll the iink document without the need for the user to input anything to it.
Do you think such an implementation could cause some problems? For instance, we noticed that scrolling when located at a 1600 lines offset feels fine, but scrolling when we are around the 16000 lines offset gets slow (laggy).
Do you think there is a realistic maximum offset that we could safely use? (An answer with an offset in mm or pixels is fine).
Best Answer
G
Gwenaelle @MyScript
said
over 3 years ago
Hi Nicolas,
The height of the document contributes to its size, so it can indeed contribute to the issue you observe.
Regarding the block Ids:
On save and reload, yes they are preserved.
On edit operations, (undo/redo, create/delete/create), they are preserved as much as possible but there are some situations when this is not possible.
We would like to be able to recognize the dummy ContentBlock we added. One option is to store the ID of the block when we create it. However, are there scenarios where the IDs of ContentBlocks can change? For example, if we save the iink document to file and then reopen it, will all ContentBlocks have the same IDs reassigned to them? Can the ID change when a block is deleted or undone and then restored with Redo? etc.
Thank you!
G
Gwenaelle @MyScript
said
over 3 years ago
Hi Nicolas,
There is no maximum number of blocks within a Text Document.
The performance depend on several factors including the size of the document, the device on which the application is running, the integration itself. For sure the larger the document is, either in term of blocks, line, or content, the slower the performance.
Best regards,
Gwenaëlle
1 person likes this
N
Nicolas Morin
said
over 3 years ago
Thank you for answering the first question.
What about the other questions?
Are there foreseen issues with adding a text block at a very high y offset?
Are ContentBlock IDs preserved if we save and reload a document? If we undo and redo the block creation/deletion?
G
Gwenaelle @MyScript
said
over 3 years ago
Answer
Hi Nicolas,
The height of the document contributes to its size, so it can indeed contribute to the issue you observe.
Regarding the block Ids:
On save and reload, yes they are preserved.
On edit operations, (undo/redo, create/delete/create), they are preserved as much as possible but there are some situations when this is not possible.
Nicolas Morin
We would like to ask a few questions about limits in iink Text Documents.
1- Is there a maximum number of Text blocks that can be created in a document?
2- As explained in an earlier question, we have other layers on top of the iink layer where the user can input data. Those layers are tied to the iink layer, in part so that the iink line markers and strokes scroll along with the other layers. To be able to scroll lower than the last iink input from the user, we are using a trick where we first add a dummy text block at the start of the document, then add another one at a far away y offset (for example, at the equivalent of a 16000 lines offset with font size set to 8 and line size set to 1.4) and finally delete the first dummy block. That way, it is possible to scroll the iink document without the need for the user to input anything to it.
Do you think such an implementation could cause some problems? For instance, we noticed that scrolling when located at a 1600 lines offset feels fine, but scrolling when we are around the 16000 lines offset gets slow (laggy).
Do you think there is a realistic maximum offset that we could safely use? (An answer with an offset in mm or pixels is fine).
Hi Nicolas,
The height of the document contributes to its size, so it can indeed contribute to the issue you observe.
Regarding the block Ids:
Best regards,
Gwenaëlle
- Oldest First
- Popular
- Newest First
Sorted by Oldest FirstNicolas Morin
We have another question related to this.
We would like to be able to recognize the dummy ContentBlock we added. One option is to store the ID of the block when we create it. However, are there scenarios where the IDs of ContentBlocks can change? For example, if we save the iink document to file and then reopen it, will all ContentBlocks have the same IDs reassigned to them? Can the ID change when a block is deleted or undone and then restored with Redo? etc.
Thank you!
Gwenaelle @MyScript
Hi Nicolas,
There is no maximum number of blocks within a Text Document.
The performance depend on several factors including the size of the document, the device on which the application is running, the integration itself.
For sure the larger the document is, either in term of blocks, line, or content, the slower the performance.
Best regards,
Gwenaëlle
1 person likes this
Nicolas Morin
Thank you for answering the first question.
What about the other questions?
Are there foreseen issues with adding a text block at a very high y offset?
Are ContentBlock IDs preserved if we save and reload a document? If we undo and redo the block creation/deletion?
Gwenaelle @MyScript
Hi Nicolas,
The height of the document contributes to its size, so it can indeed contribute to the issue you observe.
Regarding the block Ids:
Best regards,
Gwenaëlle