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 <[email protected]> > 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 > <[email protected]> > >
_______________________________________________ LibreOffice mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/libreoffice
