On 19.05.2015 14:08, Edgar Holst wrote:
To generate bookmarks, making checks, ..., we are scrolling with Basic
through the whole document. To protect the visible scrolling and speed
up the process of checking, we are using the Basic function
"ThisComponent.lockControllers" and at the end of checking
"ThisComponent.unlockControllers".
And here is the Problem. If the document grow up, let me say about 10
and more pages, pages get lost and information in cells can't be
checked. If we don't use "lock/unlockControllers" everything works fine,
but it slow down the process extremly. And if the document has up to 100
and more pages, "You know what User's say to me, ..."
do you use the document's XTextViewCursor? it could be faster to create
a new XTextCursor from the document and use that; it would avoid visibly
scrolling the document around at least, even without lockControllers.
you can create a new cursor with
ThisComponent.getText().createTextCursor()
that said i wouldn't know how much of the slowdown is due to using the
view cursor instead of a plain text cursor, and how much is due to
re-layouting after every modification of the document, which can only be
avoided with lockControllers.
Context
Privacy Policy |
Impressum (Legal Info) |
Copyright information: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License.
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (
MPLv2).
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our
trademark policy.