Created attachment 176825 [details] Java code that call UNO API. Description: The writer documents that generated by using different UNO API SDK with same java code show difference. The most difference is that test frame position moved when inserting either PARA_BREAK character. Actual Results: With SDK version 7.1.x.x and LO 7.1.x, Text frame sustains it's position regardless of inserting PARA_BREAK. With SDK version 7.2.x.x and LO 7.2.x, Text frame moves it's position by inserting PARA_BREAK. Expected Results: UNO API over different SDK version should have same behavior. Reproducible: Always Additional Info: Java code provided. screen shots are provided too.
Created attachment 176826 [details] screen shot of document generated with sdk 7.1.x
Created attachment 176827 [details] screen shot of document generated with sdk 7.2.x
Yes, that's related to the fix of bug 120469. The obvious change would be to insert the frame to the first paragraph *after* inserting the break.
Alternative: make it anchored AT_PAGE, and optionally make it AT_PARAGRAPH after inserting the following paragraphs.
I tried Mike's advice. It works if it is simple case. but it didn't work as I anticipate if case is complicated. for reference, I will attach complicate case document. that document came from converting from Hwp to Odf using uno api. After some trials, I decided I'd rather append white space to the paragraph right after anchoring object to a paragraph. Appending white space make the paragraph to NOT EMPTY paragraph. As a conclusion, this change came from Writer, not from UNO api and it is an intended change. I close this issue.
Created attachment 177181 [details] converted document in version 7.1.x
Created attachment 177182 [details] converted document in version 7.2.x