Jimmy wrote:
> I'm developping a component for Writer which has been tested with
> Windows and works fine on different machines with different OpenOffice
> Versions starting from 2.0.2 to 2.0.4.
>
> Now that I'm almost finished with it, I wanted to test the tool on a Mac
> and on Linux. Surpri
Bart Aimar wrote:
Paolo Mantovani ha scritto:
Hi Bart,
Ciao Paolo,
It works for me.
It adds a new item named "Standard.Module1.Test" under the "File" menu
of the current document.
I am a stupid man... :-(
I espected a NEW Menu...
In seek to decipher the code, I have not read the first
Hi,
we have released the first public release of our
StarOffice/OpenOffice.org NetBeans plugin to collect feedback.
Please see my announcement on our new GullFOSS blog
(http://blogs.sun.com/GullFOSS/entry/staroffice_openoffice_org_netbeans_integration)
for more detailed information (where to
HI Daniel
LanguageTool is already released and it has buggy OOo integration so I'd
like to fix it now. Will the grammar checker API be in 2.1? Can you tell
when the first binary snapshots with this feature will be available? If
it's not too far in the future I might indeed give up working with
Hu Jurgen
we have no fixed time period for unpublished APIs, the recommendation is
to publish an API at least after two releases. But APIs can be
unpublished forever when their usage is intended to be internally only.
ok
is it worth to setup a something for a regular review of this (not tha
Bernard Marcelly wrote:
Hi all,
While testing the next version of Xray I found two strange things with
small Basic macros in a Writer document.
1 - Basic code:
Dim sp as variant, v as variant
sp = thisComponent.getScriptProvider()
v = sp.ElementNames
The last instruction throws Basic
Laurent Godard wrote:
Hi
http://api.openoffice.org/docs/common/ref/com/sun/star/gallery/XGalleryThemeProvider.html
is marked as unpublished
are there any plan on this ? how long does something stay unbpublished ?
we have no fixed time period for unpublished APIs, the recommendation is
to
Dear OpenOffice.org community,
We really would like to see all questions answered, but
we need your help to keep track of your questions and their
answer status. Thus, if you still have a question unanswered
for more than two days, feel free to place a reminder on the
list. But maybe you should
On Monday 16 October 2006 08:03, Mathias Bauer wrote:
> I can't help with your problem, I only wanted to ask wether it is an
> option for you to wait for our new Grammar Checking API that will not
> require any text iteration from inside the Grammar Checker as it always
> gets plain text as a sour
Paolo Mantovani ha scritto:
Hi Bart,
Ciao Paolo,
It works for me.
It adds a new item named "Standard.Module1.Test" under the "File" menu of the
current document.
I am a stupid man... :-(
I espected a NEW Menu...
In seek to decipher the code, I have not read the first comment... Sorry!
Hi all,
While testing the next version of Xray I found two strange things with
small Basic macros in a Writer document.
1 - Basic code:
Dim sp as variant, v as variant
sp = thisComponent.getScriptProvider()
v = sp.ElementNames
The last instruction throws Basic runtime error:
Inadmissib
Tobias Krais wrote:
Hi Carsten,
http://www.openoffice.org/issues/show_bug.cgi?id=66236
We try to fix this issue for OOo 2.1.
thank you for this information. That would be great! And also thank you
for your work on this issue!
Hi Tobias,
I think I have a possible solution for this issue
Hi Carsten,
>> http://www.openoffice.org/issues/show_bug.cgi?id=66236
> We try to fix this issue for OOo 2.1.
thank you for this information. That would be great! And also thank you
for your work on this issue!
Greetings, Tobias
-
I'm developping a component for Writer which has been tested with
Windows and works fine on different machines with different OpenOffice
Versions starting from 2.0.2 to 2.0.4.
Now that I'm almost finished with it, I wanted to test the tool on a Mac
and on Linux. Surprisingly it failed and I do
Tobias Krais wrote:
Hi Julien,
I have tried your alternative solution (using transient changes of the
menu bar), and of course it works perfectly. It is far more better than
my first implementation (persistent modifications through OO
configuration), and as you have just told me, also reliable
Julien Galand wrote:
Le 18 oct. 06, à 14:46, Carsten Driesner a écrit :
I think you should use the API to set your keyboard shortcut. Just
have a look the a the following code snippet how to do it:
http://codesnippets.services.openoffice.org/Office/Office.ManagingKeyboardShortcuts.snip
There
Le 19 oct. 06, à 14:00, Stephan Bergmann a écrit :
I very much doubt that this is directly a problem of the UNO C++
language binding. com.sun.star.awt.KeyEvent is a UNO struct that has
members KeyChar and KeyCode. Maybe you can post the failing C++ code
here (if it is not too long) and s
Julien Galand wrote:
Hi,
Maybe this mail isn't appropriate in this mailing list (then tell me).
As far as I have understood, there seems to be a bug in the C++ UNO
binding of the awt::KeyEvent structure.
When using the following code snippet to set keyboard shortcuts
programmatically by the
Le 19 oct. 06, à 09:45, Tobias Krais a écrit :
you wrote, that you want to sell this solution. Please be aware of this
bug when doing this:
http://www.openoffice.org/issues/show_bug.cgi?id=66236
Hi Tobias,
Thank you. I was not aware of that.
Julien
--
Le 18 oct. 06, à 14:46, Carsten Driesner a écrit :
I think you should use the API to set your keyboard shortcut. Just
have a look the a the following code snippet how to do it:
http://codesnippets.services.openoffice.org/Office/
Office.ManagingKeyboardShortcuts.snip
There are many examples on
Hi,
Maybe this mail isn't appropriate in this mailing list (then tell me).
As far as I have understood, there seems to be a bug in the C++ UNO
binding of the awt::KeyEvent structure.
When using the following code snippet to set keyboard shortcuts
programmatically by the API :
http://codesni
Harald Weyhing wrote:
Hi Andreas, Carsten or others that might know about OOo 2.1.
Can you tell when OOo 2.1 is planned to be released? Something like "end
of next year" would be enough for me at this time.
Hi Harald,
You can see the current release map here:
http://wiki.services.openoff
Hi Andreas, Carsten or others that might know about OOo 2.1.
Can you tell when OOo 2.1 is planned to be released? Something like "end
of next year" would be enough for me at this time.
Thanks for your help
Cheers
Harald
Andreas Schlüns wrote:
Harald Weyhing schrieb:
Carsten Driesner wr
Hi Julien,
> I have tried your alternative solution (using transient changes of the
> menu bar), and of course it works perfectly. It is far more better than
> my first implementation (persistent modifications through OO
> configuration), and as you have just told me, also reliable for the
> futur
24 matches
Mail list logo
