Hi Paolo, Carlos, *
Paolo Mantovani escribió:
> Hi,
>
> Andreas Schlüns ha scritto:
>> Hi Carlos,
>>
>>> (I'm using Automation Bridge to communicate with OOo)
>>>
>>> After reading again all the stuff and trying to digest the java
>>> sample, this is what I conluded:
>>>
>>> I need to implement my own "DispatchProvider" as a COM object an pass
>>> it as a parameter to "registerDispatchProviderInterceptor", in the
>>> same way I do to register listeners, am I right? (is this the reason
>>> why Ariel said this can't be achieved with Basic?)
> Why not? You can register your own dispatch-interceptor in Starbasic and
> you can even define your custom dispatches in order to react to user
> actions
What I meant with
> mmm... I'm not sure if there is a way to achieve this with OOo Basic, as
> it can not implement UNO components.
is that one can not achieve this in a "full programmatic" (?) way with
OOo Basic: I mean, a dispatch interceptor, like a context menu
interceptor, can work in OOo Basic using the listener technique; but for
the whole thing to really work on every document the user open/creates,
you need an extension implementing a Job.
The only way I see [correct me if I'm wrong, and please share if someone
knows a working way] for OOo Basic is the Tools - Customize - Events ...
but of course this is a no-way for an extension.
So I'd dare to say that OOo Basic can not achieve this for an extension
that - in a "full programmatic" way - wants to intercept commands.
[Though I hope I'm wrong... or at least someone is developing/thinking
about giving OOo Basic the chance to fully/really work as an extension
development language]
Regards
Ariel
--
Ariel Constenla-Haile
La Plata, Argentina
"Aus der Kriegsschule des Lebens
- Was mich nicht umbringt,
macht mich härter."
Nietzsche Götzendämmerung, Sprüche und Pfeile, 8.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
