Apache OpenOffice (AOO) Bugzilla – Issue 68757
LayoutSize property for TextFrames close to the Bottom Page Border Returns the Wrong Value
Last modified: 2013-02-24 21:08:29 UTC
When a frame is close to the page's edge, it is impossible to ascertain the actual size of the content of a text frame with automatic height. If I create a textframe with a 5cm texttable (this is probably true for other types of content) and it is 1cm away from the bottom margin LayoutSize does not return 5cm but 1cm. It is not telling me how big the frame is, but how much it is possible to layout. Perhaps this is a feature. Perhaps a new property is required. In OpenOffice it is very difficult to manage programmatically things like page breaks. Without knowing how big a frame regardless of where it is on the page it is very difficult to use OpenOffice to build a text renderer.
jsc -> tl: writer API issue
.
I am having trouble reproducing this with a macro, so it could be a bug in my code. Having I am seeing a related problem. After rendering x number of pages it just stops returning sensible values. No matter how long I sleep, or how often I refresh or reformat the document, it just returns either a void uno object or 487. This is for a table in a text frame.
Now the document is formatted automatically before retrieving the value. This should fix all problems but may take some time depending on the size of the document and how much of it was formatted previously or not. Fixed in CWS tl25. Files changed: - sw/source/core/unocore/unoframe.cxx - offapi/com/sun/star/text/BaseFrameProperties.idl
great thanks. I will test it as soon as I can and return feed back. Any ideas which build this will go into? I am presuming it will not go into the next release candidate. regards.
No. It will still take some weeks beacause I want to add some more bugs to the CWS. And then, who knows when it gets integrated... ^^'
alrighty, well if you can tell me when it gets into a build I can get test it easier and get give feedback quicker. One thing related to this that you might want to look into. There is some sort of of resource leak with lots of frames. I render a document with loads of frames and you can watch it crawl to a halt. To be honest I have not completely isolated it to frames, but I have a pretty good gut feeling. The frames are with styles. I will be happy to give you more information if you want. kind regards
TL->CN: I see no good way to test this fix because it might have already worked ok previously if the document was completely formatted. Maybe it is possible to check this with a larger document and comparing it to the old versions. So you can just check the changed IDL and (if you like) the source file. ;-)
ok in tl25
ok in src680m202