Hey guys,
I have a document with about 20 columns and 500 rows using
DDE("soffice", …) to get the data from another doucment. The reason
I am using DDE() instead of an array reference to the other file is
that the array reference does not grow, i.e. if the referred file
has a line added, I have to erase and recreate the array, whereas
I can just add additional DDE() lines.
The problem I am having is that with 500 lines, adding a new line
(using fill-down) takes about *an hour per line*, so to add 6 lines,
I just had the machine chugging at 100% CPU time for 6 hours, while
libreoffice was entirely unresponsive.
Do you have any idea what's going on, or how to optimise this?
Thanks,
--
@martinkrafft | http://madduck.net/ | http://two.sentenc.es/
"to me, vi is zen. to use vi is to practice zen. every command is
a koan. profound to the user, unintelligible to the uninitiated.
you discover truth everytime you use it."
-- reddy ät lion.austin.ibm.com
spamtraps: madduck.bogus@madduck.net
--
To unsubscribe e-mail to: users+unsubscribe@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/users/
All messages sent to this list will be publicly archived and cannot be deleted
Context
- [libreoffice-users] DDE() taking minutes while the CPU has a party · martin f krafft
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.