Hi,
Thanks, Joerg. I realise that; unfortunately however, I have no authorization to
post my code on a public list :( But I might send it to a few people really in
charge of developing the API and/or the PyUNO bridge who agreed to use it
exclusively for enhancing/debugging OOo. Do you know who would be interested
and willing to accept those conditions?
Cheers,
Jorge.
when you strip down your code to just reproduce the error, the code is
in general useless and of no/little value ( but I know there maybe
employer not understanding this :-) ).
I don't see a chance to analyze your problem otherwise (except build OOo
on your own and try to hunt it down yourself or pay someone to do it).
It might be, that I need to pass the issue further on to another
developer in case it is not a pyuno bug, there no way other than doing
this via issuezilla. Sorry.
Bye,
Joerg
Bye,
joerg
By the way, I've read about crash resulting from python exceptions, but you
must
understand that the components are run a couple of times and crash happens
while
doing routine things like editing or closing, some time after the action of
any
component. And during development, when my component rose exceptions, they
seemed to be very well treated by Basic (the only user of my components so
far). In a word: while they had (grosser) errors, the didn't crash OOo ;o)
Cheers,
Jorge.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
