On Wed, 2011-05-04 at 18:23 +0200, Markus Mohrhard wrote:
I'm fine with nearly everything. And your suggestion looks even a bit
better than mine, except for the setByTable method.
I was thinking about adding the table index too, but stumbled over the
case when the table index does not match the table the db data refers
to.
Ok. I still wonder in what situations the table index differs from the
table of the db data, but I'll take your word for it.
We have a similar problem in our code base, but as long as we are
aware of it there are no problems. But with the new uno api there
might be an add-on developer who doesn't know that the range and the
table index must match.
So I would prefer to get the information which table is used by the db
range itself. It will still be possible to check for the index to be
out of bounds.
Ok. I'm fine with that. Let's go with your suggestion.
Kohei
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.