Mathias Bauer wrote:
As it seems you don't apply any modifications to the Ooo installation,
but you deliver your application to your users, right?
Do they have to execute a setup for this? You could deliver the macro or
component mentioned above as a UNO package and integrate it into your
Mathias Bauer wrote:
Ales Kahanek wrote:
I have found this:
In OpenOffice.org API the Listener mechanism is used to add a handler
for a specific event. This is not possible from Delphi because the COM
bridge does not support call-back primitives necessary for that purpose.
Now, as we use
Ales Kahanek wrote:
What do you think about following solution built in the standard OOo
instalation: when starting saving document OOo will create a very small
file (only a several bytes) with name corresponding with the original
file and remove this temporary file after saving is
Ales Kahanek wrote:
I have found this:
In OpenOffice.org API the Listener mechanism is used to add a handler
for a specific event. This is not possible from Delphi because the COM
bridge does not support call-back primitives necessary for that purpose.
Now, as we use Delphi, this is not
I have found this:
In OpenOffice.org API the Listener mechanism is used to add a handler
for a specific event. This is not possible from Delphi because the COM
bridge does not support call-back primitives necessary for that purpose.
Now, as we use Delphi, this is not the right way for us. Is
Mathias Bauer wrote:
Relying on the locked state of a file IMHO is a hack (sorry). But
Yes, I know that this is not the best way, but there are many
applications that do their job in many different ways and if the check
if the process is active scenario fails, then this is may be the last
