Hey,
[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.
Regards,
Markus
[1]
Hi Markus,
On Saturday, 2012-12-15 15:28:49 +0100, Markus Mohrhard wrote:
[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
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