Hi,
after many years, ooo api users have finally got a concrete generic
implementation of an associative array or Lookup table or
dictionary list
That's great! this powerful service could greatly simplify the
development of macros / extension
but..
unfortunately the implementation is
We have encountered a strange problem that involves OpenOffice 3.2.1 (also
reproduced with OpenOffice 2.4 but does not reproduce with OpenOffice 2.1) on
Windows Server 2003 R2, 2008, and 2008 R2. The basic problem is that it does
not print through the API. The interesting thing is that the
I have confirmed that the problem re-creates on Windows 2008 Server when it is
running natively on the hardware. It does not appear to be a problem with the
Microsoft HyperV.
-Original Message-
From: Herter, Scott [mailto:scott.her...@napersoft.com]
Sent: Saturday, December 18, 2010
Hello Paolo,
On Saturday 18 December 2010, 11:00, Paolo Mantovani wrote:
Hi,
after many years, ooo api users have finally got a concrete generic
implementation of an associative array or Lookup table or
dictionary list
That's great! this powerful service could greatly simplify the
On Saturday 18 December 2010, 21:34:00, Ariel Constenla-Haile wrote:
IMHO the wrong choice was to use the UNO type instead of
com.sun.star.uno.TypeClass.
With TypeClass and the support for new-style service constructor, it could
have been as simple as:
Dim aMap
aMap =
I really do not understand this. Let me restate the part the confuses me:
(1) I can print using a macro with no problem.
(2) I cannot print using the API
When you use a macro, you use the API; or did I miss something?
On 12/18/2010 12:05 PM, Herter, Scott wrote:
We have encountered a
I fully agree with Paolo, this kind of API is a complex solution to a simple
need.
I tried to make it work like this:
Dim keyType As Object, valueType As Object, reflect As Object
reflect = CreateUnoService(com.sun.star.reflection.CoreReflection)
keyType = reflect.forName(string)
valueType =
