Selon Joerg Budischewski <[EMAIL PROTECTED]>: > Ideally, you try to make it reproducable and create an issue attaching > your sample code to it. You should also try to get a native stacktrace > (e.g. output of the crashguard), this will help to find out about the > reason.
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. > > 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]
