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. 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.
Regards,
Markus
2011/5/4 Kohei Yoshida <kyoshida@novell.com>
On Wed, 2011-05-04 at 11:58 -0400, Kohei Yoshida wrote:
void setNewByTable( [in] long nTab, [in]
com::sun::star::table::CellRangeAddress aRange )
raises( com::sun::star::lang::IndexOutOfBoundsException );
Actually now I prefer setByTable without the 'New'. The method could be
used to overwrite the existing range as well...
--
Kohei Yoshida, LibreOffice hacker, Calc
<kyoshida@novell.com>
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.