Hey Eike,
[1] fixes [2] which is more or less a problem in
ScRangeList::UpdateReference but we can't safely change it as there
might be some users that rely on this behavior. So we just map
URM_COPY to URM_MOVE which does the right thing in our case too.
Hmm.. sure it doesn't introduce unwanted side effects?
When copying from one sheet to another, previously all relative
references where then relative to the new position with same offsets.
With the change relative references "moved" along with the range still
do this, but references pointing outside that range now still point to
the old position instead of the new relative position.
Note: I didn't try, just making this up from what I know about
reference handling so far..
I'm only using URM_MOVE to update references inside a ScRangeList
which just contains a vector of ScRange entries. Since ScRange does
not contain a notion of relative or absolute references this is a safe
change,
Two lines later where I call UpdateReference for the entries which
might contain formulas I still use the original URM_* netry.
Regards,
Markus
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.