At 12:00pm -0500 Tue, 15 Nov 2011, Michael Meeks wrote:
there are some real issues here, inasmuch that it can't be known
until run-time what interfaces are supported, and lots of type
information disappears down the toilet around queryInterfaces and
'any's. Unfortunately, this makes the API hardly fit-for-purpose for
simple scripting use, but extending the API to make it fit (eg. by
having a flat set of implementation interfaces - complete with
default parameter types etc.) is conceptually problematic ;-)
Is it similarly as convoluted and difficult to have an explanation with,
say, RuntimeExceptions? For instance, with a document with only one
sheet, one should not be able to remove the last sheet, right?
>>> doc.Sheets.removeByName('Sheet1')
---------------------------------------------------------------------------
com.sun.star.uno.RuntimeException Traceback (most recent call last)
/home/kevin/ram/temoa/branches/tmpp/<ipython console> in <module>()
com.sun.star.uno.RuntimeException:
>>>
Which is correct of course, but not terribly elucidating (note the empty
trailing colon). Would this be a simple case of putting an RTL...string
in removeByName in docuno.cxx?
Cheers,
Kevin
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.