Re: [api-dev] registering script events

2006-01-04 Thread Oliver Brinzing
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, However, I am not sure how to test equality of UNO objects in Basic, I'd suppose that = might not really work here. Perhaps there's a dedicated function for this. EqualUnoObjects( oObj1, oObj2 ) should work ... Oliver - -- GnuPG key

Re: [api-dev] Optional Parameters in Starbasic function call

2006-01-04 Thread Bernard Marcelly
Bonjour Andreas Bregas Message du 2006-01-03 15:05: Hi, The bug was reported in IZ 30500. In versions 1.1.x and 2.0.1 it is still not corrected and not even documented, so it should not have status RESOLVED and FIXED. perhraps reopen the bug and mark it as regression in keywords no,

Re: [api-dev] Optional Parameters in Starbasic function call

2006-01-04 Thread Laurent Godard
Hi Andreas no, please don't. The status is correct as this task is really fixed on my cws ab19. But both the cws and the task are targeted OOo Later and the cws is not integrated yet. So no master containing the fix is available. Nevertheless it is Resolved/Fixed and of course it's no

[api-dev] GlobalEventBroadcaster and StarBasic - continued ( ....catch a Base document being opened )

2006-01-04 Thread Andrew Jensen
OK, This is getting closer, but a couple of issues remain. I have my sub procedure that is called by the OnDocumentOpen broadcast event. Using the suggested technique of reading the last frame's title from the ActiveDesktop frames container does indeed work. However, as I put up before, the

Re: [api-dev] registering script events

2006-01-04 Thread Marc Santhoff
Am Dienstag, den 03.01.2006, 09:27 +0100 schrieb Frank Schönheit - Sun Microsystems Germany: Hi Marc, Hello Frank, The IDL reference tells me about css.script.registerScriptEvent: ... registers one event for an object identified by its index. If any object is

Re: [api-dev] Optional Parameters in Starbasic function call

2006-01-04 Thread Andrew Douglas Pitonyak
Laurent Godard wrote: Hi Bernard, The bug was reported in IZ 30500. In versions 1.1.x and 2.0.1 it is still not corrected and not even documented, so it should not have status RESOLVED and FIXED. perhraps reopen the bug and mark it as regression in keywords where are optional parameters

[api-dev] Thanks For The Help -- Upgraded From 1.x to 2.x (and upgrade notes)

2006-01-04 Thread Hal Vaughan
I just wanted to say thanks for the quick help and replies this past week. I have a Java application that was using OOo 1.x and I needed to see how much effort it would take to upgrade to 2.x (it was either that or use 1.1.5). I thought, when the time came to actually upgrade to 2.x, that it

Re: [api-dev] GlobalEventBroadcaster and StarBasic - continued ( ....catch a Base document being opened )

2006-01-04 Thread Marc Santhoff
Am Dienstag, den 03.01.2006, 17:53 -0500 schrieb Andrew Jensen: OK, This is getting closer, but a couple of issues remain. I have my sub procedure that is called by the OnDocumentOpen broadcast event. Using the suggested technique of reading the last frame's title from the ActiveDesktop

[api-dev] OOo 2.0.1: Java-interface on RH FC 3 not finding OOo Java classes, if ...

2006-01-04 Thread Rony G. Flatscher
Hi there, have been running over a very strange problem (RedHat Fedora Core 3, OOo 2.0.1 installed parallel to OOo 1.1.4): addressing OOo via Java (using a Java archive that itself uses native code that uses JNI 1.2). If setting up the environment (CLASSPATH, PATH, invoking java with

Re: [api-dev] Optional Parameters in Starbasic function call

2006-01-04 Thread Frank Schönheit - Sun Microsystems Germa ny
Hi Bernard, I can't understand this. If it's fixed it should be integrated ASAP, why keep it OOo Later ? It was fixed in August 2005, and could have been integrated in 2.0.1. I queried IssueZilla for : RESOLVED and FIXED and OOo Later and Creation date between 2005-01-01 and now. Result :

Re: [api-dev] Optional Parameters in Starbasic function call

2006-01-04 Thread Andrew Jensen
Frank Schnheit - Sun Microsystems Germany wrote: Hi Bernard, I can't understand this. If it's fixed it should be integrated ASAP, why keep it OOo Later ? It was fixed in August 2005, and could have been integrated in 2.0.1. I queried IssueZilla for : RESOLVED and FIXED and