On Mon, Aug 05, 2013 at 09:44:38PM +0200, Lionel Elie Mamane
wrote:
> This last one is triggered (by a chain of reasons where one link is)
> because it does not find the tango theme. Let me explain.
Ah OK, so in this case it indeed caused a problem. Sorry for the
misguidance. ;-)
signature.asc
On Sat, Aug 03, 2013 at 08:29:23PM +0200, Lionel Elie Mamane
wrote:
> Now, it fails because it cannot find the tango theme; actually there
> is no solver/unxlngx6/unittest/install/share directory at all. How do
> I get it into the unittest environment?
Are you sure that's the reason for the fail
On Aug 3, 2013 1:29 PM, "Lionel Elie Mamane" wrote:
>
> And that's because file xmloff/util/xo.component contains:
>
>
>
>
> which is the service about with it was complaining. OK, I understand
> and I'm one step more removed from "cargo cult unittest writing".
>
> Now, it fails because
OK that contains all the necessary information. You need to add
xmloff/util/xo to the component list.
This component file contains the missing service specification.
On Aug 3, 2013 11:32 AM, "Lionel Elie Mamane" wrote:
> On Sat, Aug 03, 2013 at 05:51:37PM +0200, Markus Mohrhard wrote:
>
> > I'm
Hey Lionel,
I'm until September in vacation so i can only give you some General advice.
Most of the time loading fails because of a wrong path or missing component
files. I suppose you checked the first so you might need a dbgutil build
that prints information about failed loading of component fi
Hey Lionel,
So you basically have two options. We already have a test concept where we
open a file and execute a basic macro in it. You can find an example for it
in sc/qa/extras/macros-test.cxx
The other more flexible option is that you open a document and call the uno
calls yourself from c++. T
