You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openoffice.apache.org by Jürgen Schmidt <jo...@googlemail.com> on 2012/03/01 13:37:48 UTC
[RELEASE]: Bug 118366 - JAVA UNO API: XTextRange.getString returns
correct String only after some delay
Hi
I have change the release blocker flag for issues
https://issues.apache.org/ooo/show_bug.cgi?id=118366
I think it's a normal issue that we should fix but it is no show stopper
issue from my point of view.
Juergen
Re: [RELEASE]: Bug 118366 - JAVA UNO API: XTextRange.getString
returns correct String only after some delay
Posted by Jürgen Schmidt <jo...@googlemail.com>.
On Thu, Mar 1, 2012 at 6:16 PM, Oliver Brinzing <Ol...@gmx.de>wrote:
>
> > loop 1409
>
> forgot to mention:
>
> the number of loops is not predicable in aoo.
> with oo3.3 it's always 1.
>
>
ok I see, I should read more careful ...
sorry
Juergen
>
> --
>
>
> GnuPG key 0xCFD04A45: 8822 057F 4956 46D3 352C 1A06 4E2C AB40 CFD0 4A45
>
>
Re: [RELEASE]: Bug 118366 - JAVA UNO API: XTextRange.getString returns
correct String only after some delay
Posted by Oliver Brinzing <Ol...@gmx.de>.
> loop 1409
forgot to mention:
the number of loops is not predicable in aoo.
with oo3.3 it's always 1.
--
GnuPG key 0xCFD04A45: 8822 057F 4956 46D3 352C 1A06 4E2C AB40 CFD0 4A45
Re: [RELEASE]: Bug 118366 - JAVA UNO API: XTextRange.getString returns
correct String only after some delay
Posted by Oliver Brinzing <Ol...@gmx.de>.
Hi Rob
> think he is saying that the XTextRange.getString() function returns the
> wrong value if called immediately, but if he introduces a delay, via a loop,
> then the XTextRange.getString() function returns the correct value.
correct, output with aoo (example):
Document loaded as XComponent
Document now available as XTextDocument
loop 1409 placeholder[0] = <Kadr1>
Replace placeholder[0] = <Kadr1> with dummy content: Dummy1
output with oo3.3:
Document loaded as XComponent
Document now available as XTextDocument
loop 1 placeholder[0] = <Kadr1>
Replace placeholder[0] = <Kadr1> with dummy content: Dummy1
even if you don't accept this bug as a showstopper, it should
be fixed soon.
Regards
Oliver
--
GnuPG key 0xCFD04A45: 8822 057F 4956 46D3 352C 1A06 4E2C AB40 CFD0 4A45
Re: [RELEASE]: Bug 118366 - JAVA UNO API: XTextRange.getString
returns correct String only after some delay
Posted by Rob Weir <ro...@apache.org>.
On Thu, Mar 1, 2012 at 11:07 AM, Jürgen Schmidt
<jo...@googlemail.com> wrote:
> On 3/1/12 5:00 PM, Rob Weir wrote:
>>
>> On Thu, Mar 1, 2012 at 7:37 AM, Jürgen Schmidt
>> <jo...@googlemail.com> wrote:
>>>
>>> Hi
>>>
>>> I have change the release blocker flag for issues
>>> https://issues.apache.org/ooo/show_bug.cgi?id=118366
>>>
>>> I think it's a normal issue that we should fix but it is no show stopper
>>> issue from my point of view.
>>>
>>
>> They are claiming it is a regression compared to 3.3.0. Also claiming
>> it is a bug in LO as well. So probably a bug introduced in 3.4 beta?
>
>
> sure but it is a new issue caused by some other underlying changes. And as
> far as I understand it still works but is slower only.
>
Maybe I am misreading the bug report, but I don't think he is saying
that the function is slow. I think he is saying that the
XTextRange.getString() function returns the wrong value if called
immediately, but if he introduces a delay, via a loop, then the
XTextRange.getString() function returns the correct value.
That sounds like some sort of race condition or other synchronization
issue. It could cause existing scripts to break.
-Rob
> We can definitely focus on this issue when we have time but for me it is no
> critical show stopper.
>
> Juergen
Re: [RELEASE]: Bug 118366 - JAVA UNO API: XTextRange.getString returns
correct String only after some delay
Posted by Jürgen Schmidt <jo...@googlemail.com>.
On 3/1/12 5:00 PM, Rob Weir wrote:
> On Thu, Mar 1, 2012 at 7:37 AM, Jürgen Schmidt
> <jo...@googlemail.com> wrote:
>> Hi
>>
>> I have change the release blocker flag for issues
>> https://issues.apache.org/ooo/show_bug.cgi?id=118366
>>
>> I think it's a normal issue that we should fix but it is no show stopper
>> issue from my point of view.
>>
>
> They are claiming it is a regression compared to 3.3.0. Also claiming
> it is a bug in LO as well. So probably a bug introduced in 3.4 beta?
sure but it is a new issue caused by some other underlying changes. And
as far as I understand it still works but is slower only.
We can definitely focus on this issue when we have time but for me it is
no critical show stopper.
Juergen
Re: [RELEASE]: Bug 118366 - JAVA UNO API: XTextRange.getString
returns correct String only after some delay
Posted by Rob Weir <ro...@apache.org>.
On Thu, Mar 1, 2012 at 7:37 AM, Jürgen Schmidt
<jo...@googlemail.com> wrote:
> Hi
>
> I have change the release blocker flag for issues
> https://issues.apache.org/ooo/show_bug.cgi?id=118366
>
> I think it's a normal issue that we should fix but it is no show stopper
> issue from my point of view.
>
They are claiming it is a regression compared to 3.3.0. Also claiming
it is a bug in LO as well. So probably a bug introduced in 3.4 beta?
> Juergen