Mailing-List: contact ooo-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: ooo-dev@incubator.apache.org
Received-SPF: pass (nike.apache.org: domain of zongdj001@gmail.com designates
 209.85.210.175 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <50332CC4.3020207@pitonyak.org>
References: 
 <CAOh1a4NE625mNy-7JobOhoC9ZdQ5q71kFkOieu1yKs1wYKJaRg@mail.gmail.com>
	<50332AF5.7080409@pitonyak.org>
	<50332CC4.3020207@pitonyak.org>
Date: Tue, 21 Aug 2012 15:23:16 +0800
Message-ID: 
 <CAOh1a4P+S_T+Ry2qVzrRqGyYhORWpqoFcbfNgHbBPRV__oW9dw@mail.gmail.com>
Subject: Re: Is this a UNO API bug?
From: dongjun zong <zongdj001@gmail.com>
To: ooo-dev@incubator.apache.org, andrew@pitonyak.org
Content-Type: multipart/alternative; boundary=90e6ba25dc2ffb12ba04c7c17f8f

--90e6ba25dc2ffb12ba04c7c17f8f
Content-Type: text/plain; charset=ISO-8859-1

The strange thing is this API can works fine for doc sample file. I guess
this is a bug.

2012/8/21 Andrew Douglas Pitonyak <andrew@pitonyak.org>

>
> OK, I had to  look...
>
> For a text field, see if you can call update. This may not work if the
> document has not finished repaginating. I have heard of cases where a
> document had not finished doing that before someone tried to do stuff to
> it. The solution was to tell the document to full refresh (probably using a
> dispatch).
>
>
>
> On 08/21/2012 02:30 AM, Andrew Douglas Pitonyak wrote:
>
>>
>> Did you successfully insert the text field? If yes, then after you insert
>> a text field, it has probably not yet refreshed its value. Off hand, I
>> don't remember exactly what you need to refresh first.... I would need to
>> look it up and I really need to run but figured it might help you a bit and
>> you can look for the various refresh items (I think that you can refresh
>> each index and for fields I think there may be a single master field
>> refresh but I don't remember... have not done it in a long time.).
>>
>> On 08/20/2012 03:32 AM, dongjun zong wrote:
>>
>>> Hi All,
>>>     Using UNO API I do below operation.
>>> 1.Launch a odt document,
>>> 2.Create a page number field and insert into this docment
>>> 3.Get the document text
>>>
>>> But in the step3, page number is not contained in the get text. But if I
>>> launch a doc document, I can get the page number in step 3. I think this
>>> is
>>> a UNO API bug, can some body help confirm? Below is my main code pieces.
>>>
>>> XMultiServiceFactory sevriceFactory = (XMultiServiceFactory)
>>> UnoRuntime.queryInterface(**XMultiServiceFactory.class, document);
>>>          XTextField  pageNumberFiled =
>>> (XTextField)UnoRuntime.**queryInterface(XTextField.**class,
>>> sevriceFactory.createInstance(**"com.sun.star.text.textfield.**PageNumber"));
>>>
>>>
>>>          XPropertySet props =
>>> (XPropertySet)UnoRuntime.**queryInterface(XPropertySet.**class,
>>> pageNumberFiled);
>>>          props.setPropertyValue("**NumberingType", 4);//Set page number
>>> display as Arabic
>>>
>>>          XTextCursor xTextCursor = document.getText().**
>>> createTextCursor();
>>>          xTextCursor.gotoEnd(false);
>>>
>>> document.getText().**insertTextContent(document.**getText().getEnd(),
>>> pageNumberFiled, true);
>>>
>>>
>>>          String documentString = document.getText().getString()**;
>>>          System.out.println(**documentString);
>>>
>>>
>>
> --
> Andrew Pitonyak
> My Macro Document: http://www.pitonyak.org/**AndrewMacro.odt<http://www.pitonyak.org/AndrewMacro.odt>
> Info:  http://www.pitonyak.org/oo.php
>
>

--90e6ba25dc2ffb12ba04c7c17f8f--